Automations
Editor guide
Build workflows on the canvas, save a draft, and publish when you want live traffic to use the new graph.
Draft vs published
- Draft — what you edit. Tests and sample runs use the draft.
- Published — what real events run against when the automation is active.
- An amber Unpublished changes banner means draft ≠ published. Live messages still follow the old published graph until you publish.
Before you start
- Permission to open Automations in the portal
- At least one WhatsApp or AppChat account if you send on a channel
- Connected credentials under Integrations for Slack / Google / HubSpot / Shopify / email nodes
Step-by-step
1. Create or open an automation
In the portal go to Automations. Create a blank automation, or open Automations Library and Use a prebuilt workflow — then open the editor.
2. Add nodes and wire them
Add a trigger (Manual, message received/sent, schedule, webhook, AI attention/handoff, campaign events, …), then logic and actions. Connect output handles to the next node’s input. You can have more than one trigger; each live event starts from the matching trigger.
3. Configure a node
Double-click a node to open its detail panel (Input · Parameters · Output). Use expressions and pickers for channel accounts, templates, and credentials. The Docs control opens reference for that node type (per-node pages roll out separately).
4. Save draft
Persist canvas, parameters, and pinned Input data. Unsaved edits show as Draft · unsaved. Saving does not change what live traffic runs.
5. Publish (or Activate)
When the draft is ready: Publish changes (or Activate if never published). After that, inbound events use the new published graph. Keep the automation active for live runs.
Not WhatsApp Flows
Meta Flows are edited under a WhatsApp account’s Flows tab. This canvas is Engagive Automations only.