Zapier

Pick one or more Events: Sent, Delivered, Delivery delayed, Bounced, Marked as spam, Opened, Link clicked, Failed, Suppressed, Scheduled or Canceled.

Each run carries the email (its ID, from, to, subject, Message-ID, tags and template) and the event's details: the bounce type and message, the opened or clicked link, the failure or suppression reason, or the delay. Fields that do not apply to an event are empty, so the same fields are there to map on every run. The events guide explains what each event means.

No settings. Each run carries the sender, the recipients, the subject, the text and HTML bodies, and each attachment's file name. Attachments themselves are not passed to Zapier.

If the message body cannot be read, the Zap still runs, with Body Available set to false, so you can decide what to do in the next step. Set up receiving first: see the receiving guide.

No settings. Each run carries the contact's ID, email, name, unsubscribed state, segment IDs and when it was created and updated.

No settings. Each run carries the same contact fields as New Contact. Updated Contact does not say which field changed. Don't follow it with Create or Update Contact on the same contact: that update starts the Zap again.

Pick the Events (Started, Completed, Failed or stopped) and, if you like, one Automation. Each run carries the run's ID, the automation's ID, the contact's ID, the event that started it, its status and, for a failed run, the reason.

No settings. Zapier checks for new ones every few minutes, as often as your Zapier plan allows, and these use no webhook endpoint.

New Unsubscribe catches people who use an email's unsubscribe link or your preference page. An address that was already suppressed, after a bounce for example, is not reported again. An unsubscribe made through the API shows up as Updated Contact instead.

The step returns the new email's ID, which later steps can map.

Schedule Email has the fields of Send Email, plus Send At: a date and time, or a phrase such as tomorrow at 9am, up to 30 days ahead. Reschedule Email and Cancel Scheduled Email take the Email from a list of your scheduled emails, or the Email ID mapped from the step that scheduled it.

Add Contact to Segment, Remove Contact From Segment, Subscribe Contact to Topics, Unsubscribe Contact From Topics and Delete Contact each take a Contact Email (or the contact's ID) and pick the segment or topics from a list.

• A segment with a filter keeps including the contacts that match it.
• Someone who unsubscribed from everything still gets no campaigns, whatever their topics say.
• Delete Contact can't be undone.
• Removing a contact or a membership that is already gone succeeds, so a replayed Zap run doesn't fail.

Create or Update Contact also shows one field per contact property you have set up in Rasket, so you can fill each one by name.

One field, Email. Rasket sends nothing to a suppressed address. Removing an address that bounced or reported you for spam can hurt your sending reputation, so remove only ones you know are good.

Pick an Event and give a Contact Email. If the event has a schema in Rasket, each of its fields appears by name; anything else goes under Data. The event starts every automation that listens for it. Rasket can't tell a replayed run from a new one here, so a replay sends the event again.

Create Campaign takes a Segment, a From address on a verified domain, a Subject, and either a Template or your own HTML and text. Set Send Now to send it straight away; leave it off to keep a draft. Send Campaign and Send Test Campaign pick from your drafts; Cancel Campaign picks from your scheduled and sending campaigns.

A campaign sends only when it passes Rasket's send checks, such as a verified domain, a postal address on your team and a segment that exists. If one fails, the step stops with the reason.

One field, Email. It finds the contact with that address, or reports none. Choose Find or Create Contact to add the contact when there is none, using the fields of Create or Update Contact.

Find Email takes an Email ID and returns the email with its latest status. The others take a name (or a template's alias) and find only an exact match, ignoring case, so a later step never acts on a near miss.

Rasket ended the connection. It was revoked under Settings → Connected apps, the admin who approved it left the team, or it reached its 90 days. Reconnect and approve again.

The connection was approved before this step existed. Reconnect Rasket in Zapier and approve again, so the connection includes the new permission.

The address must be on a domain your team has verified for sending. The From dropdown and its help text list them. If it says you have none, add and verify a domain first.

Every Zap that is on and starts with a Rasket trigger holds one webhook endpoint, and your plan allows a fixed number. Turn off a Zap you no longer need, delete endpoints you do not use under Webhooks, or move to a larger plan.

If you delete a Zap without turning it off first, its endpoint can stay behind. Delete it under Webhooks.

A team may make ten requests a second. A busy Zap that goes over is slowed down and retried by Zapier on its own; see rate limits. A used-up sending quota is different: the step stops with a message saying so, and it will not succeed until the quota resets or you raise it under Billing.

The step shows Rasket's own error message, naming the field it is about. The errors page lists every one.