What a workflow is
A workflow is a rule: when something happens, Adapt does a list of things. Today you can build and test one, but nothing runs on your leads yet.
A workflow is a rule in plain words: when something happens, if it is true, do these things. "When a lead comes in from the website, work out what it is for, give it to whoever is next, and make a task to call them within five minutes" is a workflow.
The parts
| Part | What it is | Example |
|---|---|---|
| Starts it | The one thing that sets it off | A new lead, a reply, a call that ended |
| Check | A question with two paths | The amount is over a limit, or not |
| Step | A thing Adapt does | Assign the lead, create a task, wait two days |
| Wait | A pause of minutes, hours or days | Wait 2 days |
A workflow is a chain. A split or a check gives each answer its own path. The workflow is drawn as a picture, one block under another, and it can also be read as a sentence.
Three kinds
The Workflows page groups what you build as Workflows, Sequences (a run of timed steps for a person, such as a LinkedIn sequence) and Partner paths (a path that runs once for each partner a deal is sent to).
Why it is built this way
- You choose from blocks Adapt already has. There is no code. A request that needs a block that does not exist can be asked for (Ask us to add a block, which is not connected yet).
- You check it before anything runs. Build, test on a pretend lead, show your team, then turn it on.
- Messages are drafted for you to check. The email and text blocks write a draft; they do not send it themselves.
See The Workflows page to open the page, and What Workflows and Customise cannot do yet for what is still to come.