Automation Email Action: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

Edit a preinstalled automation's email content for the first time

A preinstalled automation starts out sharing its email content with every other site running the same automation. To make the content specific to a site, you update it once, which automatically creates the site's own copy.

To edit a preinstalled automation's email content for the first time:

1. Call Get Email Content for the automation and action. This works even if the site hasn't edited the content yet, and returns the shared, template content.
2. Change the fields you want to update in the returned content, keeping the rest as retrieved. Set Email Content replaces the stored content in full, so anything left out is cleared rather than kept.
3. Call Set Email Content with the updated content. This creates the site's own copy of the content and publishes it.

Preview and test email content

To preview and test email content:

1. Call Preview Email Content for the automation and action, passing a customPayload that represents the data the action would receive when the automation runs. This renders the content as HTML without sending anything.
2. Review the rendered html and emailSubject in the response.
3. Call Send Test Email with a toEmail address and the same customPayload, to receive an actual test email rendered with that data.