Update Lifecycle
Move the contact to another lifecycle stage, or clear it — read by the dashboard's lifecycle counts, and able to move a deal forward.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Update Lifecycle.
- Choose Update stage and pick a lifecycle stage. If the list is empty, first create one under Settings → Lifecycle.
- Or choose Remove stage to clear it.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- A lifecycle stage mapped under Pipelines → Manage pipelines → Lifecycle sync can also move the contact's open deal — check there first.
- The AI agent can set stages too. Which ones it may use is chosen on the agent's Actions page.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Update Lifecycle under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing that workflow — the thing that makes it run on live conversations — is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- The lifecycle stage must already exist under Settings → Lifecycle. This step picks a stage; it cannot create one.
Set up
- Open the workflow and click + where the move belongs.
- Pick Update Lifecycle.
- Choose Update stage and pick one from the list, or choose Remove stage to clear it.
- Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Lifecycle action
- Update stage — move the contact to a named stage — or Remove stage — clear it entirely.
- Default: Update stage
- Stage
- Which lifecycle stage to move the contact to.
- Limits: Only shown for Update stage; hidden when Remove stage is chosen.
How it works
- The step resolves the contact behind this conversation and writes the chosen stage onto their record, replacing whatever stage was there before.
- Remove stage clears the stage to empty — the contact still exists, it simply has no lifecycle stage until something sets one again.
- The contact goes straight to the stage you pick, even if that skips a stage or goes backward — there is no separate “next stage” step to worry about.
- Each pipeline has a Lifecycle sync section under Pipelines → Manage pipelines: one row per lifecycle stage, with the pipeline stage it leads to.
- Moving the contact to a mapped lifecycle stage moves their already-open deal in that pipeline to the matching stage. Unless that pipeline says otherwise, the deal only moves forward and no new deal is opened.
- The sync acts when the stage changes. A contact created or imported already in a mapped stage is not synced until its stage changes, and merging two contacts never opens a deal.
- May move back on a row lets the deal move back into that stage. Create a deal when the contact has none in this pipeline opens one for a contact who has never had a deal there.
- That move fires Deal Stage Changed for any workflow listening on it, with Moved by set to A rule or import — unless the pipeline's Start Deal Stage Changed workflows switch is off. The section's Sync log lists each change and what it did. A lifecycle stage not mapped in any pipeline does none of this.
- To keep one workflow from starting on these moves while others still do, add a Moved by condition to its Deal Stage Changed trigger and leave out A rule or import.
When it fails
- This conversation has no linked contact: the step fails with this conversation has no contact whose stage could be set.
- The chosen stage no longer exists, deleted since the workflow was built: the step fails with “could not move the contact to stage <id> — it may have been deleted”. Pick another stage and save again.
- A database error reading the conversation's contact fails the step with could not load the conversation's contact.
- A failed move does not stop the run: the step shows as failed in the run's Activity tab and the flow moves straight to the next one.
- The contact's stage is left exactly as it was.
Limits
- It cannot create a lifecycle stage — only move a contact to one that already exists under Settings → Lifecycle.
- It does not fire this workspace's Lifecycle Updated trigger for other workflows. Only a change made in Contacts, the inbox thread header, the app or the public API does that — use Trigger Another Workflow to hand off on purpose instead.
- There is one exception, though: a lifecycle stage mapped in a pipeline's Lifecycle sync (see How it works) can still move an already-open deal.
- That still fires Deal Stage Changed for other workflows, unless that pipeline's switch is off — even though this specific trigger never fires.
- Directly, it only changes the contact's stage itself — it does not touch tags or the assignee. It can still move a deal, as a side effect, per the pipeline rule above.
Use cases
- Move a contact to Customer once Move Deal to Stage records their deal as won, so the dashboard's lifecycle counts reflect the sale immediately.
- Clear the stage when a contact's record needs to leave every named stage's count — the dashboard's lifecycle funnel keeps a separate No stage bucket for them, it does not drop them from the report.
Reading this with an AI assistant? Plain Markdown version.