M365 Agent icon

M365 Agent

Send messages, cards, thread replies, and invoke responses through Microsoft 365 Agents (Teams / Copilot / WebChat).

Actions28

Thumbnail Card → Update

AI-generated

Summary

Updates an existing Microsoft Teams Thumbnail Card in a conversation using the Bot Framework Connector API.

Inputs

  • title (required) — The main title of the card.
  • subtitle — The subtitle text of the card.
  • text — The main body text of the card.
  • images — A collection of images with optional URLs, alt text, and tap actions.
  • buttons — A collection of buttons with type, title, value, and options like channel data and display text.
  • options — Additional card options including fallback text, raw activity override, and tap action for the card body.
  • authKind (required) — The authentication method: 'classicBot' for Azure Bot Service or 'agent365' for Entra Agent Identity.
  • conversationSource (required) — Source of conversation routing info: 'envelope' (uses item data) or 'manual' (requires Service URL, Conversation ID, and Channel ID).
  • serviceUrl — Bot Connector service URL for the target channel. Required when 'conversationSource' is 'manual'.
  • conversationId — The conversation ID. Required when 'conversationSource' is 'manual'.
  • channelId — Azure Bot Service channel the conversation belongs to. Required when 'conversationSource' is 'manual'.
  • activityId — Required only for Reply / Update / Delete operations against a specific activity. Leave empty for proactive sends.
  • identityMode — When using 'agent365', whether the agent acts autonomously or as a specific M365 user account.
  • userSelectorMode — Selector for the agentic user when using 'agentUser' mode: 'byUpn' or 'byObjectId'.
  • agentUsername — UPN of the agentic user when using 'agentUser' mode with 'byUpn'.
  • agentUserId — Object ID of the agentic user when using 'agentUser' mode with 'byObjectId'.

Output shape

No body — success/failure only. The operation does not return data items.

The operation relies on the item's data for conversation routing when 'conversationSource' is 'envelope'. Requires valid authentication credentials configured in the node.

Examples

Example 1: Update a card in a thread reply

Set conversationSource to 'envelope' and use item data for routing. Populate title, subtitle, and text.

Example 2: Send a proactive update from an external process

Set conversationSource to 'manual'. Provide Service URL, Conversation ID, and Channel ID. Leave activityId empty.

Example 3: Update a card as an Entra Agent with specific user identity

Set authKind to 'agent365', identityMode to 'agentUser', and userSelectorMode to 'byObjectId' with agentUserId.

Links

Discussion