Send transactional email
email_sendSends ONE transactional email (a receipt, a reply, a booking confirmation) to one address right away. Not reversible, and it uses one email of quota. Never use it for marketing or to mail a list: campaigns are for that. Show the person the recipient, subject and body and get a yes before calling, then pass confirm: true. idempotency_key is required: reuse the same key if you retry so the email is not sent twice. Pass html, text, or both. Requires API key scope: send.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"to": "<to>",
"subject": "<subject>",
"idempotency_key": "<idempotency_key>",
"confirm": "<confirm>"
},
"name": "email_send"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient address. | |
| html | No | HTML body (at most 200,000 characters). Hollerpost adds the brand header. | |
| text | No | Plain text body (at most 50,000 characters). | |
| confirm | Yes | Must be true, and only after the person explicitly approved this exact recipient, subject and body. Never set it on a guess. | |
| subject | Yes | Subject line. | |
| reply_to | No | Reply-to address, if different from the workspace default. | |
| idempotency_key | Yes | A unique key for this email, for example "receipt-1042". Reusing it returns the first result instead of sending again. |