Send Email
sending_send_emailSend an outbound email with CC/BCC, HTML/text body, and attachments via uploaded attachment IDs. Include an Idempotency-Key to avoid duplicate sends on retries.
Instructions
Use this to send one outbound email through the sending API. For attachments, call sending_upload_attachment first for local/tiny content or sending_create_attachment_upload for delegated file PUTs, then pass attachments as attachment_id refs. Inline base64 is only for tiny generated content. Include an Idempotency-Key so retries do not create duplicate sends.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | CC recipients (subject to 50 total To, CC, and BCC recipients) | |
| to | Yes | Primary recipient | |
| bcc | No | BCC recipients (subject to 50 total To, CC, and BCC recipients) | |
| from | Yes | Sender address | |
| subject | Yes | Email subject line (max 998 chars, RFC 5322) | |
| reply_to | No | Reply-To address | |
| html_body | Yes | HTML email content (max 25MB) | |
| text_body | No | Plain text alternative (max 25MB) | |
| attachments | No | File attachments (max 10). Use attachment_id refs for uploaded files. | |
| return_path | No | Envelope sender for VERP support | |
| custom_headers | No | Custom X-* headers to include in the email | |
| Idempotency-Key | No | Optional client-generated key to make the request idempotent for 24 hours. Replays under the same key return the cached response; a reused key with a different body returns 409 idempotency_conflict. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||