Write lifecycle back to HubSpot
Pushes the lifecycle stage computed from real product and billing behaviour onto the HubSpot contact, so sales and marketing read the same thing.
Curated by Trishik Shrestha
Growth Marketer at Intempt
About this recipe
When to use it
Lifecycle stage usually reflects what someone set months ago and nobody revisited. This computes it from product and billing behaviour, then writes it onto the contact so sales and marketing read the same thing.
What it delivers
Defines a lifecycle attribute from real product and billing events, then pushes it one way onto the HubSpot contact.
recipe.md preview
Built from the published catalog. Blu's full step prompts load in your workspace when you run it.
---
id: hubspot-lifecycle-writeback
title: "Write lifecycle back to HubSpot"
slashCommand: /hubspot-lifecycle-writeback
group: Workflows
curator: "Trishik Shrestha"
classification:
product: [sales]
mode: [saas]
complexity: standard
procedure:
- step: 1
title: "Define the lifecycle honestly"
builds: attribute
produces: attribute
- step: 2
title: "Push it one way to HubSpot"
builds: workflow
produces: workflow
outputs:
- lifecycle: attribute
- workflow: workflow
---
# Write lifecycle back to HubSpot
Pushes the lifecycle stage computed from real product and billing behaviour onto the HubSpot contact, so sales and marketing read the same thing.Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- 01Integration: hubspotRequired
Outputs
- 01AttributeAI-Derived Attribute produced by this recipe.
- 02WorkflowWorkflow produced by this recipe.
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Define the lifecycle honestlyTrialing, active, at risk or churned, computed from product and billing reality rather than from whatever a form last said. That is the value worth holding in two systems.AI attribute
- 02Push it one way to HubSpotThe HubSpot contact property is updated whenever the lifecycle changes. This field travels one way: Intempt owns it and HubSpot displays it. A field written from both ends needs a stated winner, or the two systems quietly disagree for months.Workflow
Connections required
- hubspotRequired
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /hubspot-lifecycle-writeback in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Trishik ShresthaAI account researchReads a target account's website, pulls out the decision makers, scores the fit against your ICP, and drafts an opener for the rep to edit.View recipe Trishik ShresthaHuman approval for AI actionsHolds the riskier things an AI workflow wants to do, such as a mass update or a send to a big account, for a yes or no in Slack.View recipe Trishik ShresthaAI drafted sales repliesDrafts a reply to every inbound sales email using the thread, the deal stage and the buyer's recent product use, and leaves it in the rep's drafts.View recipe 