Open a deal when a quote request arrives

Every quote request opens a deal in your chosen HubSpot pipeline and stage, associated with the person who asked.

When this happens

New Submission on your "Get a quote" form

Do this

Create a deal in the right HubSpot pipeline and stage, associated with the contact

One-directional. A submission triggers the action — nothing is written back into your form.

Pricing enquiries have a habit of living in an inbox until someone remembers them. Opening the deal at submission time puts the enquiry on the board straight away, with a value, a stage and an owner, so the weekly pipeline review reflects what actually came in.

Agencies and service businesses reach for this most. The quote form already asks for service type, scope and budget, and those answers are exactly what a deal record needs. The deal is associated with the contact, so the enquiry and the person sit together.

Setting it up

1
Publish your Get a quote form and make Service Type and Estimated Budget required, since both feed properties on the deal.
2
In Zapier, set formformform's New Submission as the trigger and select the quote form.
3
Add a HubSpot Create or Update Contact action first, keyed on Email Address, so there is a contact for the deal to attach to.
4
Add a second HubSpot action, Create Deal, and choose the pipeline — Sales Pipeline — and the stage, Qualified to buy.
5
Build the deal name from submission data rather than a fixed string: Company or Organization followed by Service Type keeps the board readable at a glance.
6
Map Estimated Budget to the deal amount. If your form offers budget bands rather than a number, send it to a custom deal property and leave amount empty instead of pushing text into a currency field.
7
Associate the deal with the contact from step three by passing that step's contact ID into the Create Deal action.
8
Submit a test quote request, check the deal appears in the right stage with the association intact, then turn 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	HubSpot
Email Address	The contact the deal is associated with
Full Name	Contact name on the associated record
Company or Organization	Associated company, and the first half of the deal name
Service Type	Second half of the deal name, or a custom deal property used for reporting
Estimated Budget	Deal amount
Project Timeline	Deal close date, or a custom deal property

Variations worth knowing

Route by service type into different pipelines

If you run separate pipelines for retainers and one-off projects, add a Zapier path after the trigger that branches on Service Type. Each path creates the deal in its own pipeline and stage, so the two kinds of work never share a board.

Start deals at a stage that matches the budget

Branch on Estimated Budget instead of sending everything to one stage. Smaller enquiries can open earlier in the pipeline for a lighter touch, larger ones at Qualified to buy for immediate follow-up. The form itself stays identical either way.

If something isn't arriving

The deal is created but is not linked to anyone.

Create Deal needs an explicit association. Add the Create or Update Contact step before it and pass that step's contact ID into the deal's associated contact field. Without it, HubSpot makes an orphan deal that never appears on the contact's timeline.

Deal amount shows as zero, or the Zap errors on that step.

HubSpot's amount property accepts a number only. Currency symbols, ranges and words like "around" will fail. Either ask for a plain number on the form, or send budget bands to a custom text property and leave amount for a rep to fill in.

Frequently asked questions

Can one submission create both a contact and a deal?

Yes. A single Zap holds several HubSpot actions in sequence. Create or update the contact first, then create the deal and pass the contact ID into it. Both run from the same submission, in order, and if the first step fails the second does not run.

Which pipeline stage should new quote requests land in?

Pick the first stage that means a human has to act. Qualified to buy works well when the form already asks for budget and timeline. If your quote form is lighter than that, an earlier stage keeps you from inflating the reported value of the pipeline.

Will editing the deal in HubSpot change the submission?

No. Nothing travels back. The stored submission keeps the original answers exactly as they were typed, which is useful months later when a deal has been renamed and re-staged and you want to see what the client first asked for.

Related automations

Add webinar registrants to a HubSpot workflow
Each webinar signup adds the contact to a HubSpot workflow and records which event they registered for.
Create or update a contact from every demo request
Each demo request creates or updates a HubSpot contact with the requester's name, work email, company and phone.
Log a support request as a note on the contact
Each support submission finds the customer in HubSpot and adds a timestamped note with the issue details.
Log product feedback on the customer's record
Product feedback updates the HubSpot contact and logs a note, putting requests where account teams already look.
Set lifecycle stage on every newsletter signup
Subscribers become HubSpot contacts with a lifecycle stage and topic preferences already set for the nurture campaign.
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