Automations
Limits & known limitations
Accepted product behavior — not open bugs. Prefer the workarounds below when testing.
Execute step is not a full send
Single-node Execute is for validating config. Channel sends and some waits are skipped. Use Test run or Run now for real delivery.
Execute step
| Limitation | Behavior | Workaround |
|---|---|---|
| WhatsApp / AppChat send | Dry-run; send skipped | Full Test run / Run now with a real contact |
| AI generate reply + send | Text may generate; live send skipped | Full Test / Run for delivery |
| Delay | Wait skipped | Full run for real delay |
| Event triggers | Execute hidden | Test run or Input from a prior execution |
| Fork, join, approval, wait for reply, run automation | Execute disabled | Full Test / Run |
Editor tools
- Pins persist after Save draft. Unpinned mock JSON is session-only.
- Listen supports WhatsApp / AppChat message received and webhook. Other trigger families are not listen-capable yet.
- Binary / file pin is not supported.
- Sample-data tests are synthetic — they may lack a real contact for downstream channel nodes.
Catalog & integrations
- Google Drive / Calendar — not offered (Sheets + optional Gmail only).
- Join mode
wait_any— reserved / disabled in the UI. - Contact custom fields and AI workflow generator are not in product yet.