Automations
Test, Execute, debug, listen
Tools to verify a draft before publish, and to re-run paths with controlled Input.
Test run vs Run now
| Action | Uses | When |
|---|---|---|
| Test run / Test with sample data | Draft graph | Always available for testing. Event-only workflows use sample payload at the event trigger (not a Manual start). |
| Run now | Published graph | Automation must be active and include a Manual trigger on the published graph. Disabled for event-only graphs. |
Sample data is synthetic
Test with sample data does not wait for a real customer message. Downstream nodes that need a real contact or account may still fail — use Manual + real setup, or Listen, for a fuller path.
Execute step (single node)
In the node detail panel, Execute step runs only that node using current Input (pinned or from a prior step). Use it to check parameters and expressions quickly.
- Channel send nodes are dry-run — they do not send a live WhatsApp / AppChat message. Use a full Test / Run for delivery.
logic.delayskips the real wait on Execute.- Event triggers and some advanced nodes (fork, join, approval, wait for reply, run automation) hide or disable Execute — use Test run instead.
Full matrix: Limits & known limitations.
Pin Input
On the Input tab, pin JSON so the next Test or Execute reuses that payload. Save draft to keep pins. Unpinned session mock data is temporary until you pin.
Debug From / To
On a Test run you can set From (start at this node) and To (stop after this node) to re-run a slice of the graph. Pick nodes that exist on the draft path; invalid picks show a toast instead of failing silently.
Listen for next event
On supported triggers (WhatsApp / AppChat message received, webhook), start Listen, then send a real message or webhook. The captured payload lands in Input so you can pin it and re-test. Works on drafts; listening does not require publishing first.