Amazon SES Integrations: Native, Zapier, and API
Amazon SES is the AWS-native email sending service, and its integration surface reflects that heritage: deep, first-party wiring into the AWS ecosystem (Lambda, SNS, EventBridge, CloudWatch, Firehose, Route 53, Pinpoint), a SES v2 REST API with official SDKs in 10+ languages, and a long tail of 9,000+ Zapier-mediated connectors for SaaS tools that do not speak AWS natively. Unlike SendGrid, Mailgun, or Brevo, SES ships very few polished third-party plugins of its own — the assumption is that you are already in AWS, or you route through Zapier, WP Mail SMTP, or your framework’s SMTP adapter.
At a glance
Integrations directory
The 30 integrations below are grouped by how you actually wire them: native AWS services (direct IAM + SDK), CMS & websites, forms & lead capture, e-commerce & CRM, marketing & newsletters, support & backends, and DevOps & automation. Full Zapier catalogue lives at the official Amazon SES on Zapier page; AWS-service wiring is documented at SES monitoring & event publishing.
AWS services (7)
Invoke SES v2 SendEmail directly from Lambda functions using the AWS SDK — the canonical serverless pattern for transactional email in AWS.
Receive SES bounce, complaint, and delivery event notifications through SNS topics — the standard way to keep your suppression list and reputation in sync.
Route SES event destinations into EventBridge for downstream automation, cross-account fan-out, or SaaS integration via partner event sources.
Publish SES send, bounce, complaint, and reputation metrics to CloudWatch dashboards and alarms — the minimum viable observability setup for production SES.
Stream SES event destination data into Firehose for S3, Redshift, or OpenSearch analytics — useful when CloudWatch retention is not enough.
One-click DKIM CNAME and MAIL FROM MX/SPF record creation for SES-verified domains hosted in Route 53 — skips manual DNS editing entirely.
Pinpoint uses SES as its underlying sending channel for email campaigns — when you send from Pinpoint, you are already paying and configuring SES.
CMS & websites (4)
Route WordPress transactional email through SES via WP Mail SMTP, Post SMTP, or a direct SES v2 API call — the most common way to fix WP’s default wp_mail.
Configure Ghost to use SES SMTP for member and newsletter email — a common combo for high-volume Ghost publications on a per-1K cost basis.
Trigger SES transactional emails from Wix site events (form submissions, store orders, member sign-ups) through a Zap.
Send SES emails when Webflow forms are submitted or CMS items are created — useful for Webflow projects that outgrew the built-in email limits.
Forms & lead capture (6)
Send WPForms submissions as SES emails through a Zapier workflow — useful when WP Mail SMTP is not viable.
Deliver Gravity Forms notifications via SES with a Zap when the built-in Gravity SMTP add-on is not enough.
Trigger SES emails from new Jotform submissions with per-form routing rules driven by Zapier.
Send SES emails when a Typeform response is captured — handy for lead-magnet follow-ups on a low per-email budget.
Route Formsite entries to SES for transactional delivery through Zapier.
Follow up on Unbounce landing-page leads with SES-sent transactional email through a Zap.
E-commerce & CRM (3)
Send order and shipping notifications through SES from Shopify events — a common way to sidestep Shopify Email limits for high-volume stores.
Trigger SES transactional messages from HubSpot contact and deal events — useful when HubSpot’s own transactional email add-on is out of scope.
Send SES emails on new Salesforce records or updates via Zapier, keeping Salesforce as the source of truth.
Marketing & newsletters (4)
Sendy is designed from day one to send newsletters through the SES API — the reference low-cost bulk-email stack at roughly $0.10 per 1,000 recipients.
Sync Mailchimp audience events to SES transactional sends — often used to keep marketing in Mailchimp while transactional runs on SES.
Trigger SES emails from ActiveCampaign automations when the built-in transactional email add-on does not fit the workflow.
Fan out Brevo contact events into SES sends — useful when you want Brevo for marketing and SES for high-volume transactional.
Support & backends (3)
Send SES notifications for new Zendesk tickets or status updates, keeping your ops mailbox on SES pricing.
Bridge Zoho Mail workflows with SES send actions via Zapier for cross-suite email routing.
Trigger SES emails from Firestore document changes — a simple way to bolt transactional email onto a Firebase back-end without adding another provider.
DevOps & automation (3)
Notify teams via SES on GitLab pipeline or issue events — a lightweight alternative to running a full alerting stack.
Send SES build-status emails from Jenkins jobs when you don’t want Jenkins itself holding SMTP credentials.
Trigger SES sends from any generic webhook or HTTP source — the catch-all when no dedicated Zapier connector exists.
Frequently asked questions
Does Amazon SES have an official WordPress plugin?
AWS does not publish its own WordPress plugin. In practice, the two dominant options are WP Mail SMTP (which has a first-class “Amazon SES” mailer that signs requests with SigV4) and Post SMTP, both of which take an IAM access key and secret and call the SES v2 API directly. A plain SMTP plugin pointed at email-smtp.{region}.amazonaws.com on port 587 also works, but you must generate SES SMTP credentials from an IAM user first — your AWS access key will not authenticate against the SMTP endpoint.
How do I connect Amazon SES to Shopify or WooCommerce for transactional email?
Shopify does not expose an outbound SMTP configuration for its own order emails, so you cannot route Shopify’s built-in notifications through SES directly. The usual pattern is to disable the Shopify notification for a given event, then fire a Zap on the same Shopify trigger that calls the Amazon SES Zapier app. WooCommerce is easier: it uses WordPress’s wp_mail, so installing WP Mail SMTP with the SES mailer will route order and shipping emails through SES automatically.
Can I use Zapier to trigger Amazon SES sends from form submissions?
Yes. The Amazon SES app on Zapier exposes a Send Email action that accepts From, To, subject, HTML/text body, and reply-to fields. You supply an IAM access key with ses:SendEmail permissions once when you connect the account, then any of the 9,000+ Zapier-integrated apps (Typeform, Jotform, WPForms, Google Forms, Airtable, etc.) can trigger it. Note that Zapier signs each call as your IAM user, so the sending identity must be verified in the same SES region.
How do I stream SES bounce and complaint events into Slack or a webhook?
Attach a configuration set to your sending identity, then add an event destination of type SNS (fastest to Slack via AWS Chatbot or a Lambda subscriber), EventBridge (for cross-account routing), or Kinesis Data Firehose (for archival to S3). From SNS you can either subscribe a Lambda that POSTs to a Slack incoming webhook, or use AWS Chatbot for native Slack integration. Bounce and complaint events are mandatory to process at scale — SES reviews accounts at 5% bounces or 0.1% complaints and can pause sending at 10% and 0.5% respectively.
How does Amazon Pinpoint relate to Amazon SES?
Pinpoint is a customer engagement product that sits on top of SES for its email channel. When you send an email campaign from Pinpoint, the actual delivery is performed by SES using your verified identities, and the sending rate and reputation are governed by your SES account limits. You get billed for both: Pinpoint per targeted endpoint and SES per delivered email. If you only need email, using SES directly is cheaper; Pinpoint adds value when you need segmentation, journeys, or multichannel (SMS, push, in-app) alongside email.
Which AWS services integrate natively with SES event destinations?
An SES event destination can publish to CloudWatch (metrics and alarms), SNS (fan-out to Lambda, HTTPS webhooks, email, or Chatbot), EventBridge (rules-based routing across accounts and to SaaS event buses), Kinesis Data Firehose (streaming to S3, Redshift, OpenSearch, or Splunk), and Pinpoint (as a Pinpoint event source). Every send, delivery, open, click, bounce, complaint, reject, rendering failure, subscription, and delivery-delay event can be routed to one or more of these destinations per configuration set.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
