M365 AgentInstall

Summary

Send video card

Inputs

• authKind — Authentication method: classicBot (Azure Bot Service + Entra App Registration) or agent365 (Agent Blueprint in Entra, no Azure Bot resource needed). Default: classicBot.
• conversationSource — Where conversation routing info comes from: envelope (uses conversationReference from current item, works for replies/updates/deletes) or manual (fill conversation reference fields yourself, required for proactive sends outside the bot). Default: envelope.
• serviceUrl — Bot connector service URL for the target channel. Required when conversationSource is manual. Example: https://smba.trafficmanager.net/emea/
• conversationId — The conversation ID. For Teams channels this looks like 19:xxx@thread.tacv2. Required when conversationSource is manual. Use an expression like {{ $JSON.channelId }} if stored upstream.
• channelId — Azure Bot Service channel the conversation belongs to. Options: directline, emulator, msteamscopilot, msteams, webchat. Default: msteams.
• activityId — Required only for Reply/Update/Delete operations against a specific activity. Leave empty for proactive sends.
• title (required) — Title shown on the video card. Default: empty.
• subtitle — Subtitle shown below the title on the video card. Default: empty.
• text — Rich text content of the video card. Default: empty. Supports multi-line input.
• posterImageUrl — URL of a poster/preview image shown before playback. Default: empty.
• posterImageAltText — Alt text for the poster image. Default: empty.
• media — Fixed collection of media items (multiple values allowed). Each item has url (string, required) and options.profile (string, optional, quality/format hint).
• buttons — Fixed collection of button actions (multiple values allowed). Each button has type (options: call, downloadFile, imBack, messageBack, openApp, openUrl, playAudio, playVideo, postBack, showImage, signin, required), title (string, required), value (string, required, placeholder depends on type), and optional sub-options: channelData (json, default {}), displayText (string), image (string), imageAltText (string), text (string), valueJson (json, default {}).
• aspectRatio — Aspect ratio for the video card. Default: empty, placeholder: 16:9.
• autoloop — Whether the video should autoloop. Default: false.
• autostart — Whether the video should autostart. Default: false.
• duration — Duration of the video in ISO-8601 format (e.g., PT5M). Default: empty.
• fallbackText — Fallback text for the video card. Default: empty.
• rawActivityOverride — Optional: replace the constructed Activity body with raw JSON. Empty uses existing behavior. Used for protocol fields the UI does not expose (custom channelData, experimental Activity shapes). Must parse to a JSON object.
• shareable — Whether the video card is shareable. Default: true.
• value — Opaque object passed through as VideoCard.value. Default: {}.
• identityMode — Only when authKind is agent365, resource is videoCard, and operation is send. Options: autonomous (agent acts as its Blueprint app identity) or agentUser (agent acts as its own M365 user, requires sidecar transport and a separate license on the agentic user account). Default: autonomous.
• userSelectorMode — Only when authKind is agent365, resource is videoCard, operation is send, and identityMode is agentUser. Options: byUpn or byObjectId. Default: byUpn.
• agentUsername — UPN of the agentic user. Default: {{ $credentials.defaultAgentUsername || '' }}. Placeholder: agent@contoso.com. Only shows when authKind=agent365, resource=videoCard, operation=send, identityMode=agentUser, userSelectorMode=byUpn.
• agentUserId — Object ID of the agentic user. Placeholder: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Only shows when authKind=agent365, resource=videoCard, operation=send, identityMode=agentUser, userSelectorMode=byObjectId.

Output shape

The sent activity item returned from the bot connector. Exact shape depends on the connector response and whether rawActivityOverride was provided.

For proactive sends with conversationSource=manual, serviceUrl and conversationId must be provided. Replies/updates/deletes automatically use the conversationReference from the envelope when conversationSource=envelope.

Examples

Example 1: Proactive video card send to a Teams channel using manual conversation reference

authKind=classicBot, conversationSource=manual, serviceUrl=https://smba.trafficmanager.net/emea/, conversationId=19:xxxx@thread.tacv2, channelId=msteams, title=Meeting Reminder, text=Don't forget our meeting at 3pm, media=[{url: https://example.com/video.mp4, options:{profile: high}}], buttons=[{type:openUrl, title:Join, value:https://teams.microsoft.com/l/meetup-join/...}]

Links

• n8n community nodes installation guide