AWS SES n8n INTEGRATION: AUTOMATE AWS SES WITH N8N

The Update a template action allows you to modify existing email templates directly within your n8n workflows. This is particularly valuable when you need to keep your email content synchronized with changes happening elsewhere in your tech stack—like updating promotional copy when a marketing campaign changes or adjusting transactional email text based on product updates.

Key parameters: Credential to connect with (select your configured AWS IAM account from the dropdown menu—required for authentication), Template Name (enter the exact name of the template you want to update—text field, required), and Update Fields (add specific fields to modify within the template by clicking "Add Field"—optional but essential for making actual changes).

Use cases: Automatically update email templates when content changes in a headless CMS, sync promotional copy across multiple template variants, or adjust email footers or legal text across all templates simultaneously.

The Delete a template action removes an email template from your AWS SES account entirely. Use this to clean up obsolete templates, manage template versions, or automate lifecycle management of your email content.

Key parameters: Credential to connect with (your AWS IAM account selection via dropdown—required) and Template Name (the exact name of the template to delete—text input field, required).

Use cases: Automatically remove deprecated campaign templates after a set period, clean up test templates after QA workflows complete, or manage template versioning by deleting old versions when new ones are created.

This action retrieves a list of multiple email templates from your AWS SES account. It's essential for workflows that need to audit, analyze, or iterate over your existing template library—whether for reporting, synchronization, or conditional logic based on available templates.

Key parameters: Credential to connect with (AWS IAM account selection—required), Return All (toggle switch to retrieve every available template—optional), and Limit (numeric input specifying the maximum number of templates to return, defaults to 20—optional).

Use cases: Generate weekly reports of all active email templates, sync template lists with external documentation systems, or check for template existence before creating new ones.

The Get a template action retrieves the complete details of a specific email template, including its HTML content, subject line, and text parts. This is perfect for validation workflows, content backups, or when you need to reference template content in downstream nodes.

Key parameters: Credential to connect with (AWS IAM account dropdown—required) and Template Name (the name of the specific template to retrieve—text input, optional but needed for meaningful results).

Use cases: Backup template content to Google Drive or Dropbox before making changes, validate template content against brand guidelines, or extract template variables for dynamic content mapping.

Create a template lets you programmatically build new email templates in AWS SES. This action is a cornerstone for dynamic email systems where templates need to be generated based on external inputs—like creating localized versions of emails or generating event-specific templates automatically.

Key parameters: Credential to connect with (AWS IAM account—required), Template Name (unique name for the new template—text input, required), Subject Part (the email subject line—text input, optional), Html Part (the HTML content of the email body—text input, optional), and Additional Fields (add custom fields like text-only body parts—optional).

Use cases: Auto-generate campaign templates from marketing brief submissions, create localized email templates for different regions, or build event-triggered templates (webinar confirmations, ticket receipts).

This action sends templated emails through AWS SES, combining your predefined templates with dynamic data. It's the go-to action for personalized transactional and marketing emails where you want consistent formatting with variable content.

Key parameters: Credential to connect with (AWS IAM account—required), Template Name or ID (the template to use for sending—text input, required), From Email (sender email address, must be verified in SES—text input, required), To Addresses (list of recipient email addresses, you can add multiple recipients—required), and Template Data (dynamic data to populate template variables—optional but highly recommended for personalization).

Use cases: Send personalized order confirmations with customer and order details, trigger welcome sequences with user-specific information, or dispatch event reminders with personalized schedule data.

The Send an email action dispatches emails directly without requiring a pre-existing template. It's ideal for one-off communications, system notifications, or workflows where email content is generated dynamically within n8n itself.

Key parameters: Credential to connect with (AWS IAM account—required), Is Body HTML (toggle to indicate if the body content is HTML-formatted—optional), Subject (email subject line—text input, required), Body (email content, plain text or HTML—text input, required), From Email (verified sender address—text input, required), and To Addresses (recipient list, add multiple addresses as needed—required).

Use cases: Send system alerts when workflow errors occur, dispatch internal notifications for team workflows, or create ad-hoc emails based on webhook payloads.

This action modifies existing custom verification email templates used for email address verification flows. It's useful for keeping your verification messaging current without rebuilding entire verification workflows.

Key parameters: Credential to connect with (AWS IAM account—required), Template Name (name of the verification template to update—text input, optional), and Update Fields (specific fields to modify, add as needed—optional).

Use cases: Update verification email branding after a visual refresh, modify redirect URLs for A/B testing verification flows, or adjust verification messaging for seasonal campaigns.

Send a custom verification email triggers a branded verification email to confirm an email address. This replaces the default AWS SES verification email with your customized version, maintaining brand consistency during user onboarding.

Key parameters: Credential to connect with (AWS IAM account—required), Email (the email address to verify—text input, required), Template Name (your custom verification template name—text input, optional), and Additional Fields (extra customization options as needed—optional).

Use cases: Automate verification emails when new users register, trigger re-verification sequences for bounced addresses, or integrate verification into multi-step onboarding workflows.

Retrieves a list of your custom verification email templates. Use this to audit your verification configurations, sync with documentation, or build conditional logic based on available verification templates.

Key parameters: Credential to connect with (AWS IAM account—required), Return All (toggle to retrieve every verification template—optional), and Limit (maximum number of templates to return—numeric input, optional).

Use cases: Audit verification templates across multiple AWS accounts, generate compliance reports for verification email configurations, or sync verification template lists with internal documentation.

Create a custom verification email builds a new branded verification email template. This allows you to maintain brand consistency when AWS SES verifies new sender addresses, replacing the generic AWS verification message.

Key parameters: Credential to connect with (AWS IAM account—required), From Email (sender address for verification emails—text input, required), Template Name (unique name for the template—text input, required), Template Content (HTML/text content of the verification email—text input, required), Template Subject (subject line—text input, required), Success Redirection URL (where to redirect after successful verification—text input, optional), and Failure Redirection URL (where to redirect if verification fails—text input, optional).

Use cases: Set up branded verification for new product launches, create regional verification templates with localized content, or build verification templates with custom redirect flows.

This action retrieves details of a specific custom verification email template. It's useful for validation, backup, or when you need to reference verification template content in other workflow nodes.

Key parameters: Credential to connect with (AWS IAM account—required) and Template Name (name of the verification template to retrieve—text input, optional).

Use cases: Backup verification templates before making changes, validate verification content against compliance requirements, or extract redirect URLs for testing purposes.

Removes a custom verification email template from your AWS SES account. Use this for cleanup, version management, or when decommissioning verification flows.

Key parameters: Credential to connect with (AWS IAM account—required) and Template Name (the verification template name to delete—text input, required).

Use cases: Clean up deprecated verification templates, remove test verification configurations after QA, or manage verification template versions by deleting old iterations.