CRM Workflow: Designing the Path a Deal Actually Takes
Last updated on · written from the review set and vendor pages; the oldest reading dates from .
Before you start
3 things to have ready. Each one is assumed by a step below; get it first.
A CRM with an automation feature
The workflow runs inside your CRM's automation settings, so you need a plan that includes them and rights to edit them.
Your deal stages, written down
A workflow reads the stage a deal is in, so the stages must exist and be named before you automate anything.
A named owner for the workflow
Someone must decide when the rule changes and answer when it misfires, or it keeps running after the process has moved on.
The steps
7 steps, in order. Tick each one once its check passes; “How you know it worked” is what you should see before moving on.
- Map the path a deal takes today
- Set the stages and fields it reads
- Choose the event that triggers it
- Add conditions that narrow it
- Define the actions it takes
- Build it and run a test deal
- Turn it on and review its runs
Write down each stage a deal passes through, who moves it forward and what must be true for it to move. Use a recent closed deal and follow it from the lead's arrival to the close.
How you know it workedEach stage has a name, an owner and a rule for moving on.
If it failsReps describe the path differently: pick the path of the deals you closed, and write down the gaps for later.
Create each stage and the fields a rule will check, such as deal owner, source or amount, so the workflow can read them. A rule can only react to data the record holds.
How you know it workedEach stage exists in the CRM, and the fields you need are filled on a test deal.
If it failsA field stays empty: make it required at the stage where the rule needs it, otherwise the condition cannot match.
A trigger is the event that starts the workflow, such as a deal moving stage, a form submitted or a record created. Pick the event that signals the moment a human would act.
How you know it workedThe trigger fires when you move a test deal into that stage, and only then.
If it failsIt never fires: check that the event exists in this CRM's trigger list and that the test record meets the entry rules.
Conditions decide which records the trigger applies to: deal owner, source, amount or stage, for example. Add only the conditions needed to keep the rule from firing on records it should not touch.
How you know it workedA test record that fails a condition does not trigger the workflow.
If it failsConditions block everything: loosen them gradually, since a rule joined by AND needs every condition to pass.
An action is what the workflow does when the conditions pass: assign an owner, send a message, create a task, log an activity or request a signature. Choose actions a rep would otherwise do by hand.
How you know it workedEach action runs on a test record and leaves a visible result in the CRM.
If it failsAn action does nothing: check the integration behind it is connected and that the field it writes to accepts the value.
Assemble trigger, conditions and actions in the CRM's workflow builder, name the workflow after what it does and run it on a test deal before any real record. Read the history to see which step ran.
How you know it workedThe workflow's history shows the trigger, each condition and each action as passed or run.
If it failsThe history shows an error: read which step failed, fix that step alone and run the test again.
Activate it for new records only, then review its run history on a fixed rhythm: which records it touched, and whether each outcome was intended. Pause it if a result looks wrong.
How you know it workedEvery record the workflow touched matches the trigger and conditions you set.
If it failsIt fires too often: tighten a condition or add a rule that stops the same record entering again.
Tick each step once its check passes.
Keep going: a step whose check fails is redone, not skipped.
Every step ticked. Run the final checks below.
Did it work?
4 checks before you call it done. If one fails, the line says which step to redo.
Each stage has an owner and a rule
Pass whenA colleague reading your map can say who moves a deal out of each stage and why.
If notredo step 1 · Map the path a deal takes today
The trigger fires only on its event
Pass whenMoving a test deal into the chosen stage starts the workflow; moving it elsewhere does not.
If notredo step 3 · Choose the event that triggers it
Conditions exclude the wrong records
Pass whenA test record that fails a condition does not enter the workflow, and a matching record does.
If notredo step 4 · Add conditions that narrow it
The live workflow fires on the right records
Pass whenAfter some days, the run history lists only records that match your trigger and conditions.
If notredo step 7 · Turn it on and review its runs
A check that fails sends you back to one step, never to the start.
If something breaks
3 failures people hit once the steps are done, and what to do about each.
The workflow fires on every record
Do thisThe trigger is too broad and no condition narrows it: add a condition on stage, owner or source, then run the test again.
Reps get the same message repeatedly
Do thisA record re-enters the workflow each time it matches the trigger: limit re-entry where the CRM allows it, or add a condition that marks the record as already handled.
A rule stops working after a process change
Do thisThe workflow still reads old stages or fields: revise the trigger and conditions when the sales process changes, and let the named owner approve it.
The tools named in these steps
Grouped under the step they serve, not ranked. A name opens our review; Try goes to the vendor.
Grouped by the step they serve, alphabetical within a step. No ranking implied. 10 of the 116 tools we score in Engagement & CRM. ≈ marks our US dollar conversion at European Central Bank euro reference rates of Sep 30, 2026.
Related questions
A CRM workflow is an automated rule inside the CRM: a trigger starts it, conditions filter the records, and actions run. A sales process is the path a deal takes; the workflow automates a step of it.
The trigger is what sets the workflow off, a condition is a test the record must pass, and an action is the change the workflow makes. CRM workflow automation relies on these parts, and each is set and checked on its own.
Start with a repetitive, rule-based move reps forget, such as assigning a new lead or creating a task when a deal changes stage. Build a single workflow, watch its runs, then add more.
Ask each rep who moves deals to describe the path, set their accounts beside the history of a closed deal, and settle the differences before you build anything.
Reps receive repeated messages or tasks and start ignoring them, records get changed that should not be, and the real signal is lost. Tighten the trigger or conditions, and review the run history.
This page walks through one procedure; it does not score tools.
Affiliate linksThis page contains affiliate links: some vendors pay us a commission when you subscribe through their Try button. Scores come from public user reviews, on the same grid for every scored tool. Affiliate disclosure