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 Approval Request
AI-generatedSummary
Send an adaptive approval request card to a Microsoft Teams channel or user chat to prompt for approval with customized options.
Inputs
- Title (required) — The title of the approval request.
- Description (required) — The description of what needs to be approved.
- Request ID (required) — A unique identifier for this approval request.
- Recipient Type (required) — Choose whether to send to a Teams channel or a user direct message.
- Team ID (required) — The ID of the team containing the channel (required if Recipient Type is Channel).
- Channel ID (required) — The ID of the channel to send the card to (required if Recipient Type is Channel).
- User ID (required) — The ID or email address of the user to send the card to (required if Recipient Type is Chat).
- Options — Optional details for the approval request including requester name, due date, additional info, and custom labels for approve and reject buttons.
Output shape
a single item containing the API response confirming the adaptive card was sent
The operation returns the Teams API response after sending the adaptive approval card. Validation of inputs occurs before sending. Either a channel message or a direct chat message is created depending on recipient type. The card includes buttons for Approve and Reject actions with customizable labeling and optional metadata fields.