How to create and use automations
An automation responds for you to what your subscribers do. When someone subscribes, opens an email, or has a birthday, it acts at that very moment and independently for each person.
It allows you to welcome someone who has just subscribed, follow up with someone who did not open your last send, congratulate someone on an anniversary, or reactivate someone who has not read you for months. In addition to sending messages, it can update a subscriber’s data, move them to a list, or notify another of your systems.
Every automation has two parts. The trigger, which determines who enters and when, and the steps, which are the actions that are executed next. We call the path each person follows their journey, and each person moves through their own at their own pace.
It is configured once, and from then on it works on its own.
In this article:
- Create your first automation
- How an automation is defined
- Where your automations are
- Create an automation
- Choose the trigger
- Add steps
- Save, review, and confirm
- Activate and stop
- Check the statistics
- Warnings, stopped subscribers, and cancellations
- Check a subscriber’s journey
- The same subscriber in several lists and channels
- Channel availability
- Credit consumption
- Customize messages
- What is configured outside the editor
- Duplicate, copy, and delete
- Operations available via API
- Migrate old automations
- Migrate autoresponders
Create your first automation
Before going into the details of each option, it is worth building a simple automation from start to finish. The rest of the article then serves as a reference.
What we are going to build
We are going to build a welcome sequence with follow-up, which is the most common case and uses almost all the pieces you need to know. The journey each subscriber will follow is this.
- Someone subscribes to your list.
- They receive a welcome email immediately.
- We wait three days.
- If they did not open that email, we send them a reminder. If they opened it, we do not bother them.

Create the automation
You can access Automations from the side menu. When you click the New automation button, you can start from scratch or choose one of the predefined templates with preconfigured steps from the gallery. In this case, choose the Start from scratch option.

This creates a new empty automation in draft mode. While it is in draft, you can apply all the changes you need without affecting subscribers. It will not be operational until you confirm the changes and activate it.
Choose who enters
Clicking the first item in the journey opens the trigger panel, which always occupies that position because it decides who enters. Under Trigger type, choose New subscription and, below, select the email channel and the list you want to apply it to.
With this, you have already defined the audience, and each new subscription that occurs on that list will start a new journey. It is advisable to choose the list carefully, since it cannot be changed once you publish the automation for the first time.

Add the steps
A + button appears below the trigger. Each time you click it, you can choose the step you want to add at that point in the journey.
The welcome email
Click the + button, go to Action, and choose Send email with template. The step is added to the journey and its configuration opens in the panel on the right.
There you choose the template, write the subject, and specify the sender. The sender must be one of your verified addresses, and if you do not have any yet, the field itself links you to the screen where you can register them.
The template must include the unsubscribe link, just like in a normal campaign. If it does not, when you confirm the changes we will notify you so that you can edit it and add it.
The wait
Click + again, this time below the email, and go to Wait to choose Wait for a period of time. Set the wait time to three days.
The condition
Add a third step with the + button, go to Condition, and choose Decide by behavior, which looks at what the subscriber has done with your sends. As the event to monitor, choose Does not open the campaign, and as the campaign, the welcome step you have just created. You can point to a step in the automation itself; you do not need a separate campaign.
Two branches come out of the step, one for those who meet the condition and one for those who do not. In the yes branch, add another Send email with template with the reminder. The other branch remains empty, because there is no need to write again to someone who has already opened the first email.

Confirm the changes
As you design, the draft is saved automatically and the header tells you at all times whether it is saved.
When the journey is finished, click Confirm changes in the header. Before applying anything, the configuration is checked to make sure it is complete.
If any data is missing, a list of points to review appears, grouped by step, with warnings such as “subject missing” or “choose a template.” Clicking any of them opens the field causing it directly.
Once everything is correct, the draft is saved as the first version of the automation. Confirming does not put it into operation; that is done in the next step.

Activate the automation
The last step is to activate it with the switch in the header, the one that shows Active or Stopped. Confirmation is requested before applying the change, and from that moment, each person who subscribes to the list will start their journey. It can also be activated from the automation menu in the list, without opening it for editing.
To activate it, the automation must have at least one confirmed version and your account must have a paid plan. Free accounts can create and design automations, but not activate them.
The same switch stops it. When stopping it, you are asked what to do with the subscribers who are already inside: they can finish their journey or exit immediately.
How an automation is defined
Every automation consists of a trigger and a series of steps.
- The trigger determines what makes a subscriber enter. It can be a signup to a list, the opening of an email, or the arrival of a specific date. It always comes first.
- The steps are the actions that are executed next, such as sending an email, waiting for a certain amount of time, or splitting the path in two according to the subscriber’s behavior. You can chain together as many as needed.
We call the path each person follows from the moment they enter until they exit their journey. Each subscriber moves through their own independently and at their own pace, so two people who enter on different days do not affect each other. Entry is immediate, within seconds of the event that defines the trigger occurring.
The same person can be inside several automations at the same time. If you have two automations listening to the same list, a new subscription starts a journey in each one, and both progress without interfering with each other.
Where your automations are
The Automations section of the side menu gives access to two screens. Home summarizes the account activity with six indicators.
- Active automations. The ones running at this moment.
- Subscribers (last 30 days). How many subscribers have entered during the last month.
- Completion rate. What proportion of those who enter reach the end of the journey.
- Stuck runs. How many are waiting for you to resolve an issue.
- Runs in progress. How many subscribers are inside an automation right now.
- Canceled (last 30 days). How many left before finishing.
Recent automations appear below. The second entry in the menu opens the full list, with a search box by name.
On both screens, each row shows the name, the creation date, the status, the version in use, the pending changes, and how many subscribers it has in progress and stuck, as well as the actions menu. The Pending changes column warns that there is a draft that has not been confirmed. In the full list you can sort by any of those figures, which is convenient for finding the automations with stuck subscribers.

Automations created with the previous version appear in this same list with the Old badge. Their menu offers Open in old editor and, if they have already been migrated, Go to new version.
Create an automation
Clicking New automation opens the gallery of preconfigured templates, which you can use as a starting point instead of designing the entire journey. The templates are grouped by category and can be filtered by Onboarding, Engagement, Lifecycle, or E-commerce, or you can keep the filter on All.
The gallery only shows templates compatible with your account, so a template with an SMS step does not appear if you do not have that channel. To design it from the beginning, click Start from scratch and a blank automation is created.

In both cases, a draft is created. The automation does not start running until you confirm the changes and activate it.
Choose the trigger
The trigger panel starts with its Type. There are twelve available, grouped into four families according to what starts them.

By lists
- New subscription. A signup to the selected list. If the list requires email confirmation, the subscriber enters when they confirm, not when they register. Anyone who signs up by their own decision enters, and so does anyone who appears on the list for the first time. Someone you add yourself does not enter, whether from their record, through the API, by importing a file, or with a step from another automation.
- Subscriber updated. An existing subscriber starts meeting the conditions you define. For example, their city field changes to Madrid.
By dates
- Specific date. A specific day and time, only once.
- Anniversary (once a year). Repeats annually on the date in a field. It is suitable for birthdays or signup dates. The trigger can occur on the same day, or a number of days before or after, allowing you to congratulate in advance.
- Relative date. A number of days or months before or after the date in a field. For example, seven days after the signup date, or one month before an expiration date.
In date triggers, the specified time is interpreted in your account’s time zone. All three support all three channels, so a birthday can be congratulated by email, SMS, or WhatsApp.
By interactions
- Email open and Email click. The click can be limited to a specific link in the campaign.
- SMS click and WhatsApp click. They are equivalent to an email click, on the links or buttons in the messages you have sent through those channels.
- WhatsApp read. Triggers when Meta confirms that the recipient has read the message.
- Survey answered. The survey must request the email address. Without that data, it is not possible to identify the respondent and the automation does not trigger.
By integrations
- External event (webhook). Your own system notifies Acumbamail and the subscriber enters. This is the right option for events that occur outside Acumbamail and that you detect yourself. The same webhook can feed several automations, which are distinguished by the event name.
The entry channel
Under the type, you choose the channel and list on which the automation operates. The channel can be email, SMS, or WhatsApp, depending on what your plan includes. A channel you have not subscribed to cannot be selected (see channel availability).
The trigger channel determines which data is used to identify the subscriber throughout the entire journey. Someone who enters by email is identified by their address, and someone who enters by phone is identified by their number.
That choice is maintained throughout the entire journey, even if a specific step operates on another list or another channel (see the same subscriber in several lists and channels).
Allow re-entry
By default, each subscriber enters only once. Even if they unsubscribe and subscribe again, they do not start a new journey. To allow repetition, there are two settings in the trigger.
- Allow a subscriber to re-enter. Enables repetition.
- Wait between entries. Appears when you check the previous box. Indicates the minimum number of days that must pass. With a value of zero, the subscriber can re-enter as soon as the previous journey ends.
This option is not offered for date triggers, which repeat on their own or run only once.
In the Subscriber updated trigger, re-entering means something more specific. Time passing is not enough. The subscriber has to stop meeting the conditions and meet them again. Someone who meets them without interruption does not re-enter however long you wait. The wait between entries is still a minimum, and with a value of zero they re-enter as soon as they meet the conditions again.
Allowing repetition conditions what a behavior condition can monitor. If the same subscriber can receive the same email several times, there is no way to know which of those times an open or a click corresponds to. That is why, when the trigger repeats, a condition cannot monitor a send from the automation itself.
Include existing subscribers
The trigger acts on those who meet the condition from that moment onward. To also include those who already meet it, there is a checkbox, with a different name depending on the trigger.
- Apply to current subscribers. In triggers that work on a list.
- Apply to those who already interacted. In open and click triggers, where those who already opened or clicked the reference campaign enter.
They enter only once, at the moment you request it. Before checking it in an automation that sends messages, it is worth assessing the scope, because a list of ten thousand subscribers starts ten thousand journeys.
Add steps
Click the + button located between two steps, or below the last one, to add a new one. The menu groups them into three families.

Action
They perform a specific task.
- Send email with template. An email generated from one of your templates, with its subject and preheader. The template can be edited without leaving the step. It supports link and open tracking, so the send appears in your reports like any other campaign.
- Send plain email. A text email, without a template. Useful for short notices.
- Send SMS. A text message to the subscriber’s phone. Requires an SMS list and a verified sender. If the subscriber is not on that list or has no phone, the step is skipped and recorded in its statistics.
- Send WhatsApp. A WhatsApp message based on a template approved by Meta. WhatsApp lists are managed separately, so the subscriber must also be on the list you choose here.
- Send me an email. A notification addressed to you, not to the subscriber. It lets you know when someone reaches a certain point in the journey. It indicates which subscriber and which step it is, and does not spend sending credits.
- Add to a list. Subscribes the subscriber to another list and copies fields that match by name. It can be a list from another channel, in which case you must indicate which field contains the corresponding phone number or email.
- Remove from a list. Removes them from the list while preserving their consent. It is reversible and does not affect the rest of the lists. If the subscriber was not on it, the step is skipped.
- Move to another list. Subscribes them to the destination list and removes them from the source list in a single step. Only between lists of the same channel. If the subscription is not applied, they are not removed from the source list, so they do not end up outside both.
- Unsubscribe. Removes the subscriber’s consent. It applies only to email subscribers. Unless you have configured otherwise, the unsubscribe applies to all your lists, not only the one in the step. It is different from removing them from a list.
- Update field. Modifies the value of a subscriber field. It allows you to record which points of the journey they have passed through. The value is fixed, the same for everyone who passes through there.
- Webhook. A call to an external address to notify another system. For security reasons, it only accepts public addresses accessible from the internet. If the call fails, it is retried, and the subscriber continues the journey in any case. Each call carries the X-Acumbamail-Delivery-Id header, which is repeated with the same value if the call is retried, to detect duplicates in the destination system.
- Jump to step. Redirects the journey to another point in the same flow. It is the only way to go backwards, and it has a repetition limit so that no one gets stuck in a loop.
- Jump to another automation. Transfers the subscriber to another automation on the same channel. It is a final step, because they leave this one and start the other from its trigger. The destination automation must be active.
Wait
They stop the subscriber before continuing. There are three types.

- Wait for a period of time. Two modes. A fixed time, in minutes, hours, or days. Or until the next time you indicate, choosing one or more days of the week, a day of the month, or simply a time. It is useful so that messages are never sent on weekends or to group sends early in the morning.
- Wait until a date. Until a specific date and time, or until a date stored in the subscriber. This second option allows you to wait for something different for each person, such as their booking date or their plan renewal date.
- Wait for an event. Until a condition is met, with a maximum deadline.
The third type allows, for example, waiting for the subscriber to open the previous email for a maximum of three days. Whoever opens it continues through one branch, and whoever does not exits through the other when the deadline expires. The statistics indicate how many subscribers exited through each one.
Condition
They split the journey into two paths.
- Decide by rules. Evaluates subscriber fields. For example, whether they are a VIP customer or whether they live in a specific city.
- Decide by behavior. Evaluates whether they opened or clicked a campaign.
Inside the step panel there is also a third type of condition, Relative date, which compares a subscriber date field with the current moment. It allows you to separate, for example, someone who purchased more than one hundred and eighty days ago from someone who purchased more recently.
Two branches come out of each condition, and each continues on its own path. A branch can remain empty if there is nothing to execute in that case.
In rules-based conditions, the available operators depend on the field type.
| Field type | Operators |
|---|---|
| Text | Equal to · Different from · Contains · Does not contain · Starts with · Ends with · Is empty · Is not empty |
| Number | Equal to · Different from · Greater than · Greater than or equal to · Less than · Less than or equal to |
| Date | Equal to · Different from · After · On or after · Before · On or before |
Rules can be combined, indicating whether all of them must be met or whether any one is enough. If you already have a saved segment with those same conditions, the editor lets you import its rules as a starting point instead of rewriting them. Rules based on campaign behavior are not imported, and the editor indicates how many have been included.
In behavior-based conditions, the event to monitor depends on the channel.
| Channel | Events |
|---|---|
| Opens the campaign · Does not open the campaign · Clicks · Does not click | |
| SMS | Clicks · Does not click |
| Clicks · Does not click · Reads the message · Does not read it |
The campaign to monitor can be one of your campaigns or the send from a previous step in the automation itself. This second option allows you to chain a reminder addressed only to those who did not react to the previous message.
Monitoring a send of your own requires each subscriber to enter only once, because that is the only way to relate an open to the journey that caused it. If the trigger repeats subscribers, that option is not offered and the only choice left is a campaign already sent. Anniversary and relative date triggers repeat, as does any trigger with the new entry box checked.

Move around the editor
The editor control bar lets you zoom in and zoom out, reset the zoom to 100%, and center the view at the start of the journey. There is also a minimap that can be shown or hidden, useful when the automation grows and On the Statistics tab the minimap is colored, it marks the steps that have subscribers inside and flags in red the ones with stopped journeys.

Changes can be undone and redone with the buttons in the bar or with Ctrl+Z and Ctrl+Shift+Z.
Reorder steps
Each step has the options Move step up and Move step down to change its position in the journey. Conditions are the exception, because since they have two branches, they cannot be moved without undoing the split. To reorganize a journey around a condition, you have to work on the steps hanging from each branch.
Go back without creating loops
The Jump to step step allows the journey to return to an earlier point. It is useful for repeating a reminder until you get a response.
To avoid indefinite journeys, you must indicate the maximum number of times a subscriber can pass through that jump. The allowed limit is 10 loops per subscriber.
If a subscriber reaches that limit, they exit the automation and their history records that the journey was stopped to avoid staying in a loop.
Save, review, and confirm
During design, the draft is saved automatically, and the header indicates the save status at all times. The draft does not affect the automation currently running, which continues to use the last confirmed version.
The first version
When the design is finished, click Confirm changes. Before applying anything, Acumbamail checks that the configuration is complete.
If any data is missing, the list of points to review is shown grouped by step, with the number of issues for each one. Each error is also marked in its own field. Clicking a warning takes you directly to the step that originates it, and the warning disappears from the list once corrected.
The reasons are described in plain language and name the step they correspond to.
The review checks two things.
- That each step is complete. With warnings such as “choose the list associated with the trigger,” “subject missing,” or “choose the WhatsApp template.”
- That the whole is consistent. You are warned if the trigger is missing or there is more than one, if no action has been added, if there are linked steps forming a loop, if any step is not reachable from the trigger, or if a condition has an unconnected branch.
If there is nothing to correct, the draft is saved as the first version. This does not start the automation. It remains stopped until you activate it.
Subsequent versions
From then on, each confirmation generates a new numbered version. The header indicates which one is in use, and during editing it shows that you are working on the draft of the next one. This allows you to modify a running automation safely, since the changes are not applied until you confirm them.
The configuration check is repeated with each confirmation. What changes is that now, before applying anything, the summary of changes appears with three pieces of information.
- What will happen when you confirm.
- How many steps the change affects.
- What has been modified compared to the previous version, field by field and with the previous value crossed out. It also includes structural changes and indicates the steps added, the steps deleted, and those whose position has changed.
When the change affects those who are already inside, the summary warns you. It indicates how many will move on to the next step because theirs disappears, how many will continue immediately because you have shortened a wait, and how many will repeat a step because you have changed the order.

It is worth keeping an important consideration in mind. If the automation is active, when you confirm, the new version is applied both to subscribers who enter from that moment on and to those who are already inside. If it is stopped, the version is saved and will be applied when you activate it.
Discard the draft
While there are unconfirmed changes, the more options menu in the header offers Discard draft. It returns the design to the last confirmed version and the draft changes are lost. It is only available when there is a previous version to return to.
The trigger remains fixed
There is one change that is no longer possible after the first confirmation. The trigger audience cannot be modified. Those fields appear locked with the indication “Defined on publish.”
The reason is that changing the audience of an automation that already has subscribers inside would leave those people going through a flow that does not correspond to them.
If you need a different audience, use the Duplicate to change it button next to the notice. A copy is generated in which the trigger can still be selected.
The name and re-entry options can still be modified, since they do not determine who enters but how often they can repeat.

Activate and stop
An automation is Active or Stopped, and its status appears in the editor header. While it is stopped, no subscriber enters and no sends are made.
The switch in the header changes from one status to the other. Its label indicates which status it is in, and when you toggle it, confirmation is requested before applying anything. It can also be activated and stopped from the automation menu in the list, without opening it for editing.
Confirming changes does not activate the automation. They are two different operations. Confirming saves a new version, and activating is what makes subscribers start entering.
Before you can activate it
To activate an automation, two requirements must be met.
- At least one confirmed version. While it does not have one, the header shows the status but the switch cannot be toggled.
- A paid plan and available quota. Free accounts can create and design automations, but not activate them.
Each plan includes a maximum number of active automations. The count is combined, so the number in your plan covers all active automations in the account, both new ones and those created with the previous version. When the limit is reached, the notice indicates which plan allows you to activate more.
Migration does not consume additional quota. If the automation you activate replaces an old one that is still active, that one is stopped at the same moment, so the total does not increase and you can complete the migration even if you are right at your limit.
When stopping it
You are asked what to do with the subscribers who are already inside.
- Let them finish. They complete their journey and no new subscribers enter. This is the default option.
- Make them exit now. Their journey is interrupted at the point where they are. Each subscriber’s history records that they exited because the automation was stopped.

Stopping an automation is reversible and you can activate it again whenever you want. Deleting it is not. If you delete it while it is active, ongoing journeys are canceled and there is no way to recover them.
Check the statistics
Statistics are checked inside each automation. When you open it, the header offers two tabs, Editing and Statistics. In the second, the data appears on the journey itself, step by step, so you can see how many subscribers pass through each step and where they stay.

The summary
The automation totals appear at the top.
- Entered. Subscribers who started the journey.
- Completed. Subscribers who reached the end.
- In progress. Subscribers currently inside.
- Canceled. Journeys ended early.
- Failed. Journeys interrupted by an issue.

Data by step
Each step indicates how many subscribers have passed through it, and opening it expands its details. Sending steps also include delivery data. In email, sends, opens, and clicks are shown. In SMS and WhatsApp, sends, deliveries, pending, and failed are shown.
From the step details, the View report link opens the full report for that send in a new tab, with the same details as any campaign. Sends generated by an automation do not appear as independent campaigns in the email, SMS, or WhatsApp lists, so they are not mixed with the ones you launch manually. The step is the entry point to their results.
From that same detail you can open the list of Current subscribers, with those going through the step at this moment, and the list of Stopped subscribers. Both show each one's email or phone and are browsed by pages.
When the trigger allows a subscriber to enter again, opens and clicks count each person only once, even if they received the same email in several journeys. In that case the step report warns about it and stops showing the data that depends on telling one send from another.
Steps that split the journey show the branch distribution, that is, how many subscribers exited through each one. Steps that wait for an event also indicate how many exited because the deadline expired.

The period
The period can be adjusted between Last 7 days, Last 30 days, Last 6 months, and Historical · totals.
If an automation has been running for some time and no data appears, it most likely has had no activity within the selected period. Switching to Historical will show you the accumulated totals.
If the automation is published but has not yet processed anyone, the panel says so with a message instead of showing you a column of zeros.
Warnings, stopped subscribers, and cancellations
The details of each step can show two counters that should not be confused.

Warnings
A warning indicates that the step was not applicable to that subscriber and that the journey continued normally. There is nothing to do.
This is the case, for example, of an SMS step for a subscriber without a registered phone. These are the most common reasons.
| Situation | Cause |
|---|---|
| They were not on the step’s list | The step operates on a list where the subscriber is not present |
| They have no registered email or phone | The data the step needs to perform the send is missing |
| They have no date in the field used by the step | A wait that checks an empty date field |
| They are unsubscribed, outside the list, or their address bounced | It is not possible to send them messages |
| They requested not to receive WhatsApp messages | Their decision is respected |
| The phone is not valid | The number does not have a usable format |
| The value does not match the field type | A step that updates a field with an incompatible value |
| The destination list no longer exists | The list on which the step operated was deleted |
| The step unsubscribes from email and the subscriber entered by phone | Unsubscribe applies only to email subscribers |
Stopped subscribers
A stopped subscriber is a subscriber stopped by an issue you can resolve. They are not lost or advanced; they remain waiting for you to fix it.
The notice itself indicates the cause and where to resolve it.
| Situation | How to resolve it |
|---|---|
| No email credits | Add balance or a payment method |
| No SMS credits | Add SMS balance |
| SMS sender not registered with the CNMC | Register it in Settings › SMS senders |
| Invalid SMS sender | Correct it. It allows a maximum of 11 characters and no spaces |
| SMS sender under review | Wait for it to be accepted. We will let you know when you can run it again |
| SMS sender rejected by the CNMC | Check the reason in Settings › SMS senders and request a new one |
| SMS sender registered only for outside Spain | Register one for Spain in Settings › SMS senders |
| The account is blocked | Resolve the account block |
| The internal notification address is not verified | Verify it in Settings › Senders |
| The webhook URL is not valid | Correct it. Only public addresses are allowed |
| The step has a configuration problem | Edit it and confirm the changes again |
| The step operates on a list from another channel | Select a list from the correct channel |
| The WhatsApp template is no longer active | Wait for Meta to approve it again |
| Issue with the WhatsApp account | Review it in WhatsApp Business. It may be due to the payment method, the name not being approved, a quality block, or a Meta restriction |
| The channel is no longer available in the account | Reactivate it |
Once the issue is resolved, open the step and click Rerun stopped subscribers. The step is tried again with all subscribers stopped there, who continue from where they left off.
It is worth keeping two things in mind.
- It affects only that step. If there are stopped subscribers in several steps, you must rerun each one.
- If the issue is still not resolved, they will stop again. It is advisable to check first that the problem is truly fixed.
Stopped subscribers have a period of fifteen days to continue. After that time, they exit the automation, and their history records it as a cancellation due to an issue that was not resolved.

Cancellations
From the summary, you can view the details of cancellations, with the subscribers who exited before completing the journey and the corresponding reason. The most common are these.
- The subscriber unsubscribed or left the list.
- The subscriber was permanently deleted from the list.
- The automation was stopped by choosing for subscribers to exit.
- They were manually removed with “Remove from journey.”
Calls that do not start any journey
If you use the external event trigger, your system may notify about a person who is not on the automation’s list. The call is received and recorded, but it does not start any journey.
To view them, open the trigger in Statistics mode. If any call has been discarded, a counter called Discarded appears, indicating how many were received for an email or phone that was not on the list. When there are none, the counter is not shown.
A high number usually means that the integration is sending data that does not match your list data.
Check a subscriber’s journey
Statistics mode includes a search box by email or phone with which to check the case of a specific subscriber. When found, their full journey is expanded, step by step and with dates. Each event indicates what happened and, in sends, what the actual result was, such as whether they opened the email, clicked, bounced, or whether the SMS was delivered.
If the subscriber is inside the automation at that moment, the step they are in appears highlighted in the editor. From that same view, you can use Remove from journey. The subscriber exits the automation and stops going through it. This operation is irreversible.
The history also records where each subscriber comes from. If they entered because another automation sent them here, it says which one. And if a jump step did not manage to take them to its destination because they were not on that automation's list, the history explains it and reminds you that to achieve it they have to be added to that list in an earlier step.
The search box is available for periods of up to six months. It does not work in the Historical range.

The same subscriber in several lists and channels
The subscriber who enters through the trigger is the recipient of the entire journey, and that does not change at any time. What can vary in each step is where that same person is located.
This mechanism is what allows you to design an automation that starts in email and ends by sending a WhatsApp to the same subscriber.
The list for each step
By default, each step operates on the trigger list and requires no additional configuration. For a specific step to act on another list, select it in that step. In sending steps, the field is called Send to another list (optional). If left empty, the trigger list is used.
Within the same channel, location is automatic. If the subscriber entered by email, they are searched for by their address in the indicated list. If they entered by phone, by their number.

Change channel in a step
A step can point to a list from another channel. An automation that starts with an email subscription can later send an SMS or a WhatsApp.
When crossing channels, the Field that identifies the subscriber field appears, where you indicate which field in the destination list contains the data of the subscriber who started the automation. As long as the step does not cross channels, that field does not appear.
It is necessary because an SMS list does not store email addresses, and there is no automatic way to determine that an email subscriber and an SMS subscriber are the same person.
For example, the automation starts with a subscription to an email list and a later step sends a WhatsApp. In that step, you select the WhatsApp list and, as the identifying field, the field in that list where the email is stored. With that data, the same subscriber is located and the send is carried out.

Automations started by phone
They work the same way, with one difference. The list is not optional.
If the automation starts by SMS or WhatsApp and you add an email step, the field becomes Email list and must be filled in, together with the identifying field. Without those two pieces of data, there is no way to know which address to send to.
If the subscriber is not located
It can happen for two reasons.
- They are not on the destination list.
- The identifying field is empty.
In both cases, the step is not executed for that subscriber and the journey continues with the following steps. It does not stop or get lost. In the statistics, it is counted as a warning, and their history indicates that the subscriber could not be identified in the destination list.
A large number of warnings of this type usually indicates that the selected identifying field is not the correct one.
Subscription to another list
The Add to a list step not only locates the subscriber, it can also subscribe them. Within the same channel, it copies to the destination list the fields that match by name with those in the source list. If the subscriber already appeared on the list but had been removed, they are reactivated instead of duplicated.
When crossing channels, it works the same way and uses the identifying field to determine which phone or address to subscribe. If that field is empty, the subscription cannot be performed, and the step is skipped with its corresponding warning.
Channel availability
Email is always available, while SMS and WhatsApp depend on your account configuration. This is reflected in the editor in two different ways.
| Channel status | What you see in the editor |
|---|---|
| Not available in your account | Its steps do not appear in the menu |
| Available but not subscribed to | Its steps appear dimmed and lead to the subscription page |
| Subscribed | Its steps are used normally |
The same criterion applies to the channel selector for the trigger and conditions. An unsubscribed option cannot be selected.
If you subscribe to a channel later, its steps become available without any additional action. Conversely, if a running automation uses a channel that is no longer available, subscribers are stopped at that step until it is restored.
Credit consumption
Automations consume the same balance as the rest of the platform, with no separate fee. Each channel behaves differently.
- Email. Each email sent deducts one credit. The plan balance is consumed first and then, if any, the prepaid balance. If it runs out and there is a registered payment method, sends continue and the excess is billed later. If there is none, the send is not carried out and the subscriber is stopped at that step.
- SMS. Each message deducts SMS credits, and the amount depends on the length of the text. If there is not enough balance, the message is not sent and the subscriber is stopped at that step, even if the account has a registered payment method. Here, excess is not billed; you must add balance.
- WhatsApp. Messages are billed by Meta according to its own rates and do not consume Acumbamail credits.
Customize messages
Messages can be adapted to each recipient with tags, which are replaced by each subscriber’s data at the exact moment of sending. Tags come from the fields of the list on which the step operates. If the list has a field with the name, it can be used to personalize the greeting.
Fields that support tags have a Tags button that shows the available ones and inserts them into the text. The email step subject, the plain email body, the SMS text, the WhatsApp template parameters, and the webhook body have it. The content of an email with a template is personalized from the template editor.

If the tag dropdown appears empty, the list does not yet have configured fields. They are added by editing the list.
What is configured outside the editor
Some steps need resources that are managed in other sections of Acumbamail. The editor does not duplicate them, but it does take you directly to the place where they are created.
When a dropdown is empty because you do not yet have that resource, the field itself indicates it and offers the link. For example, if you do not have any WhatsApp lists, the WhatsApp step shows that notice next to the link to manage them.
Senders
Email steps request the sender address, which must be one of the verified addresses in your account. The field offers the link View my verified senders, and if you do not have any, Register a sender.

In the Send me an email step, the restriction applies to the recipient. Its Send notice to field only accepts an address of yours, either your account address, a verified address, or any address from a verified domain.
SMS steps request the message sender, which is managed in the SMS senders section. It must be registered with the CNMC and allows a maximum of 11 characters without spaces.
A sender can be under review, have been rejected, or be registered only for sends outside Spain. In those three cases the step does not send and subscribers remain stopped with the corresponding reason.
WhatsApp templates
WhatsApp sends are always made from a template approved by Meta. Templates are created and submitted for approval from the WhatsApp templates section, and only those already approved appear in the step.
Surveys
The survey trigger only supports surveys that capture the respondent’s email. If you do not have any, the field indicates it and links to the surveys section.
Inbound webhooks
The external event trigger needs an inbound webhook configured. The editor shows the address that triggers the automation and links to its configuration.
Email templates
The Send email with template step includes a selector with your templates and Acumbamail’s predefined ones. It has a search box, filters by category and tag, and Preview for each one.
Once selected, the template menu allows you to Change template or Edit. The Edit option opens the template editor in the same tab. When you return, the automation reloads with the updated design.
Duplicate, copy, and delete
The menu for each automation in the list brings together the rest of the operations.

- Edit name changes the automation title.
- Duplicate creates a copy as a draft, allowing you to test scope changes without affecting the one that is running.
- Delete permanently deletes it and is irreversible. If it was active, ongoing journeys are canceled.
Each automation also supports a description, which is edited from the editor header. It is useful for recording its purpose when several people work on the same account.
Copy to another account
If you manage several accounts within an agency, you can move a journey from one to another without redesigning it. The operation is only available between accounts in your own agency.
The automation is copied, not moved. The original remains in its account with its ongoing journeys and statistics.
What is copied is the design, not the data. All references to elements in the source account arrive empty, since in the destination account they correspond to other elements or do not exist.
- Lists, fields, senders, campaigns, WhatsApp templates, surveys, and webhooks arrive blank.
- Email templates are the exception and are copied to the destination account.
- Steps from a channel that the destination account has not subscribed to are removed, and the journey is reconnected at that point.
The person receiving the copy must complete the data that arrives blank before they can confirm the changes in the draft and activate it.
Operations available via API
Automations can also be viewed and controlled from the Acumbamail API, within the Automations category. There are six operations.
- getAutomations. Returns the account’s automations with their metadata. Supports filtering by name.
- getAutomation. Returns the details of an automation together with its metrics by step. Allows you to choose the time range and omit metrics if you only need the structure.
- getAutomationSubscriberHistory. Returns a subscriber’s journey within an automation, indicating the channel and their email or phone.
- cancelAutomationSubscriber. Removes a subscriber from an automation in progress.
- activateAutomation. Activates an automation. It requires the same conditions as the editor.
- pauseAutomation. Pauses an automation. Allows you to indicate whether subscribers who are already inside finish their journey or exit immediately.
The cancellation operation is especially useful for integrations. It allows you, for example, to remove a subscriber from a journey as soon as they have done what you were writing to them about. It is idempotent, so if the subscriber was not inside, the call still responds successfully.
The full reference for parameters and responses is in the API documentation.
Migrate old automations
The previous editor remains operational, but new automations are no longer created with it. The ones you already have created continue to operate normally, are identified in the list with the Old badge, and can still be viewed with Open in old editor.
An old automation that is stopped can no longer be activated again. The old editor is discontinued, and what is stopped in it cannot be started again. Those that are active are not affected and continue to work as long as you do not stop them.
When trying to activate one that is stopped, the notice indicates the way forward.
- If it has already been migrated, the name of the new one is indicated so you do not have to search for it. Having both active at the same time would make the subscriber enter through both sides.
- If it has not yet been migrated, the only way to use it again is to migrate it.
How it is migrated
Migration is started from the automation menu in the list.

A copy is created as a draft and the old automation remains running. The copy starts without statistics, and when you activate it the old one is removed from the list, so it is worth checking anything you need from it beforehand.
It is recommended to review the copy before activating it. If you are missing something or see differences from the original, contact the support team and we will review it with you.
When reviewing it, be careful with the wait steps. If when activating it you decide that the people already inside should continue in the new one, each person lands on the step equivalent to the one they were on in the old automation. If that step is deleted or replaced by another, that person no longer moves across. Changing its duration does keep them, although those already inside complete the time they had, not the new one.
When you activate it, you are asked what to do with those waiting inside the old automation, and the notice says how many people there are.
- Let them stay here. They move to the new automation and continue from the same point, without restarting the time they had been waiting.
- Start from scratch. Nobody moves across and the new automation only picks up those who enter from that moment on. Anyone left out no longer receives the rest of the sequence.

When you confirm, the old one stops automatically, so there is no risk of duplicate sends.
Migrate autoresponders
Autoresponders become part of automations. In the campaign list, the Autoresponder type indicates that it is now configured in Automations and leads to the template gallery.
The autoresponders you already have created continue to be sent and are identified with their own badge. Their options menu includes Migrate to Automations.

A copy is created as a draft and the autoresponder keeps sending in the meantime. The copy starts without statistics because it sends with a campaign of its own.
It is recommended to review the copy before activating it. If you are missing something or the result is not what you expected, contact the support team and we will review it with you.
When you activate it, the notice says how many people are waiting for their email. There is nothing to choose here. Anyone who already triggered the autoresponder and has not received it yet receives it from the new automation, on the date that was due and without restarting the wait.
When you confirm, the autoresponder stops automatically, so there is no risk of duplicate sends. It stays in the campaign list with what it managed to send and cannot be started again while the automation exists.