Usage onto the Salesforce opportunity
Keeps the usage fields on an open opportunity current, so the forecast reflects what the account is doing rather than what was said on a call.
Curated by Trishik Shrestha
Growth Marketer at Intempt
About this recipe
When to use it
Opportunity fields get updated from memory after a call. Usage is the one thing nobody has to remember. This keeps the usage fields on open opportunities current.
What it delivers
Describes the usage that matters to the forecast as attributes, then updates them on the open Salesforce opportunity.
recipe.md preview
Built from the published catalog. Blu's full step prompts load in your workspace when you run it.
---
id: salesforce-usage-to-opportunity
title: "Usage onto the Salesforce opportunity"
slashCommand: /salesforce-usage-to-opportunity
group: Workflows
curator: "Trishik Shrestha"
classification:
product: [sales]
mode: [b2b]
complexity: advanced
procedure:
- step: 1
title: "Describe usage for the forecast"
builds: attribute
produces: attribute
- step: 2
title: "Update the open opportunity"
builds: workflow
produces: workflow
outputs:
- usage_attrs: attribute
- workflow: workflow
---
# Usage onto the Salesforce opportunity
Keeps the usage fields on an open opportunity current, so the forecast reflects what the account is doing rather than what was said on a call.Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- 01Event: feature_usedRecommended
- 02Integration: salesforceRequired
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.
- 01Describe usage for the forecastActive seats, the share of them active weekly, how deeply features are adopted, and the trend over the last month. These are the things a rep would otherwise assert from memory.AI attribute
- 02Update the open opportunityIt finds the open opportunity for the account and writes the usage fields onto it. Only the fields Intempt owns are written, never the stage, the amount or the close date, which belong to the rep. A CDP that quietly moves a stage is a forecasting incident dressed up as an integration.Workflow
Connections required
- salesforceRequired
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 /salesforce-usage-to-opportunity 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 