Actions57
- Card Actions
- Card Builder Actions
- Channel Actions
- Chat Actions
- Message Actions
- Analyze Reactions
- Delete
- Delta (All Chats)
- Export All Messages (Metered)
- Export Retained Messages (Metered)
- Generate Thumbnail
- Get
- Get Many
- Get Pinned Messages
- Get Reaction Analytics
- List Messages
- List Replies
- Monitor Upload
- Pin Message
- Pin Channel Message
- Process File
- Reply
- Reply with Attachment
- Send
- Send and Wait
- Send File Link
- Send with Attachment
- Set Reaction
- Soft Delete
- Undo Delete
- Unpin Message
- Unpin Channel Message
- Unset Reaction
- Update
- Upload to OneDrive
- Subscriptions Actions
- Team Actions
- User Actions
Card → Send Notification
AI-generatedSummary
Send a notification adaptive card with a title and message to a Microsoft Teams recipient, which can be either a channel or a direct chat user, optionally customizing notification type, including an image, and adding an action button with a URL.
Inputs
- Title (required) — The title of the notification.
- Message (required) — The message content of the notification.
- Recipient Type (required) — The type of recipient: 'Channel' to send to a Teams channel, or 'Chat (Direct Message)' to send directly to a user.
- Team ID (required) — The ID of the team containing the channel; required if sending to a channel.
- Channel ID (required) — The ID of the channel to send the card to; required if sending to a channel.
- User ID (required) — The ID or email address of the user to send the card to; required if sending as a direct chat message.
- Options — Optional settings to customize the notification, including notification type (color coding), image URL to include, action button URL, and action button label.
Output shape
a single item containing the API response object from sending the adaptive card notification.
The operation asynchronously sends the adaptive card notification. It returns the API response parsed as an object. Errors may occur if Bot Framework authentication fails, the bot is not installed for the recipient, or parameters are invalid. This operation does not provide pagination or subsequent updates. Recipient-specific parameters must be provided based on the chosen recipient type (channel vs chat).