Send email with Make
An HTTP module in a scenario, with the key in a connection.
You need a verified sending domain and an API key from Settings › API Keys. If neither exists yet, the quickstart covers both in a couple of minutes.
Send
URL: https://sending.dev/api/v1/emails
Method: POST
Headers: Authorization: Bearer sk_your_api_key
Body type: Raw · JSON (application/json)
{
"from": "Acme <[email protected]>",
"to": "{{1.email}}",
"subject": "Welcome",
"html": "<p>You are in.</p>",
"idempotencyKey": "welcome-{{1.id}}"
}A successful call answers 202 with the message id: accepted and queued, not yet delivered. Delivery, opens, bounces and complaints arrive later, on webhooks or in the dashboard.
What changes in Make
Turn on Parse response so later modules can read the returned id instead of a raw string.
The thing that catches people
Make's error handling retries the module by default. With the record id in the idempotency key a retry is answered with the original message id, and nothing is sent twice.
Next
- All the fields: cc and bcc, reply-to, attachments, templates, scheduling.
- Webhooks: delivery, bounce and complaint events, signed with HMAC.
- Domains: SPF, DKIM and MAIL FROM, and why sending is refused until they are in place.
- MCP: the same operations as tools, when the one writing the code is an agent.