Amazon SES

Send transactional and templated email through Amazon SES v2. Agents deliver receipts and notifications, manage reusable Handlebars-style templates, and broadcast personalized email in a single batch.

4 actions available

Upstream system signals a transactional event (order placed, invoice issued, payment failed)

Agent assembles the template-data object from the upstream event

Agent confirms the From Address is a verified SES identity

Agent calls Send Templated Email with the template name and template data

Agent inspects the response for the messageId

Send log appended to the audit spreadsheet for retention

Bounce or complaint spikes get routed to the deliverability owner for review

What This Integration Enables

Agents send plain-text or HTML email through Send Email, with at least one of Text Body or HTML Body required and both supported for multipart messages. Templated sends use Handlebars-style `{{variable}}` substitution in subject and body parts; template data is supplied as plain JSON and serialized to the format SES expects. Send Bulk Templated Email applies a default template-data object to every entry, with optional per-entry replacementData overrides, and returns a per-recipient result with messageId, status, and error. Verified senders are selectable through the List Identities dictionary, and templates through the List Templates dictionary. The connector covers the send surface; the surrounding flow decides what content goes out, who receives it, and what counts as an exception worth pausing for.

Without FlowRunner

Email logic in app code Each service that sends mail rebuilds template handling and verified-identity selection

Bulk personalization in shell scripts One-off scripts loop over CSVs and call SES per row, with no per-recipient retry visibility

Templates managed outside the workflow Updates to a transactional template require a developer commit, not a workflow change

With FlowRunner

Templated send as a flow step Send Templated Email is a node with the template name selected via the List Templates dictionary

Bulk in one batch Send Bulk Templated Email handles up to many recipients per batch with per-entry replacementData and per-recipient status

Templates owned by the workflow Create Email Template lets the workflow manage template lifecycle alongside the send logic

Use Case Scenarios

Branded Transactional Receipt

A finalized invoice in Stripe fires the flow. The agent assembles the template-data object with the customer name, invoice number, line items, and total, then calls Send Templated Email against a "receipt-v2" template. The customer gets a branded, personalized email with the invoice details substituted in. The agent logs the messageId in a spreadsheet for the audit retention window the finance team requires.

Bulk Personalized Campaign

A contact list lives in Airtable. The agent calls Find Many Records to fetch the segment, then calls Send Bulk Templated Email with the recipients array, a default template-data object, and per-entry replacementData overrides for personalization. The response includes a per-recipient result with messageId, status, and error. The agent writes any errored recipients into a review tab so the operator can resolve before the next send.

Workflow-Owned Template Lifecycle

When marketing wants a new welcome message, the agent calls Create Email Template with the subject, HTML body, and text body. Subsequent flows reference the template name when calling Send Templated Email or Send Bulk Templated Email. Template ownership lives in the workflow, not in a developer branch, so the operator can ship changes without a code release.

Human-in-Loop Highlight

A bounce or complaint spike is the exact signal that needs a human, not another send. The agent watches the per-recipient status field returned by Send Bulk Templated Email and the messageId outcomes from Send Templated Email. When the bounce or complaint rate crosses the configured threshold, the agent pauses outbound sends and posts to the deliverability owner's channel: "Bounce rate at [percent] across [count] sends in the last [window]. SES sender reputation at risk. Pause outbound, throttle, or continue?" The operator decides. The agent does the durable thing: it stops sending before the SES sender reputation takes a hit that takes weeks to repair.

Agent processes routinely

Detects that takes weeks to repair

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

4 actions

Send

Send Email Sends a plain-text or HTML email from a verified SES identity. Requires at least one of Text Body or HTML Body; both may be supplied for multipart messages.
Send Templated Email Sends a templated email with per-message variable substitution. The template is selected via the List Templates dictionary; template data is supplied as plain JSON.
Send Bulk Templated Email Sends a templated email to many recipients in a single batch. Applies Default Template Data to every entry, with optional per-entry replacementData overrides. Returns a per-recipient result with messageId, status, and error.

Templates

Create Email Template Creates a reusable SES email template with Handlebars-style variable substitution. Subject and body parts support `{{variable}}` placeholders.

Start building with Amazon SES

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us