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.
New submission on your "Contact sales" form
Create a Lead in Pipedrive's Leads Inbox with a linked person and organisation
One-directional. A submission triggers the action — nothing is written back into your form.
Sales teams protect their pipeline. A form fill from an unknown visitor is not a deal yet, and dropping it straight into a stage skews every forecast that comes off that pipeline. The Leads Inbox exists for exactly this gap, and this flow fills it automatically.
It suits companies where a rep qualifies before anything is committed — agencies, B2B software, consultancies. The lead arrives with the person and organisation already linked, so the first action is a phone call rather than ten minutes of typing.
Setting it up
- 1
Publish your contact sales form in formformform from the Lead Generation Form template, keeping Work Email and Company Name required so every lead arrives with something a rep can act on.
- 2
Embed it on your pricing and contact pages with the two-line snippet rather than linking out, so the form sits where buying intent is highest.
- 3
In Zapier, add formformform's New Submission trigger and select this contact sales form by name — do not point the Zap at a general enquiries form that also collects support questions.
- 4
Choose Pipedrive's Create Lead action so the record lands in the Leads Inbox instead of an active pipeline stage.
- 5
Inside that action, set the linked person from Full Name and Work Email, and the linked organisation from Company Name, so the lead is not an orphan record.
- 6
Give the lead a scannable title: Company Name followed by the value of What are you most interested in? (check all that apply) reads better in the Inbox than a bare person name.
- 7
Assign an owner — either a fixed rep, or a Zapier path that branches on Industry if you run territory ownership.
- 8
Submit a test enquiry through the live form, confirm the lead appears in the Leads Inbox with both the person and the organisation attached, then switch the Zap on.
What maps where
Using the Lead Generation 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 | Name on the person linked to the lead |
| Work Email | Email on the linked person, and the value to match on if you add a lookup step first |
| Company Name | Organization linked to the lead, created if it does not already exist |
| Job Title | Job title on the person record, so reps can see seniority before dialling |
| What problem are you trying to solve? | Note attached to the lead |
| How did you hear about us? | Lead source custom field |
Variations worth knowing
If your team works from an activity list rather than the Leads Inbox, swap Create Lead for Create Person plus Create Organization and add a follow-up activity. You lose the qualification buffer, and you gain a contact that is searchable across the whole CRM straight away.
Add a Zapier path on Company Size so enterprise enquiries land in a named rep's Leads Inbox and everything else goes to a shared queue. It costs one extra step, and it stops your largest inbound enquiries waiting behind twenty small ones.
If something isn't arriving
Company Name was blank, or the field was optional on the form. Pipedrive will not invent an organisation from an email domain. Make Company Name required on the contact sales form, and add a Zapier fallback value rather than leaving the link empty.
The Create Lead action has a fixed owner selected. Replace it with a Zapier path branching on Industry, or set the owner from a lookup step. Leads that all land on one person tend to get worked last, which is rarely what territory rules intend.
Frequently asked questions
Should form enquiries go to the Leads Inbox or straight into a pipeline?
Use the Leads Inbox when a human qualifies before you commit to a forecast. Anything created as a deal counts towards pipeline value immediately, which is fine for demo requests and misleading for a cold contact form. Leads convert to deals in one click.
Will this create a duplicate person if the same visitor enquires twice?
Create Lead can link to an existing person when the email matches, but Pipedrive does not deduplicate for you by default. Add a Find Person step keyed on Work Email before the lead action and reuse the match instead of creating a second contact.
Can I route leads to different reps automatically?
Yes, inside Zapier rather than inside the form. Add paths that branch on Industry or Company Size and set a different owner on each. The form has no knowledge of your rota; it only sends each submission onward for Pipedrive to act on.
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.
- 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.
- 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