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 Sid Chaudhary
Founder & CEO 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
Coming soonBlu builds a step
- 2
Upsert the lead, never double
Coming soonBlu builds a step
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
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Agree the qualifying signalCreate a segment describing the product-qualified signal (the usage threshold, the feature reached, the seats added) rather than encoding it inside the workflow. The definition is the thing sales and product will argue about, so it needs to live somewhere both can see it.
- 02Upsert the lead, never doubleCreate a workflow enrolling members of the segment and creating a Salesforce lead for each. Use upsert with an external ID rather than create, because a create without a match key is a duplicate generator and the rep pays for it. Map only fields Intempt owns (the score, the signal, the source) and leave Salesforce-owned fields alone. Failure policy is skip-and-record so one rejected lead does not stop the rest. Use the result of "Agree the qualifying signal".
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
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 