Skip to main content
Steps run in order. Each one can read what the steps before it produced, using {{ steps.<reference name>.<value> }} — see Variables and expressions. Every step also has the same three advanced options, whatever its type: If this step fails (stop the run, or carry on), Also save the result as (a short alias under vars.), and an internal Note for your team. A step can be paused with the switch in its settings header; it stays on the canvas and is recorded as skipped.

​
Messaging

These put something in front of the contact. All of them need a conversation to send on, and are skipped when there is not one — a form submission or a store order from somebody who has never messaged you.
Request a payment and Send an invoice fail the step when the amount resolves to nothing. Everywhere else an unknown token is a cosmetic gap; here it would be a payment request for zero, or a tax document with no value that has already consumed an invoice number.
Send form and Send booking link fail the step if the form is not published, or the appointment type is not bookable. A message containing a dead link is worse than no message. Left blank, the line above the link reads Please fill in this short form: or Pick a time that suits you:. Both send the link as an ordinary text message on every channel. Send booking link’s Appointment type lists your published booking forms and, when Cal.com is connected, your Cal.com event types, marked (Cal.com). A saved choice that no longer exists is shown as (no longer available). Send an invoice is the one sending step that does not need a conversation. An invoice has value the moment it exists — it is your own record — so the run creates it and reports that it could not deliver it, rather than skipping. The step fails on every run while Sales documents is switched off, or while your business name and address are not filled in; the settings panel says which, with a link to the screen that fixes it. With What to bill set to the items on the order, it only works from a store trigger, and carries the order’s discount and shipping; it is issued as paid when the store says the order is paid. A payment link’s Message sent with the link applies inside the 24-hour window only. Outside it, the approved template supplies the wording, because a template’s copy is fixed at approval. Put {link} where the URL should go, or it is appended.

​
Contact

Pointing Add to segment at a filter (dynamic) segment fails every time it runs — a dynamic segment works out its own members — and the checks panel says so before it goes live. Opt out of marketing marks the contact as opted out, so campaigns and broadcasts skip them from then on. It does not stop replies, order updates or receipts: somebody who opts out and then asks about their order still gets an answer. Running it twice is safe — it keeps the date they first opted out. Opt back in to marketing clears the opt-out. Neither has settings, and both need a contact. See Opt-outs and consent.

​
Deals and team

Update deal needs at least one thing to change — a stage, a status, a value or a title — or activation is refused.

​
Conversation

​
Logic and timing

Both waits park the run rather than holding anything open. Everything the run has collected so far is kept, and it continues later. Detail in Conditions and branching.

​
Data

A variable name may use letters, numbers and underscores only. It is read back as {{ vars.<name> }}, and a dot or a space there would split the path.

​
Report a conversion

This step is how a business with no store and no payment gateway reports a sale or a booking back to the ad that brought the customer in.
  • What happened is a picker: Purchase — they bought, Lead — they gave you their details, Qualified lead — worth following up, Started checkout, Added to cart, Viewed a product. Purchase is the default.
  • What it was worth (optional) takes a number or a token. Leave it empty when there is no amount — a booking or an enquiry. An empty amount is not reported as zero.
  • Currency appears once there is an amount. It defaults to INR; the other choices are USD, AED, GBP, EUR and SGD.
Only contacts who arrived from a click-to-WhatsApp ad are reported. For everyone else the step does nothing, records nothing to report — this contact did not come from an ad, and the run carries on. That is the normal case, not a failure. An amount that resolves to nothing at run time, or to something that is not a positive number, fails the step rather than reporting a sale worth nothing. Each step reports at most once per run, so a run that is retried does not count the same conversion twice. How conversions travel to Meta is covered in Click-to-WhatsApp ads.
An HTTP request to a private, loopback or internal address is refused by the server for security. The checks panel catches the obvious cases while you are editing. Credentials typed into the authentication fields are ordinary settings — anyone who can edit the automation can read them.
Google action does not appear as a generic entry in the add menu. Each action is listed individually, because that is what you are looking for. The step names no connection and no URL: the deployment is resolved from the workspace.

​
Orchestration

Only an active flow can be started; a draft is skipped. Run automation refuses to run the automation it is in, and a chain of automations is capped at three deep so a loop dies immediately rather than filling the queue.

​
Superseded steps

Send webhook and Close conversation still work and still open for editing, but they are hidden from the add menu. HTTP request does everything Send webhook does and lets later steps read the response; Set status does everything Close conversation does and can also reopen a thread.