Workflows

Visual automation: a trigger enrols records, then they flow through timing, messaging, branching and action steps.

Automationabout 9 min

By the end you'll be able to

Walk through it

0 of 10 steps done0%

"Start from a template" gives you a working graph to adapt, which is much faster than a blank canvas. Otherwise create a new workflow and pick what it operates on — contacts, companies or deals.
Open Workflows

Good to know

Handing off to a sequence is skipped for a record already in one, so a workflow cannot double-enrol somebody mid-cadence.
A deal or company workflow that enrols into a contact sequence uses the primary contact of that record.
"Rotate to owner" needs the workflow to have a product, because the owner pool comes from the product.
Task reminders only reach a task's owner. A workflow with no product used to leave its tasks unassigned and therefore silent; assignment now falls back to the record's own owner, and to whoever created the record when there is no owner column (contacts do not have one).
A due date counted from one of the record's dates falls back to the moment the step runs when that date is empty — a deal with no close date, say.
Counting from a date that is already well in the past lands the task in the past too: it shows as overdue on the task list, but the "due soon" reminder only fires for a due date still ahead of it. That is worth knowing if you enrol older records into a workflow that dates tasks from them.
A record enrols once per trigger. It only goes through again if the trigger is set to re-enrol on change, or the workflow has a re-enrolment delay, so moving a deal back into a won stage does not create a second task.
When a data source imports history for the first time, that history does not enrol people into automations. A workflow meant to act on imported history has to opt in, and its enrolments are spread out rather than firing at once.

Common questions