What is this?
Pipeline Stage Changed reacts when a contact is added to, or moved within, a Pipeline — optionally scoped to one stage. Contact data — name, phone, labels, custom fields, source — is already available as variables in the workflow, so you don’t need to ask for it again.Workflows can react to pipeline changes, but the builder has no step that creates or moves Pipeline cards. Contacts are moved on the Pipelines board.
How to use it
1
Create the pipeline first
Create the pipeline and its stages in Pipelines. The trigger can only select pipelines and stages that already exist.
2
Create the workflow
Go to Automation → Create Automation, choose the channel, and pick Pipeline Stage Changed as the Trigger Type. See Create a Workflow.
3
Choose the pipeline and stage
Select the pipeline. To run only when contacts reach a particular stage, also select that stage — otherwise the workflow runs when a contact is added to or moved within any stage of the pipeline.
4
Add the follow-up steps
Add what should happen next — for example send a message or template, assign a teammate with Assign team member, add a note with Create Note/Reminder, or update a field with Update Field or Update Label.
5
Test, then activate
Move a test contact to the chosen stage on the Pipelines board, then check the result in Inbox and in Analytics under Automations. Only then activate the flow — see Manage Live Flows.
Tips
- The pipeline must exist first. The trigger can only select existing pipelines and stages; stage names must match exactly.
- Scope to a stage when you can. Leaving the stage unset fires on every move within the pipeline, not just the one you care about.
Troubleshooting / Technical Notes
- It doesn’t start when a contact moves. Is the workflow Active, and do the trigger’s pipeline and stage match where the contact moved, on the same channel?
- It fires for the wrong stage. Confirm a specific stage is selected on the trigger, and that the stage name matches exactly.