Skip to Content
PortalAutomations

Automations

Open in the app: Automations

Automations send a WhatsApp template to each contact a set time after one of the contact’s dates, as long as the contact matches your conditions. For example, a welcome follow-up 3 days after a contact is added, or a check-in 1 day after a contact’s last conversation started.

ℹ️

Automations are in beta and available on request. If you don’t see Automations under Management, contact [email protected] to turn them on for your workspace.

ℹ️

As with Broadcast, WhatsApp templates must be created and approved in your WhatsApp Business Account (WABA) before you can use them. You can manage templates from the Meta WhatsApp Manager.

What you can do in Automations

  • Message contacts automatically a set time after they are created, or after their last conversation started
  • Limit who gets the message by lifecycle stage, tags, and country
  • Choose the days and hours when messages go out
  • Decide whether a contact can get the message once, or again after each new conversation
  • See who was messaged, and how many messages were delivered, read, and replied to

Owners, Admins, and Managers can create, edit, activate, and pause automations. Only Owners and Admins can delete them.

Automation areas in Portal

Automation list

Open Management > Automations.

  • The cards at the top count your Active, Paused, and Draft automations.
  • Search by name, or filter by state.
  • Each row shows the trigger, the template, the state, the number of messages sent, and when the automation last messaged a contact.
  • Turn the Enabled switch on or off to activate or pause an automation.
  • A warning icon next to the state means the automation stopped sending. Hover over it to see why.
  • From the row menu you can Edit, View occurrences, Activate or Pause, and Delete.

Automation create/edit

Use this screen to set up an automation. It has these sections:

  • Automation details: the name, the WhatsApp channel, the template, and its parameters, with a preview of the message.
  • Trigger: the date to count from, and how long to wait after it.
  • Conditions: lifecycle stage, tags, and country.
  • Schedule & frequency: when messages can be sent, and how often a contact can get them.
  • Audience summary: how many contacts match now, and how many would be messaged right away.

Automation occurrences

An occurrence is one message sent to one contact. Open it from View occurrences in the row menu. This page shows how the automation is doing:

  • The automation name, state, and trigger, with Edit and Activate or Pause buttons.
  • The reason in red if the automation stopped sending.
  • Cards with the totals for the selected period: Total, Sent, Delivered, Read, Failed, and Replied.
  • A table with one row per occurrence: the contact, the trigger date, when the message was due, when it was processed, its status, and when the contact replied.

Create an automation: step-by-step

  1. Open Management > Automations.
  2. Click New automation.
  3. Enter a clear name.
  4. Select the WhatsApp channel you want to send from.
  5. Choose a template and fill in its parameters. You can use contact placeholders such as {{name}} in parameters.
  6. Under Trigger, choose what to count from in Send after:
    • Contact created: when the contact was added to your workspace.
    • Last conversation started: when the contact last started a new conversation with you.
  7. Set the delay in Days and Hours. The sentence below the fields reads it back, for example “3 days after the contact is created”. Leave both at 0 to send right away.
  8. (Optional) Under Conditions, choose a lifecycle stage, tags, or a country.
  9. (Optional) Under Schedule & frequency, set the send window, the catch-up window, and how often a contact can get the message. See Schedule and frequency.
  10. Check the audience summary.
  11. Click Save as draft to keep it without sending, or Save & activate to start it.

Conditions

Conditions decide which contacts get the message. A contact needs at least one of the selected tags, and must match the stage and country if you set them. Leave them empty to include every contact.

Conditions are checked when a contact becomes due, not when you save the automation. A contact that gets a tag after it was created still gets the message if it has the tag by then.

Archived contacts, contacts who opted out with your opt-out word, and blacklisted contacts never get the message. As with broadcasts, only contacts who messaged you in the last 90 days are included, unless this rule is turned off for your workspace. While the rule applies, the delay after Last conversation started must be less than 90 days.

Schedule and frequency

  • Timezone, Send from, Send until: messages go out only between these times, in this timezone. Set both times or neither. Leave them empty to send at any time of day.

  • Send on: the days of the week to send on. Leave it empty to send every day.

  • Catch-up window (days): how long after its due time a contact can still get the message. Contacts that became due longer ago are skipped. It can be 1 to 30 days, and the default is 1 day.

  • How often can a contact receive it:

    • Only once: a contact gets the message at most once.
    • Once every N days: a contact can get it again after each new conversation, but not within Minimum days between messages of the last one.
    • Every time the date changes: a contact gets it again after each new conversation.

    The last two options are only available with the Last conversation started trigger.

Contacts that become due outside the send window wait for the next window. If the catch-up window ends first, they are skipped. Make the catch-up window at least as long as the longest gap between two send windows. For example, a Monday to Friday window needs at least 3 days to cover the weekend.

The audience summary

Below the schedule, the editor shows a summary like “120 contacts match the conditions now. 8 of them are already due within the catch-up window and will be messaged on activation.”

  • The first number counts the contacts that match your conditions today.
  • The second number counts the contacts that are already due and still within the catch-up window. They get the message on the first run after you activate the automation. Contacts that became due earlier are skipped. To reach fewer existing contacts at launch, shorten the catch-up window.

When you edit a saved automation, contacts it already messaged, and would not message again, are left out of the second number. For an active automation, the summary says they will be messaged on the next run.

The list below the summary shows sample contacts that match the conditions.

Activate and pause

  • Save & activate saves the automation and starts it. If activation fails, the automation is still saved as a draft, and a message explains why.
  • Save as draft saves it without sending. On a paused automation this button reads Save changes, and the automation stays paused.
  • On an active automation there is a single Save changes button. Your changes apply from the next run.
  • To change the trigger of an active automation, pause it first.
  • Use the Enabled switch in the list, or Activate and Pause on the occurrences page, to start and stop an automation.

When you activate a paused automation, it continues where it stopped. Contacts that became due while it was paused get the message if they are still within the catch-up window.

A workspace can have up to 20 active automations. Activation is not possible when your workspace reached its broadcast usage limit.

When an automation stops by itself

If the channel or the template can’t be used any more, for example because the template was deleted or paused in WhatsApp, or if most messages in a batch fail, the automation pauses itself. The list shows a warning icon next to its state, and the occurrences page shows the reason. Fix the problem, then activate the automation again.

If your workspace reaches its broadcast usage limit, the automation stays active but stops sending until there is room again. Contacts that were not sent are tried again later, if they are still within the catch-up window.

Occurrences and stats

Choose a period at the top of the occurrences page: Last 7 days, Last 30 days (the default), Last 90 days, or All time. The cards and the table both use it. You can also search by contact name or phone, and filter by status.

CardWhat it counts
TotalEvery contact the automation picked in the period.
SentMessages handed to WhatsApp.
DeliveredMessages delivered to the contact, including the ones read since.
ReadMessages the contact read.
FailedMessages that could not be sent, plus sent messages that WhatsApp rejected later.
RepliedMessages the contact replied to within 7 days.

A reply counts when the contact writes to you within 7 days of the message, and the automation sent the newest broadcast or automation message that contact received. It counts once per message, whether the reply starts a new conversation or arrives in an open one.

In the table, the status shows how far each message got: Queued, Sent, Delivered, Read, or Failed. Hover over a Failed status to see the reason. The Replied column shows when the contact replied.

Delete an automation

Choose Delete from the row menu and confirm. The automation stops sending and leaves the list. Its occurrence history is kept.

Troubleshooting

  • No contacts match: relax the conditions, and check that the contacts messaged you in the last 90 days.
  • Nobody is messaged after activation: contacts get the message about 10 to 15 minutes after they become due. Check the send window, and that the contacts became due within the catch-up window.
  • Cannot save: fill in the name, channel, and template, and all template parameters. With a send window, set both times, with the start before the end. The catch-up window must be 1 to 30 days.
  • Cannot activate: check the broadcast usage limit, and that fewer than 20 automations are active.
  • The automation paused itself: read the reason on the occurrences page, fix the channel or template, then activate it again.