Something happens, something follows: trigger and action
A workflow is a trigger and the actions that follow it. What can start one, what one can do, and the point where it hands back to you.
Watch
What it does
What it does
Anything on a record can be a trigger
A form filled in, a call missed, a stage changed, a tag added, a date reached. If the software saw it, it can start a workflow.
Actions are the things you already do
Send a text or email, wait a day, add a tag, move a card, create a task for a person. Chained in the order you set.
Every run is on the record
You can open a contact and see which workflow touched them, when, and what it sent. Nothing fires invisibly.
How it works
How it works
- Pick the trigger: the one event that should start this.
- Add the actions in order, with waits between them where a pause is right.
- Decide where it stops: a reply, a booking, or a number of attempts.
- Turn it on for new contacts and read the first few runs before you trust it.
Worth knowing
Worth knowing
- A workflow does what you built, not what you meant. A wrong wait or a missing stop condition texts someone four times.
- It cannot decide. Anything needing judgement has to end in a task for a person, and you have to add that step.
- Automating a process you have not settled makes the mess faster. Get the steps right on paper first.
Related
Related
Building a workflow
The builder itself: picking a trigger and chaining the steps on screen.
The work you do twice
Which of your repeated jobs is worth automating first.
Email campaigns
When the action you want is a send to a whole list.
Build one small workflow
Log in, open Automations, and build the shortest one you can: one trigger, one message, one stop.