Visual editor
Add steps, connect them by dragging and tidy the layout in one click. Before saving, the editor points out what needs fixing.
visual automation
The process runs itself.
Draw the flow in the visual editor: trigger, decision, wait and action. Your team handles only what needs a person.
Talk to the teamthe problemFollow-ups from memory.
Follow-ups from memory.
Tasks that slip.
Chasing a reply, moving a pipeline stage or notifying another system depends on someone remembering. Sooner or later, nobody does.
01
what you do
Trigger, rule, action.
Record triggers
Account, contact, opportunity, task, event, campaign, chat contact or message: created, updated, deleted or restored. Entry conditions compare the old value with the new one.
Webhook
Each workflow gets its own URL. Paste a sample of the incoming JSON and its fields become variables in your steps. A secret header is optional.
Scheduled or launched
Run on a recurring schedule in the time zone you pick, or start it by hand and from another workflow, passing inputs in and getting outputs back.
Operational steps
Decide, find, create and update records, wait, loop, send a message, edit tags, transfer the conversation to a person or a queue, and launch another workflow.
A cadence that knows when to stop
A series of touches with waits and a send window that stops the moment the contact replies, on any channel. You can run actions after each touch.
HTTP request
Call another system with a method, headers and a JSON body built from variables. The response status, body and headers flow into the next steps.
Execution history
Each run shows every step with its status, result and error. Waiting runs can be cancelled, and the log downloads as JSON or TXT.
how it works
Draw it once, run it always.
- 01Pick the trigger
A record change, a call from another system, a schedule or the Run button.
- 02Draw the steps
Connect decisions, waits, messages and HTTP calls, and set a failure path for each step.
- 03Activate and test
Turn the workflow on and fire the trigger: change a record, call the URL or run it from the list.
- 04Read the runs
See what each step did and adjust the flow. Waiting runs pick up again on their own at the right time.
questions
Before you automate.
Do I need to know how to code?
No. You build the flow in the visual editor. JSON only shows up when you connect another system through a webhook or an HTTP request.
What happens when a step fails?
The flow follows that step's On failure path. Without one, the run ends as failed and shows up in the history with the error.
Can AI build workflows for me?
Yes. Through the MCP server, assistants such as ChatGPT and Claude create, edit, activate and run workflows and follow their executions.
Is Workflows generally available?
It is in Beta. The company turns the feature on in settings and grants the permission per role. On a phone you can view flows and runs; editing happens on larger screens.
next step
Talk to the team