Resources · Zapier integration

Amazon SES Zapier integrationAutomate Amazon SES with Zapier.

Count them on one hand: the Amazon SES Zapier integration gives you 1 trigger, 1 action and 0 searches. SES can send a message on behalf of any app, and it can flag a freshly verified sender. Below: how each works, the price in tasks and the weak spots.

Premium app Zapier reserves this app to its paid plans.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Amazon SES Zapier integration is for

The Amazon SES Zapier integration plugs Amazon's email sending service into the rest of your tools. Any app Zapier supports can ask SES to send a message, and SES can tell Zapier when a new identity has been verified. Two operations in total: a short catalog, aimed at sending rather than managing.

Three results come up most. First, transactional emails from tools that cannot send their own: a form entry, a new row or a paid invoice starts the Zap, and Create Email sends the matching message through SES. Second, internal alerts: the same action mails your team when something in another app needs a human look. Third, an admin heads-up: New Verified Identity notices when an identity passes verification in SES, and the Zap tells whoever set it up that sending can start.

Now the limits, which the app page keeps quiet about. There is no search, so a Zap cannot look up an existing identity or a past message. There is no trigger for opens, bounces or replies, and no action to manage identities, templates or lists. If you were hoping to follow delivery from Zapier, the catalog does not go there.

One more thing: SES is a premium app on Zapier, so it is a paid-plan job from day one. Weighing your options? The Amazon SES Make integration page covers the same service on Make, and the n8n vs Zapier comparison lays out the differences by criterion rather than by verdict.

Vocabulary

Zapier vocabulary in one minute

A handful of Zapier words come back on every line below. Here they are, plainly.

Zap
A recipe that runs by itself on Zapier: one starting event, then the steps that follow it each time, here usually ending in an email.
Trigger
The starting event. It may be an identity SES has just verified, or something that happens in another app entirely.
Action
A step that does the work once the Zap is under way. On this page the main one is handing an email to SES.
Task
Zapier's billing unit: each step that succeeds is one task, and the monthly allowance on your plan is counted in them.
Polling vs instant
Polling: Zapier asks the app for news on a schedule. Instant: the app speaks up as soon as it happens. SES polls.
Filter
A checkpoint you add between steps: if the data passes your condition the Zap goes on, if not it ends there.
Connection
The saved link to your SES account, made once and then picked from a menu in each Zap that sends mail.
Cost

What it really costs

No free ride here: Zapier lists Amazon SES among its premium apps, so you will need a paid plan or the trial.

  • App typePremium: paid plan or free trial
  • Trigger cost0 tasks, however often Zapier checks
  • Each email sent1 task when the action succeeds
  • Failed sendNot counted

That rules out the free tier entirely, with its 100 tasks a month, its 15 minute checks and its two-step limit. Once you are on a paid plan, what you spend is easy to predict. Watching SES for new identities never touches your allowance. Each message that Create Email hands over successfully uses one task, and a send that errors out uses none. Put a filter in front, for instance so only some form answers get a reply, and you have a multi-step Zap, which paid plans allow.

Connect

Connect Amazon SES to Zapier in 3 steps

  1. 01

    Start from your Apps page

    Inside Zapier, open Apps from your account and press + Add connection. Look up Amazon SES in the dialog and click its name. The dialog may list other Amazon apps, so check the name.

  2. 02

    Sign in to Amazon

    Click Add connection. A new tab opens: sign in with the Amazon account that runs your SES sending, the one whose identities and emails the Zap should use.

  3. 03

    Grant access

    Accept what Zapier requests. From then on the SES connection is listed under Apps, ready for any new Zap. When the sending account belongs to a coworker, ask them for access before you start.

First Zap

Your first Zap: announce each verified identity by email

GoalWhenever SES verifies an identity, an email goes out through SES to tell the team that sending can start.

  1. 01

    Pick the trigger

    Start a new Zap. Set Amazon SES as its starting app and New Verified Identity as the event, then pick your SES connection.

  2. 02

    Test on a real identity

    Test the trigger. Zapier fetches up to three recently verified identities from the account, which gives you something real to work with in the next steps.

  3. 03

    Add a filter (optional)

    Click the plus icon and choose Filter. Fill in the three boxes: the identity field, a text rule such as an exact match, then the value to compare it with.

  4. 04

    Add Create Email

    Add a step with Amazon SES and Create Email. Write a short message for the team and drop in the identity that the trigger brought back.

  5. 05

    Test, then publish

    Run the action once and check the email that arrives. When it reads right, click Publish. Each email sent from then on uses one task.

Triggers

Amazon SES triggers

1 event starts a Zap when something happens in Amazon SES. Zapier checks for them at the interval your plan allows.

1

New Verified Identity

Polling trigger

In Zapier“Triggers when a new identity is verified in SES.”

Your Zap wakes up when SES marks an identity as verified, and the next steps receive that identity. This is the app's single trigger, and it belongs to setup rather than sending: it says a sender is ready, never that a message left.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise
When to use it
you want the person who asked for a new sender to get a note, or a ticket closed, once SES has verified it.
Watch out
identities verified before the Zap went live are never picked up.
Actions

Amazon SES actions

Amazon SES gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Email

Action

In Zapier“Create a new email.”

Hands a new message to SES, which sends it for you, filled with whatever the earlier steps of the Zap carried. Every successful send counts as one task.

When to use it
a tool with no email feature of its own, like a form or a sheet, has to send a confirmation or an alert.
Watch out
a Zap that emails into an inbox another Zap watches can loop and burn tasks.
When it breaks

When the Zap breaks

Two operations means few moving parts; when a Zap on SES fails, look first at when it was switched on and at how it is wired.

Zapier links one help article to this app, on getting started with Amazon SES; read it before you dig further. The Zapier troubleshooting page explains how to read a failed run step by step.

  • Nothing from before the Zap

    Identities verified, or form answers received, before you clicked Publish are never replayed. The Zap starts counting from that moment on.

  • An email loop eats your tasks

    If Create Email lands in a place that the same Zap's trigger watches, the Zap sets itself off over and over and your task count drops fast.

  • A big batch gets held back

    When the trigger app suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold it back rather than send it all.

  • No double send from polling

    A polling trigger keeps track of what it has already seen, so the same item cannot start the Zap twice on its own.
Need help

Need help automating Amazon SES with Zapier?

A person reads every message.

FAQ

Amazon SES Zapier integration: FAQ

01Is the Amazon SES Zapier integration free?
No. Zapier classes Amazon SES as a premium app, which keeps it to paid plans and the free trial. The free plan, 100 tasks a month and Zaps of two steps, has no access to premium apps. Inside a paid plan, the trigger and the regular checks for new identities are free; only the emails your Zap sends successfully draw on your tasks. Prices of the plans themselves move often, so look at Zapier's current grid before picking one.
02How many tasks does sending an email through SES use?
Exactly one per message that Create Email hands over successfully. Nothing is charged for the trigger, nor for Zapier looking for new data, however often that happens. A Zap that answers every form entry with one email therefore spends one task per entry. Log each message in a sheet as well and it becomes two per run. If SES refuses the send, the attempt is not billed, and a filter that stops a run early saves the tasks of everything after it.
03Does the Amazon SES trigger fire in real time?
No. New Verified Identity works by polling: Zapier goes to SES on a schedule and asks for identities verified since its last visit. How often depends on the paid plan you hold: every 2 minutes on Professional, every minute on Team and Enterprise. While testing, paid plans also let you trigger a check by hand from the editor. The polling type is fixed by the app's own API, so no setting in Zapier makes it instant.
04What does it take to connect Amazon SES to Zapier?
Three things: an Amazon account with SES set up, a Zapier plan that includes premium apps or a running trial, and access to the account that does the sending. From the Apps page, click + Add connection, sign in to Amazon in the tab that opens and approve the access Zapier asks for. If a colleague owns the SES account, get access from them first. After that, every Zap that sends through SES picks the same connection.
05Can Zapier track opens or bounces on SES emails?
Not with this integration. The catalog stops at one trigger, New Verified Identity, and one action, Create Email. There is no trigger for opens, clicks, bounces or replies, and no search to find a past message. Zapier can send through SES and tell you when an identity is verified, and that is all. If following delivery matters to you, that part has to happen in Amazon's own tools or in another product that exposes those events.
06What if the SES operation you want is not in Zapier?
Then the ready-made catalog cannot do it, two operations being all there is. Start with the getting-started article that Zapier attaches to Amazon SES, to make sure nothing was overlooked. Next, compare what other automation platforms offer for the same service, since each keeps its own list. Anything to do with managing identities or templates can also stay in Amazon itself, with Zapier kept for the sending part only, at least until a platform covers it.
07Zapier, Make or n8n for Amazon SES?
Decide on criteria, not on a ranking. On Zapier the SES catalog is small and quick to set up: one action that sends, one trigger on verified identities, but it sits behind a paid plan. Make and n8n each cover the service with their own operations and their own way of counting usage, which is worth checking against your email volume and how much branching you need. Line up the operations each platform really offers for SES before committing to one.
Same platform

Other docs you might need on this stack.

Browse all integrations