Actions23
- Activity Actions
- Adaptive Card Actions
- Attachment Actions
- Conversation Actions
- Proactive Actions
- Reaction Actions
Attachment → Send Inline Attachment
AI-generatedSummary
Send a message with an inline attachment encoded as base64 directly within the Microsoft Teams conversation specified by the Service URL and Conversation ID.
Inputs
- Service URL (required) — The Bot Framework service URL, typically obtained from trigger output, specifying the Teams service endpoint.
- Conversation ID (required) — The target conversation ID in Microsoft Teams where the inline attachment message will be sent.
- Message Text — Optional text content to accompany the inline attachment in the message.
- Attachment Name — Optional filename to identify the inline attachment.
- Attachment Content Type — MIME type of the inline attachment; defaults to 'application/octet-stream'.
- Inline Base64 — Base64-encoded string of the attachment content to send inline; leave empty to use data from the specified binary property.
- Binary Property — Name of the binary property from which to read base64-encoded attachment data if Inline Base64 is not provided; defaults to 'data'.
- Mention Options — Options to configure mention behavior, such as automatically mentioning the sender, specifying mention ID and name, and whether to prepend mention text to the message.
- Execution Options — Settings to control debug output, output data shaping (pass through, merge, response only), and retry logic for API calls.
Output shape
a single JSON object representing the API response for the sent message activity
The operation constructs a message activity with type 'message' and an inline base64-encoded attachment, applying mention options if specified, then performs a POST request to the Bot Framework API at /v3/conversations/{conversationId}/activities. Output can be shaped per Execution Options, with optional debug metadata included.
Examples
Example 1: Send a base64-encoded inline image as an attachment with a text message in a Teams conversation.
Specify the Service URL and Conversation ID acquired from a trigger, provide Message Text, set the Attachment Content Type to 'image/png', optionally name the attachment, and supply base64 data inline or via input binary data property.