Open a deal when someone books a demo
A demo request opens a deal at the Demo scheduled stage, with the person attached and pipeline value updated immediately.
New submission on your "Book a demo" form
Create a Deal in your sales pipeline at the "Demo scheduled" stage and attach the person
One-directional. A submission triggers the action — nothing is written back into your form.
A demo request has a short shelf life. The person asking has budget attention right now, and a request sitting unread in a shared inbox until Monday is the most expensive kind of delay. Opening the deal on submission means the pipeline reflects real demand within seconds.
Revenue teams that report on inbound pipeline value use this one hardest. Because the deal is created at Demo scheduled rather than the first stage, stage-duration reporting stays honest and nobody has to drag cards to catch up.
Setting it up
- 1
Build the demo request form in formformform from the Demo Request Form template and publish it on the page your demo button points at.
- 2
Use conditional logic so When are you looking to implement? only appears once Company Size has been answered, keeping the form short for the smallest visitors.
- 3
In Zapier, set formformform's New Submission as the trigger, pick the demo request form, and pull in a sample submission so the field names appear in the mapping dropdowns.
- 4
Add a Pipedrive Find Person action matched on Work Email with create-if-missing switched on, so a returning prospect reuses the record you already have.
- 5
Add Pipedrive's Create Deal action, choose your sales pipeline, and set the stage explicitly to Demo scheduled instead of accepting the pipeline default.
- 6
Link the deal to the person ID returned by the previous step, and set the organisation from Company.
- 7
Name the deal predictably — Company followed by "demo" — so a rep scanning the stage knows what each card is without opening it.
- 8
Run a test submission, check the card appears in Demo scheduled with the person attached, then turn the Zap on.
What maps where
Using the Demo Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Pipedrive |
|---|---|
| First Name | First half of the person name on the linked contact |
| Last Name | Second half of the person name on the linked contact |
| Work Email | Person email, and the value the Find Person step matches on |
| Company | Organization linked to the deal |
| When are you looking to implement? | Expected close date on the deal, via a Formatter step |
| What problem are you trying to solve? | Note attached to the deal, read before the call |
Variations worth knowing
Map When are you looking to implement? through a Zapier Formatter step into the deal's expected close date. Forecasts become usable straight away, though a self-reported timeline is optimistic often enough that the rep should confirm it during the demo itself.
Chain a Create Activity action after Create Deal, due the same day and assigned to the deal owner. The deal on its own is a card sitting in a stage; the activity is what makes someone open it before the prospect has moved on.
If something isn't arriving
Create Deal was given a person name as text instead of a person ID. Add a find-or-create person step before it and pass the ID that step returns. Pipedrive links deals by ID, and matching on name text quietly leaves the association empty.
Zapier fell back to the pipeline default because the stored stage no longer resolves. Reselect the stage in the action and retest after any pipeline restructure, since the Zap holds an ID pointing at one specific stage in one specific pipeline.
Frequently asked questions
How do I get a demo request to open a deal at the right stage?
Set the stage explicitly in the Create Deal action rather than accepting the pipeline default. Pipedrive drops new deals into the first stage otherwise, and your average time-in-stage figures then include days nobody actually spent qualifying that opportunity.
What happens if the person already exists in Pipedrive?
A find-or-create person step matched on Work Email returns the existing record, and the new deal links to it. Without that step you get a second contact carrying the same address, and the deal history for one buyer splits across two records.
Can the deal update itself once the demo is done?
No. The connection runs one way only: a submission creates the deal, and nothing is read back from Pipedrive into the form. Stage moves, notes and outcomes after that point are ordinary Pipedrive work done by your team.
Related automations
- Add webinar registrants as labelled people
Every webinar registrant becomes a Pipedrive person carrying a registration label you can filter on later.
- Attach customer feedback to the Pipedrive contact
Feedback lands as a note on the customer's Pipedrive record, next to their open deals.
- Log support requests as Pipedrive activities
A customer help submission creates a Pipedrive activity on that customer's record, assigned to the account owner.
- Open a deal with a note for every quote request
A quote request opens a Pipedrive deal and files the full set of answers as a note on the same card.
- Send website enquiries to the Pipedrive Leads Inbox
Each contact sales submission becomes a Pipedrive lead in the Leads Inbox, with the person and organisation already linked.
- Add newsletter signups to Zoho CRM as tagged contacts
Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free