Prepare an email automation
An automation starts from an event or timing choice. Plan who should enter, what they should receive and when before creating a workflow. Keep this separate from preparing a one-off campaign.
Find the automation area
- Open your eMailSense dashboard from Builder and choose Automation. The campaign-type chooser also links to Manage Automations.
- Use the name search, Active/Inactive status filter and date/name sort to find an existing workflow. Check its identity and actual state before making changes.
- For a new workflow, choose New Automation. An empty list can instead offer Create your first automation.
- Review the available trigger choices before choosing one. The next Configure step is separate from the final Create automation action.
Prepare the common fields
- Choose a trigger that matches the event you intend to use.
- Enter a recognisable Automation name, such as “New subscriber introduction”. This name helps your team identify the workflow.
- Review the intended Mailing list and optional Segment. Check actual membership and the event that will qualify someone to enter.
- Review the fields specific to that trigger below. Check any date, time, tag or subscriber-field values before proceeding.
- Use Back to return to trigger selection if the choice is wrong. Review the resulting fields again after changing triggers.
- Use Create automation only when the intended configuration is ready. Inspect the actual resulting workflow, message content and status before allowing it to send. Do not assume creation means the message and release settings are complete.
To leave preparation without submitting the form, use the Automations breadcrumb before Create automation. Check the list afterwards. Leaving this form is separate from disabling a previously saved or active workflow.
Review each trigger’s fields
| Trigger | What to prepare and check |
|---|---|
| Welcome new subscribers | Review the mailing list and optional segment for the intended subscription event. Compare this plan with the list’s separate welcome-email choice to avoid an unintended overlapping message. |
| Say goodbye to subscriber | This is the unsubscribe-related choice. Review the intended purpose, eligible audience and suppression handling with support before relying on it. Do not use it to reverse a subscriber’s choice or assume the label establishes who will receive a message. |
| Say Happy birthday | Review Date of Birth field, Send how many days before? and Send at time. Check actual date-field data and the intended timing before using an offer. |
| Subscriber added date | Review Delay (days after) and Send at time. Confirm how this trigger interprets the subscriber’s added date before promising a particular anniversary or delay. |
| Specific date | The configuration form shows Trigger date and Send at time. Check the intended date and audience. If you need a different date for every subscriber, confirm the appropriate setup rather than assuming this fixed-date field provides it. |
| API 3.0 | Use this route for an intended integration-triggered workflow. Review the supplied integration information with the person responsible for that integration. A displayed integration address does not establish that the connection, event or sending workflow has been tested. |
| Weekly recurring | Review Days of the week and Send at time. Check each intended day and the relevant time zone before relying on the schedule. |
| Monthly recurring | Review Days of the month and Send at time. The day choices run from 1 to 28. Confirm the appropriate approach if you need the 29th, 30th, 31st or the last day of each month. |
| Tag based | Review the intended Tags and what will add them to the intended contacts. Check the exact tag values and entry behaviour before applying tags to an audience. |
| Remove Tag | Review Tags for the intended removal event. Keep this separate from the Tag based choice, and check what process will remove the tag. |
| Contact Attribute Update | Review Subscriber field and New value. Check the actual field and value you intend to match. Confirm matching and repeat-entry behaviour before relying on patterns or repeated updates. |
| Abandoned Cart Reminder | Review the intended list and optional segment. Confirm the shop connection, eligible cart event, audience and timing before relying on reminders. This choice being visible does not establish that your webshop is connected or that cart events reach it. |
Example: introduce new subscribers
- Choose Welcome new subscribers.
- Name the workflow clearly and check the intended mailing list and optional segment.
- Compare the list’s welcome-email setting with the messages planned for this workflow.
- Prepare a short introduction and useful next action, such as exploring the relevant collection. Check sender identity, links and any offer conditions.
- Review the actual saved workflow and release choices. Use controlled test recipients and events before allowing an intended audience to enter.
Example: a weekly shop update
Plan the intended weekdays, time, audience and message content before choosing Weekly recurring. Check which time zone applies and whether recipients can enter again. A weekly trigger does not itself establish that changing product information will be inserted automatically into each message.
Before allowing a workflow to send
- Check the actual workflow identity, trigger and state.
- Review the mailing list, segment and subscriber status rules.
- Review message content, sender identity, links and any offer dates.
- Check timing, time zone, repeat-entry rules and what happens to existing contacts.
- Review a controlled test event and actual received message, then inspect the workflow’s recorded result.
- Identify the current stop/pause controls and what they affect before releasing the workflow.
If the expected message does not arrive
Check the workflow’s actual state, intended event, subscriber identity/list/segment, relevant field or tag values and expected time. Retain the exact workflow name, event time and displayed result for support. Do not repeatedly change tags, unsubscribe/resubscribe a contact or trigger an integration to force another attempt without understanding whether that could create duplicate entries or sends.
If you selected the wrong trigger
During unsaved preparation, use Back and review the correct trigger’s fields. For an existing workflow, inspect its actual state and available controls first. Do not assume deleting, closing or changing a screen recalls messages already sent or reverses events that already occurred.
Prepare an email list · Prepare a one-off campaign · Review the sending domain.
