On this page
What HubSpot supports natively
Before building a workflow, check what HubSpot already automates under Settings > Objects > Contacts > Lifecycle Stage.
| Setting | What it does |
|---|---|
| Set lifecycle stage when a contact or company is created | A default stage for new records |
| Set lifecycle stage when a deal is created | Updates associated contacts and companies when their first deal is created |
| Set lifecycle stage when a deal is won | Updates associated contacts and companies when a deal is closed won |
| Set lifecycle stage when a lead is associated | Updates the stage when a lead record is associated |
| Sync lifecycle stages | Copies a primary company’s stage to its contacts (one-way) |
None of these settings sets values backward. Workflows follow the same rule: the Edit record action only moves the default lifecycle stage forward, and a backward set fails with an error in the action log. To move a record back on purpose, clear the property in one action, then set the earlier stage in the next.
How to set lifecycle stage with a workflow
- List the stages the settings don’t cover. For most teams that’s Lead (if not set on create), MQL and SQL.
- Build one workflow per stage, or one routing workflow for all of them. Either way, one workflow owns each stage. Name it so its job is obvious, for example “Lifecycle | Set MQL | Contact”.
- Use a clear entry rule. For MQL: score above your threshold and lifecycle stage is Lead or earlier. The second filter stops the workflow touching contacts sales already owns.
- Use Edit record to set the stage. Add a clear action before it only if this workflow is meant to move records backward, and document why.
- Decide on re-enrollment. A contact that drops back to Lead and re-qualifies only goes through again if re-enrollment is on for the trigger that means “qualified”. See how re-enrollment works.
- Test with a record before turning it on, and choose whether to enroll existing contacts that already meet the criteria.
Common mistakes
- Duplicating the deal settings. A workflow that sets Opportunity on deal creation, alongside the setting that does the same, gives you two writers and confusing property history.
- Clear-and-set in a broad workflow. It moves every enrolled contact backward, including customers. Narrow the enrollment criteria first.
- Several teams each “fixing” lifecycle. That’s the most common reason lifecycle stage keeps changing.
Where Jetstack AI fits
Jetstack AI Projects builds this from your written stage rules. Put the stages, each entry rule and which workflow owns which stage in the brief. Jetty turns it into a plan you review, and approving the plan generates the properties, lists and workflows; you review those and approve deployment separately, then check the receipt of what was created, read back from HubSpot. Workflows are created switched off, so you test before turning them on. Projects is currently in limited release; see what Projects can build.
In a portal that already has lifecycle automation, a Workflow Audit shows every workflow that writes lifecycle stage and flags competing actions between them. Projects doesn’t edit those workflows: it builds the corrected replacement as a new, switched-off workflow, and you retire the old ones in HubSpot.
Sources
- Use contact and company lifecycle stages (HubSpot Knowledge Base)
- Manage how lifecycle stages sync between objects (HubSpot Knowledge Base)
- Troubleshoot common workflow errors (HubSpot Knowledge Base)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Workflows & automation
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects