A workflow responds to an event and runs a series of actions. Use one to update records, create tasks or notes, start fulfillment, or enroll a contact in a sequence. Workflows execute real changes; the editor is not just a diagram.
Choose a precise trigger#
- Open Workflows and choose New workflow. Enter a name and description.
- In Editor, start from scratch and choose a trigger: record created, record updated, field value changed, task created, or note created.
- Choose the required object and field. For record updates, selecting a field limits which changes trigger a run; leaving it blank listens for any supported field update.
Scope the trigger before importing or updating many records. A broad trigger can start work for each affected record, not just once for the whole operation.
Add actions and conditions#
Use a block's plus control to add the next step and fill its required inputs. A Filter stops nonmatching runs; If creates true and false paths. Delay and Delay until wait before continuing. Check the workflow timezone in Settings when scheduling a specific time.
Choose Create or update record with an appropriate matching field when repeated events should update an existing record instead of creating duplicates. Start fulfillment needs a deal and template; a contact trigger cannot infer which deal you intend.
Publish, enable, and exercise#
An owner or admin publishes the configured draft, then uses Enable workflow to allow new runs. Publishing and enabling are separate: edits do not change the running version until published, and publishing does not turn an off workflow on.
On an enabled, published workflow, Trigger workflow lets you select a record and queue a real run. Use a record appropriate for the actions: this is not a dry run. Switching off stops new runs; work already in flight continues on its original snapshot.
Read outcomes and boundaries#
Open Runs, select a run, then inspect its blocks for outcomes, inputs, and errors. A completed run may have stopped at a filter without performing later actions. A failed run does not automatically retry, and earlier successful changes remain.
There is no send-email action: use Enroll in sequence for email follow-up. Workflow-made changes do not trigger other workflows, so put dependent actions in the same workflow rather than expecting a chain between workflows.