1
Create a workflow
Name it after the outcome, not the tool.
Automation · Step 1
Name it after the outcome, not the tool.
Product / Automation
Automation
Workflows with webhook triggers and six action types, stored on the organization.
When a form lands or a deal moves, WhatsApp, SMS, or Studio can fire.
Who it is for
Teams who already repeat the same three steps after every lead.
What you get
Trigger + actions, webhook URL, run history.
What we do not pretend
Not Zapier-for-everything. Six action types, on purpose.
Use cases
Would this actually happen in your week?
New lead → WhatsApp
Webhook from a form. Action: send an approved template.
The lead gets a message before someone opens the CRM.
Deal won → invoice
Stage change fires a GST quotation or invoice draft.
Accounts does not retype the buyer.
Weekly poster
Schedule trigger. Action: remind the team or kick a Studio job you already templated.
Friday does not start from a blank prompt.
How to use it
The same screens you will click after you sign in.
Recreated from the live product so you can follow along before you create an account. Red circles mean a count or a remove — they are not decoration.
2
Pick a trigger
Webhook, schedule, or a record change the engine supports.
Automation · Step 2
Webhook, schedule, or a record change the engine supports.
3
Add actions
WhatsApp, SMS, email, and the other shipped action types.
Automation · Step 3
WhatsApp, SMS, email, and the other shipped action types.
4
Turn it on
Runs write to WorkflowRun. Failures show in the run, not a silent skip.
Automation · Step 4
Runs write to WorkflowRun. Failures show in the run, not a silent skip.
Usually next
Studio
Write what you need, pick a brand kit, and Design Graphic. Studio copies logo, colors, and style posters — then you publish.
See how it works →
Cloud API numbers, approved templates, and broadcasts from the same workspace as Studio.
See how it works →
Sales
Deal pipelines connected to contacts, invoices, and automations.
See how it works →