SES email actions
Use an SES email action when you need to author the subject and body directly in Builder, using a verified sender domain configured for the library. It supports Liquid values, Markdown by default, raw HTML when necessary, multiple recipients and real file attachments.
This action is useful for tailored operational emails. It carries more responsibility than a provider-managed template: the service author owns the clarity, accessibility and safety of the message content.
Prepare the sender identity
The From address domain must be a verified email domain available in the library’s email identities. Configure and verify it before building the action. Set the From address local-part to the part before the @, for example notifications, and optionally add a friendly From display name.
Use a recognisable sender and a working Reply-to address whenever people may reasonably need to respond. Do not use a personal mailbox or an unmonitored address for a service that invites questions.
Configure the email
- Open Page actions and add an SES email action.
- Set a clear Action ID and name.
- Choose the verified sender domain and supply the sender local-part.
- Add the display name and reply-to address where appropriate.
- Set the recipient in To addresses; add CC or BCC only for a documented business reason.
- Write the subject and body, using Liquid values where required.
- Add attachments and optional filenames if the message needs them.
- Choose a trigger after validation or completion, then test in QA.
Separate multiple addresses with line breaks. Confirm that each recipient is expected to receive the message; CC and BCC are powerful but easy to misuse.
Author the subject and body
The Subject line and Body support Liquid. Use a subject that explains the purpose without exposing sensitive details in notification previews. Keep the body readable in a plain-text context as well as an HTML-capable mail client.
By default, the body is written in Markdown and converted to HTML. Prefer Markdown for headings, lists, links and emphasis; it is easier to maintain and produces a more consistent structure. Turn on Send body as raw HTML only when Markdown cannot express the required content and the HTML has been reviewed for correct, accessible markup.
flowchart LR
A[Verified sender identity] --> B[Sender and reply-to]
C[Service values] --> D[Liquid subject and Markdown body]
B --> E[SES email action]
D --> E
F[Optional attachments] --> E
E --> G[Message delivered]Do not rely on colour, images or complex tables to communicate essential information. Use descriptive link text and make the action requested of the recipient clear.
Manage recipients and attachments
Use To addresses for people who need to act on or know about the message. Use CC and BCC sparingly, with an approved reason and appropriate privacy consideration. A Liquid expression that can resolve unexpectedly must be tested with blank and unusual inputs.
Choose uploaded file fields or successfully generated document outputs for Attachment field ID. Optionally provide a matching Attachment filename for each attachment; keep names short, meaningful and safe for the recipient. A filename override must align with the corresponding attachment in the same order.
Generate documents before sending the email. Test missing files and a route without attachments so the service handles both deliberately.
Test the final message
Review a delivered QA email on desktop and mobile. Check sender, reply-to, recipient list, subject, Markdown rendering, Liquid substitutions, links, attachment names and the outcome when an optional field is blank. Also test returning to the relevant page to ensure the trigger does not send unintended duplicates.
Important: Keep personal and sensitive information out of subjects, recipient lists and unnecessary copies. An email is not a secure store for the full contents of a service submission.