M365 AgentInstall

Summary

Sends an Animation Card activity to a conversation via the Bot Connector, optionally using the incoming envelope or manually supplied conversation details.

Inputs

• authKind (required) — Authentication method: Classic Bot (Azure Bot Service) or Agent 365 (Entra Agent Identity).
• conversationSource (required) — Whether to take conversation reference from the incoming item (envelope) or fill it in manually.
• title (required) — Title shown at the top of the animation card.
• subtitle — Subtitle shown below the title.
• text — Body text of the animation card.
• posterImageUrl — URL of a poster / preview image displayed before playback.
• posterImageAltText — Alternative text for the poster image.
• media — Collection of media items to play, each with a URL and optional profile hint.
• buttons — Collection of action buttons; each button defines a type, title, value, and optional channel‑specific data.
• options — Additional animation‑card options such as aspect ratio, autoloop, autostart, duration, fallback text, raw activity override, shareable flag, and an opaque value object.
• serviceUrl — Bot Connector service URL for the target channel (required when conversationSource is manual).
• conversationId — Conversation ID (required when conversationSource is manual).
• channelId — Channel ID (required when conversationSource is manual).
• activityId — Existing activity ID to reply to or update (optional).
• identityMode — For Agent 365 auth: whether the agent acts as its Blueprint app identity (autonomous) or as its own M365 user (agentUser).
• userSelectorMode — For Agent 365 auth with agentUser mode: select the user by UPN or object ID.
• agentUsername — UPN of the agentic user when identityMode is agentUser and userSelectorMode is byUpn.
• agentUserId — Object ID of the agentic user when identityMode is agentUser and userSelectorMode is byObjectId.

Output shape

object

Returns the sent Activity object from the Bot Connector (including at least the activity ID and other metadata).

Examples

Example 1: Reply to an incoming Teams message with an animation card

conversationSource set to envelope, authKind set to classicBot, title provided, optional subtitle, text, media, and buttons defined.

Example 2: Proactively send an animation card to a Teams chat

conversationSource set to manual, serviceUrl, conversationId, channelId filled, authKind as needed, title and other card fields supplied.

Links

• n8n community nodes installation guide