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.
New submission on your "Request a quote" form
Create a Deal with the requested service and add a Note containing the full form answers
One-directional. A submission triggers the action — nothing is written back into your form.
Pricing requests carry more detail than a CRM field can hold. Service type, timeline, budget and a paragraph describing the job all matter to the rep who calls back, and re-typing them out of an email is how details get lost. This flow opens the deal and files the full answers as a note beside it.
Agencies, contractors and any team quoting bespoke work will recognise the pattern. The deal value is set from the stated budget, so the pipeline is roughly right before anyone has spoken to the prospect.
Setting it up
- 1
Publish your quote request form in formformform from the Quote Request Form template, with Service Type as a dropdown listing the work you actually sell.
- 2
Offer Estimated Budget as a set of ranges rather than a free-text box; ranges map onto a deal value far more reliably than "around 10k-ish".
- 3
In Zapier, trigger on New Submission from the quote request form and pull a sample so the budget and timeline values appear in the mapping picker.
- 4
Add Pipedrive's find-or-create person step on Email Address, then Create Deal linked to that person and to the organisation from Company or Organization.
- 5
Name the deal from Company or Organization and Service Type, so the stage view reads as a list of jobs rather than a list of surnames.
- 6
Set the deal value from Estimated Budget, with a Zapier Formatter step converting the selected range into a single number.
- 7
Set the expected close date from Project Timeline, so your forecast is not full of deals carrying no date at all.
- 8
Add a second Pipedrive action, Create Note, attached to the deal and holding every answer including Project Description in full, then test and switch the Zap on.
What maps where
Using the Quote 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 |
|---|---|
| Full Name | Person linked to the deal |
| Email Address | Person email, and the key the find-or-create step matches on |
| Company or Organization | Organization on the deal, and the first half of the deal title |
| Service Type | Second half of the deal title, or a custom field if you report by service line |
| Estimated Budget | Deal value, converted from a range to a number by a Formatter step |
| Project Description | Note attached to the deal, kept in the requester's own words |
Variations worth knowing
If you keep a product catalogue in Pipedrive, add an Attach Product action after Create Deal and match it on Service Type. The deal value then comes from your own list price rather than the prospect's guess at what the work should cost.
Point Create Deal at a Quotes pipeline with its own stages: requested, quoted, accepted. Mixing unquoted requests into your main sales pipeline makes conversion rates look worse than they are, because half the cards were never real opportunities.
If something isn't arriving
Estimated Budget arrived as text — a range, a currency symbol, or "not sure yet". Add a Formatter step that extracts a number and leaves the field blank rather than writing zero, so unpriced enquiries do not drag your forecast down.
Project Description was mapped into a short field such as the deal title or a single-line custom field. Notes take the full text: map it into the Create Note action's content field, and keep the deal title to the company and service.
Frequently asked questions
How do I turn a budget range into a Pipedrive deal value?
Use a Zapier Formatter step between the trigger and the deal action to convert the selected range into one number, usually the lower bound. Pipedrive's value field expects a number, and a text range will either fail the step or import as zero.
Why put the answers in a note instead of custom fields?
Custom fields are for the two or three values you will filter and report on, such as budget and service type. A note holds the paragraph the person actually wrote. Splitting a project description across fields makes it harder to read, not easier.
Does the note have to be attached to the deal?
It is worth doing. A note attached only to the person does not appear on the deal card, so a rep opening the quote sees a title and a value and nothing else. Attached to the deal, it sits in the timeline they are already reading.
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 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.
- 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