Product qualified signal to a Salesforce lead
Creates a Salesforce lead the moment product usage says someone is ready, so a signal the product saw becomes a record a rep can work.
Authored by Trishik Shrestha
Growth Marketer at Intempt
Agentic workflow
Coming soon2 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Agree the qualifying signal
Install nowBlu builds Segment
- 2
Upsert the lead, never double
Coming soonBlu builds workflows
About this recipe
When to use it
The product sees the buying signal first, and it usually dies there because nobody turns it into a record. This creates the lead the moment usage qualifies, and upserts it so a rep never gets the same person twice.
What it delivers
Agrees the qualifying signal as a segment, then upserts a Salesforce lead when an account matches it.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Creates a Salesforce lead the moment product usage says someone is ready, so a signal the product saw becomes a record a rep can work.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- 01Event: feature_usedRecommended
- 02Integration: salesforceRequired
Outputs
- 01SegmentSegment 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.
- 01Agree the qualifying signalThe usage threshold, the feature reached or the seats added, defined as a segment rather than buried inside the workflow. Sales and product will argue about this definition, so it has to live where both can see it.Segment
- 02Upsert the lead, never doubleMembers of the segment are enrolled and a Salesforce lead is created for each, by upsert against an external ID rather than a plain create, because a create with no match key generates duplicates the rep pays for. Only the fields Intempt owns are mapped, the score, the signal and the source, and Salesforce's own fields are left alone. A rejected lead is recorded and skipped rather than stopping the rest.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-pql-to-lead 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 riskier actions an AI workflow wants to take, such as a mass update or a send to a big account, in an approval gate and queue for human review before execution.View recipe Trishik ShresthaAI drafted sales repliesDrafts a Gmail reply for a sales email thread using the thread, deal stage, and recent product activity, leaving it in the rep's drafts for review and send.View recipe 