sendsend.email
Sign inStart building

Zapier

Send email from any Zap, add contacts, and start Zaps when an email is delivered, bounces, is opened or arrives.

Status. The Zapier app is built and tested against a stand-in API, but it is not in Zapier’s public app directory yet. Until then it is shared as a private app: ask us for an invite, or use the HTTP route below today, which needs nothing from us.

What the app does

  • Send Email action: from, to, subject, HTML or text, cc, bcc, reply-to, a send time, and an optional idempotency key.
  • Create or Update Contact action: adds someone to an audience, or updates them. Someone who unsubscribed stays unsubscribed.
  • Email Event trigger: delivered, bounced, complained, failed, opened, clicked, delayed, sent, scheduled, suppressed, or received. It creates and removes its own webhook and ignores anything that is not signed by SendSend.

Connect your account

Create an API key in the dashboard under API keys and paste it when Zapier asks. Give it only what your Zaps need: emails:send to send, contacts:manage for contacts, webhooks:manage for the trigger.

Today, without the app

Zapier’s built-in Webhooks by Zapier works with any API:

  1. Add an action, choose Webhooks by Zapier → Custom Request.
  2. Method POST, URL https://api.sendsend.email/v1/emails, Data Pass-Through off.
  3. Data: {"from":"Acme <hello@mail.acme.com>","to":["{{email}}"],"subject":"Hi","html":"<p>Hello</p>"}, mapping your own fields in.
  4. Headers: Authorization: Bearer ss_live_… and Content-Type: application/json. Add Idempotency-Key mapped to a unique value from your trigger so a Zap replay never sends twice.

To start a Zap from an event, use Webhooks by Zapier → Catch Hook, then create a webhook that points at the URL Zapier gives you. That route does not check signatures, so keep the Zapier URL private.