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.
A send email action's input mapping is internal to Wix, so you generate it rather than build it yourself.
To add a send email action to an automation:
action, such as its emailType, notificationTopicId and recipients, and optionally the email content with MJML as its editorType. To email the contact who triggered the automation, set recipients.recipientType to TRIGGER_CONTACT and specify the path of the trigger payload schema property marked with "identityType": "contact" as recipients.triggerContactOptions.contactIdPath. Without recipients, the email goes to the site owner. A BUSINESS_TRANSACTIONAL email needs a transactional notificationTopicId.APP_DEFINED action whose appDefinedInfo.appId, appDefinedInfo.actionKey and appDefinedInfo.inputMapping are the appId, actionKey and inputMapping from the response. Don't modify the input mapping, and use it for this action only: actions that share an input mapping share their email content, so removing one of them deletes the content the others send. The email content goes live when the automation is activated, and stays a draft until then.An existing automation's email goes to the recipients it was set up with, such as the contact who triggered the automation. You can send it to a group of contacts instead, such as every contact with a VIP label.
To send an automation's email to contacts with a label:
id and the ID of the APP_DEFINED action whose appDefinedInfo.actionKey is triggered-emails.id of the provider that selects contacts by label.automationEmailAction.recipients, set recipientType to CUSTOM and add an audience to customOptions.audiences with the provider's ID as audienceProviderId and the label IDs in audienceProviderData. Send only recipients, so the action's other settings stay as they are. The email goes to the labeled contacts from the automation's next run.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:
To preview and test email content:
customPayload that represents the data the action would receive when the automation runs. This renders the content as HTML without sending anything.html and emailSubject in the response.toEmail address and the same customPayload, to receive an actual test email rendered with that data.By default, a send email action uses the site's default sender details, or a Wix-branded fallback if the site has none. To send from a specific sender instead, assign a sender you've already created with the Sender Details API.
To assign a sender to a send email action:
Last updated: 26 October 2026