M365 AgentInstall

Summary

Updates a hero card in an existing conversation via the M365 Agent node.

Inputs

• authKind (required) — Authentication kind for the agent. Classic Bot uses an Azure Bot resource + Entra App Registration; Agent 365 uses an Entra Agent Blueprint identity, no Azure Bot resource needed.
• conversationSource (required) — Where the conversation routing info comes from. 'From Envelope' uses conversationReference from the current item (works for replies/updates/deletes automatically). 'Specify Manually' requires filling service URL and conversation ID fields.
• serviceUrl (required) — Bot Connector service URL for the target channel. Required when conversationSource is 'Specify Manually'. Example: https://smba.trafficmanager.net/emea/
• conversationId (required) — The conversation ID. For Teams channels this looks like 19:xxx@thread.tacv2. Use an expression such as {{ $JSON.channelId }} if stored upstream. Required when conversationSource is 'Specify Manually'.
• channelId (required) — Azure Bot Service channel the conversation belongs to. Options: Direct Line, Emulator, Microsoft 365 Copilot, Microsoft Teams, Web Chat. Default: msteams.
• activityId — Required only for Reply / Update / Delete operations against a specific activity. Leave empty for proactive sends.
• title (required) — Title of the hero card. Required for send and update operations.
• subtitle — Subtitle of the hero card.
• text — Main text body of the hero card.
• images — Images to include in the hero card. Each image can have a URL, alt text, and tap action with configurable type, title, value, and channel data.
• buttons — Buttons to overlay on the hero card. Each button supports activity types such as Open URL, IM Back, Post Back, Open App, and others, with title, value, and optional channel data.
• options — Additional options including fallback text, raw activity override (replace constructed Activity with custom JSON), and tap action on the card body.
• identityMode — Controls the identity under which the agent operates. 'Autonomous' acts as the Blueprint app identity. 'Agent User' acts as an M365 user, requiring additional licenses (E5 + Teams Enterprise + Agent 365 on the agentic user account).
• userSelectorMode — Selects how the agentic user is identified when identityMode is 'agentUser': by UPN or by Azure AD Object ID.
• agentUsername — UPN of the agentic user. Defaults to the credential's Default Agent Username.
• agentUserId — Object ID of the agentic user in Azure AD. Required when userSelectorMode is 'byObjectId'.
• agentUserNotice — Informational notice that agent user account mode requires a separate license (E5 + Teams Enterprise + Agent 365) on the agentic user account.

Output shape

Returns the constructed or updated Activity object representing the hero card, including card content and conversation reference. Exact return shape depends on the underlying bot connector implementation and conversation routing.

The node's execute flow (update.operation.js, dispatchUpdate.js) transmits an update activity to the specified conversation. The rawActivityOverride option can replace the constructed Activity body with custom JSON for protocol fields not exposed through the UI.

Examples

Example 1: Update hero card in existing Teams conversation using envelope conversation reference

authKind: classicBot, conversationSource: envelope, title: 'Status Update', text: 'Everything is working well.', subtitle: 'System health check'

Example 2: Proactive send of hero card update outside bot flow

authKind: agent365, conversationSource: manual, serviceUrl: 'https://smba.trafficmanager.net/emea/', conversationId: '19:xxx@thread.tacv2', channelId: msteams, title: 'Proactive Alert', text: 'New data available', identityMode: autonomous

Links

• n8n community nodes installation guide