Automations overview
Build trigger-based workflows on the canvas—from templates or blank—then activate, run, and monitor runs.
Automations are visual workflows (React Flow canvas) that fire on a trigger, then run actions, conditions, filters, and delays. Start from a free or Pro template (creator or brand catalog), or build blank. Activate the flow so events run it, or run it manually when permissions allow.
What you'll do
- Open Dashboard → Automations (feature
automations+ view permission) - Create from a template or blank, then land on the canvas editor
- Wire a trigger and action nodes; save and activate
- Monitor run history, toggle on/off, bulk enable/delete, or Run manually
Before you start
- Plan includes Automations
- Your role can view (and ideally create / enable / run) under Automations permissions
- Connected accounts for actions you need (Telegram, WhatsApp, Slack, social, Shopify, etc.)
- Pro templates require the Automation Templates Pro add-on to start from; existing graphs keep running without it
Image placeholder — add `images/overview-cover.png` under this category
Steps
1. Open Automations
- Go to Dashboard → Automations.
- Switch between table and cards views with the toggle.
- If the list is empty, use the empty state to start creating.
Image placeholder — add `images/overview-step-01.png` under this category
2. Create from template or blank
- Click New automation (create shortcut when shown).
- On the choose step, browse templates filtered for your team type (creator vs brand).
- Locked Pro or feature-gated templates show a toast if you select them without access—pick a free starter or upgrade.
- Or choose Start blank.
- On the details step, set name and optional description, then submit.
- You are redirected to
/dashboard/automations/{publicId}— the canvas editor.
Image placeholder — add `images/overview-step-02.png` under this category
3. Build the canvas
- Confirm the trigger node matches the event you want (examples):
- Manual, New link, New deal, Schedule, campaign / application events
- Integration events (Shopify, Mailchimp, HubSpot)
- Social (Instagram/Facebook comment or DM)
- Routine alert / health events, Calendar event reminder
- Add action nodes as needed, for example:
- Messaging: Telegram, WhatsApp, email, Slack, in-app notification
- Links: create / tag link, add to bio
- AI: generate caption or email
- Pipeline / calendar: create kanban cards or calendar events (need those features)
- Publishing: Content Studio distribute / post actions
- Integrations: Sheets, Notion, Airtable, HubSpot, Shopify discounts
- Use condition, filter, and delay nodes for branching and pacing.
- Save the graph. Coming-soon actions (for example some storage / X post) stay disabled in the UI.
Image placeholder — add `images/overview-step-03.png` under this category
4. Activate, run, and review
- Toggle the automation Active so live triggers can fire (needs enable permission).
- Use Run for a manual execution when the trigger type allows (needs run permission).
- Inspect last run status and run history (success / failed / partial / cancelled).
- From the list: bulk activate/deactivate or delete when permitted.
Image placeholder — add `images/overview-step-04.png` under this category
Tips
- Prefer a free single-step template first to prove connections, then expand the graph.
- Match action feature gates: Telegram/WhatsApp/Slack/social/pipeline/calendar each need their own entitlement.
- Routine-driven triggers pair well with Routines health alerts for ops automation.
- Keep one job per automation (notify, create cards, post) so failures are easy to diagnose.
- Deactivate before major canvas edits if you want to avoid mid-edit live runs.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| Upgrade block | No automations feature | Billing → upgrade / add-ons |
| Permission page | Role lacks Automations view | Ask a team admin for access |
| Template locked (Pro) | Missing automation_templates_pro | Add the Pro templates pack, or start blank |
| Action node disabled | Feature / integration not on plan | Connect the integration or upgrade for that action |
| Run fails | Missing credentials or invalid node config | Open the failed run steps; fix the node and re-run |
| Trigger never fires | Automation inactive or wrong trigger config | Activate; verify event source (link create, webhook, etc.) |