AWS SES n8n integrationAutomate AWS SES with n8n.

SES asks any new sender address to confirm it belongs to you. This operation stores the template used for that confirmation message, so the ask carries your wording instead of a generic one.

• From Email: the address the custom verification email is sent from.
• Template Subject: the subject line of that verification email.
• Success Redirection URL: where the recipient lands once the address is verified.
• Failure Redirection URL: where the recipient lands when verification does not succeed.
• Template Content: the body, HTML allowed, with the total email size kept under 10 MB.

Verification templates accumulate fast once two or three wordings have been tested. This operation removes one from the account, which also removes the risk of a later send picking stale copy by name.

• Template Name: the name of the custom verification email template to remove; feed it from a previous step with {{ $json.templateName }} rather than typing it twice.

Reading one template back returns it as SES currently stores it, which is the only reliable way to know what an address is really being sent.

• Template Name: the name of the custom verification email template to read.

Rather than one template by name, this returns the custom verification email templates that exist on the account, which is what an inventory job needs.

• Return All: on, n8n walks the API pages and brings back every template; off, it stops at Limit.
• Limit: the maximum number of templates returned when Return All stays off.

Here the template stops being an object and starts being an email: the address receives the confirmation request and gets added to the list of identities once it goes through.

• Email: the address to verify, often {{ $json.email }} from the form or record upstream.
• Template Name: the custom verification email template to use for this send.
• Configuration Set Name: in Additional Fields, the configuration set to use when sending the verification email.

The verification wording ages like any other copy: a redirect points at an old landing page, the subject line no longer matches the product. This operation edits the stored template instead of deleting and recreating it.

• Template Name: the template being edited.
• From Email, Template Subject and Template Content: in Update Fields, the sender, the subject line and the body.
• Success Redirection URL and Failure Redirection URL: the two destinations after a verified or failed address.

This is the workhorse: subject and body are built in the workflow and handed to SES as is, with no stored template involved.

• Subject and Body: the message itself, usually assembled from earlier nodes.
• From Email: the sender address, such as admin@example.com.
• To Addresses: the recipients.
• Is Body HTML: on when the body carries markup, off for plain text.
• Cc Addresses, Bcc Addresses, Reply To Addresses and Return Path sit in Additional Fields, the last one collecting bounces and complaints.

Same delivery, opposite split of responsibilities: SES holds the wording, the workflow only supplies the values that change from one recipient to the next.

• From Email: the sender address, the one required field here.
• Template Name or ID: picked from the list, or set with an expression when the template depends on the data.
• To Addresses: the recipients of this send.
• Template Data: the Key and Value pairs that fill the template placeholders.

Before any templated send there has to be a template. This operation registers one in SES under a name the workflow will call later.

• Template Name: the name of the template, and the handle every later operation uses.
• Subject Part: the subject line of the email.
• Html Part: the HTML body.
• Text Part: in Additional Fields, the body shown to recipients whose email client does not display HTML.

Retiring a piece of wording is a one-field job, and doing it from a workflow beats doing it by hand three environments in a row.

• Template Name: the name of the template to delete, required, so a wrong value removes the wrong wording.

Fetching a single template by name returns what SES holds for it, which is how a workflow checks the live wording instead of trusting a copy in a document.

• Template Name: the name of the template to read, required.

The list view of the same resource: every template on the account comes back in one execution, ready to be filtered downstream.

• Return All: on, n8n follows the API pages until no template is left; off, the run stops at Limit.
• Limit: how many templates come back at most when Return All is off.

Copy changes more often than workflows do. This operation rewrites a stored template in place, and every send that follows uses the new version without any workflow edit.

• Template Name: which template gets rewritten, required.
• Subject Part, Html Part and Text Part: in Update Fields, the subject, the HTML body and the plain text fallback.