Automation actions: everything an automation can do

Actions are what an automation does once a contact is in it. You add them on the Flow tab of the automation editor: click a + in the flow, then click the action in the Add action panel on the right, or drag the action from the panel onto a +. Fill it in and click Update to save it. Delete at the bottom of the panel removes it.

Actions run top to bottom, and they come in four groups. An automation needs at least one action, and every action has to be filled in, before you can activate it.

Workflow

Actions that shape the flow rather than do something to a contact.

Delay: pause before the next action. Timer waits a number of days, hours and minutes. Dynamic date waits until a date from the contact or the event, chosen under Delay until; if that date has already passed, there's no wait. A delay can't be the last step in a flow.
If/Then branching: split the flow. Each branch has its own filters, and a contact goes down the first branch whose filters they match, so put the narrowest one first. A contact who matches none takes the else branch at the bottom, which has no filters. Use Add branch for more than two.
Calculation: do a sum on two values and store the result under a name you choose. Later actions in the same automation can use that result through the { } button, for example as the number of points in a loyalty transaction. Either value can be contact or event data.

External

Webhook: send the automation's data to a URL outside Leat. See the next section before you use it.
Automated email: send the contact one of the automated emails you've built under Marketing → Automated emails. Only published emails can be picked. The email isn't sent to an anonymous contact, or to a contact who isn't subscribed to the email's subscription type. The step still counts as done, and the flow carries on.

The Webhook action

Use a webhook subscription instead when all you want is to tell another system something happened. Subscriptions are signed, retried when your endpoint is down, and every delivery is logged. See Webhooks: send events from Leat to your own system. The Webhook action is for when the call has to be one step in a flow: only for some contacts, after a delay, or next to an email.

What you can set:

URL: the field starts with https://, so type the rest of the address after it. The address comes from the system that receives the data, not from Leat.
Request body: Include all automation data sends everything the automation knows about the contact and the event. Customise data lets you send only what you pick: click Add Key-Value pair, type a key, and fill the value with text or data from the { } button.

That's all there is to set. The request is always a POST with a JSON body, shaped like {"data": { … }, "version": "v1"}. There's no choice of method, and no headers or authentication to add. If the receiving system needs a key or token in a header, the Webhook action can't provide it: use a webhook subscription, or put a middleware tool between the two.

The call isn't retried. If your endpoint can't be reached, the step shows Error and the flow stops for that contact. If your endpoint answers with an error status, Leat still counts the webhook as sent.

Create

Actions that write something for the contact.

Voucher: issue a voucher of the promotion you pick, in the quantity you set. With Use an existing, unlinked voucher on, it hands out a voucher you already created in that promotion instead of generating a new code. When none are left, the step fails and the flow stops for that contact.
Loyalty transaction: credit or debit points. Choose Directly set points to set a number yourself, or Calculate using Loyalty Rules to let your rules work it out from an amount. A negative number takes points away. See How to add points through an automation.
Reward reception: claim a reward on the contact's behalf. Pick the reward and the business profile it's recorded against.
Prepaid transaction: add to or take from the contact's prepaid balance.
Identifier: create a contact identifier, so the contact can be recognised by a card or code. Leat can generate one, or take the value from a contact attribute.

Internal

Internal e-mail: email your own team rather than the contact. This is the alerting action: "someone just hit the top tier", "a form submission needs review". Pick the users under Receivers, and write a Subject and a Body. Both can carry contact data, like their name or points balance, through the { } button.
Set contact attribute: write a value onto the contact. Pick the Attribute, then the Strategy:
- Value from automation: a value you type, or data from the { } button.
- Value from attribute options: one of the options of a select attribute. For a multi-select attribute, Multi-select strategy decides whether the value replaces what's there or is added to it.
- Date of execution: the moment the action runs.
- Clear existing value: empty the attribute.
Contact type: set the contact's type. Only there if your account uses contact types.

Set contact attribute can't change points, the tier or the total purchase amount. Those are results of transactions, so the way to change them in an automation is a Loyalty transaction.

Setting an attribute or a contact type counts as updating the contact, so it starts your Contact updated automations too. If that automation is the one doing the setting, filter its Start step on Attribute has changed so it doesn't keep starting itself.

When an action fails

Open the run on the automation's Runs tab, then Actions, to see each step with Success or Error and the reason. Some failures stop the flow for that contact: a webhook that can't be reached, an email that couldn't be sent, a voucher promotion with no unlinked vouchers left. Others are recorded and the flow carries on to the next action.

If the email an Automated email action points to is gone, the automation stops altogether and gets the status Has errors. Pick another email and activate the automation again.

What isn't an action

There's no action that removes a contact, sends an SMS, or edits another automation.