Actions28
- Adaptive Card Actions
- Animation Card Actions
- Audio Card Actions
- Card State Machine Actions
- Hero Card Actions
- Invoke Response Actions
- Message Actions
- O365 Connector Card Actions
- Raw Attachment Actions
- Receipt Card Actions
- Sign-In Card Actions
- Thumbnail Card Actions
- Video Card Actions
Hero Card → Send
AI-generatedSummary
Send a Microsoft 365 hero card to a specified conversation.
Inputs
- authKind — Authentication method; classicBot uses Azure Bot resource, agent365 uses Entra Agent Blueprint identity.
- conversationSource — Where routing info comes from; envelope for replies/updates, manual for proactive sends.
- serviceUrl (required) — Bot Connector service URL for the target channel.
- conversationId (required) — Conversation identifier; for Teams channels format like 19:xxx@thread.tacv2.
- channelId — Azure Bot Service channel type; default msteams, options include directline, emulator, etc.
- activityId — Activity identifier for Reply/Update/Delete; 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 body text of the hero card (multiline).
- images — Collection of image objects; each can include URL, alt text, and tap actions.
- buttons — Collection of button objects; each defines type, title, value, and optional actions.
- options — Additional card options such as fallback text, raw activity override, and tap action.
- identityMode — When using agent365 authKind, how the agent identity is resolved; autonomous or agentUser.
- userSelectorMode — When identityMode is agentUser, criteria for selecting the user; By UPN or By Object ID.
- agentUsername — UPN of the agentic user; defaults to credential's Default Agent Username.
- agentUserId — Object ID of the agentic user; required when userSelectorMode is By Object ID.
- agentUserNotice — Notice about license requirements for agentUser identity mode.
Output shape
object representing the sent activity (e.g., includes id, serviceUrl, etc.)
Optional fields may be omitted; errors raise an exception; no pagination.
Examples
Example 1: Proactive send of a hero card using manual conversation ID.
authKind=classicBot, conversationSource=manual, serviceUrl=https://smba.trafficmanager.net/emea/, conversationId=19:xxx@thread.tacv2, title=Hello, text=World, channelId=msteams
Example 2: Update an existing message by replying within the same conversation.
authKind=classicBot, conversationSource=envelope, serviceUrl=https://smba.trafficmanager.net/emea/, conversationId=19:xxx@thread.tacv2, title=Updated, text=Update reply, activityId=12345