If you want your WordPress forms to create Pipedrive contacts and deals automatically, your first decision is how the form sends data out: webhooks or email parsing. Webhooks are usually cleaner, more reliable, and cheaper to run in Zapier because you can skip the “parse the email” steps.
Routing WordPress Forms to Pipedrive: A 4-Form Example
In a real consultation, the website had four different WordPress forms that all currently landed in one inbox. The goal was to route each form into Pipedrive differently:
- Inquiry form: Create or update the person, then create a deal in the first intake stage
- Contact us form: Create or update the person, then create a deal in the first intake stage
- Newsletter popup: Create or update the person only
- Brochure request: Capture limited info, then create or update the person (and optionally create a deal)
The key idea is one form submission should map to one “path” in your automation.
Step 1: Choose webhooks or email parsing
Option A: Webhooks (recommended)
A webhook means the form sends a structured payload (usually JSON) directly to an endpoint when someone clicks Submit.
Why it is usually better:
- Cleaner data (the website already knows the field structure)
- Fewer points of failure than parsing inbox email templates
- Often fewer Zapier tasks per submission because you can skip parsing steps
In the consultation, the recommended approach was:
- Create 4 separate webhook URLs (one per form)
- Build one Zap per form or a single Zap with routing logic, depending on complexity
- Map each form’s data into Pipedrive in the correct way
Option B: Email parsing (fallback)
Email parsing is when your form sends a notification email, and Zapier parses the email contents to extract fields.
This can work, but it adds complexity:
- You have to maintain parsing rules
- Email templates change over time
- You usually add more steps just to identify the form type and extract fields
In the consultation, email parsing was described as possible, but less clean and less reliable than webhooks.
Step 2: Structure your routing (4 webhook endpoints)
If you can get webhooks, the simplest and most reliable structure is:
- Webhook URL 1: Inquiry
- Webhook URL 2: Contact us
- Webhook URL 3: Newsletter
- Webhook URL 4: Brochure request
This prevents “form detection” logic later. Zapier already knows which form fired because each form has its own endpoint.
Step 3: Build the Zap logic in Zapier
Common pattern for each form
Most Pipedrive lead-intake automations follow a repeatable pattern:
- Trigger: Catch Hook from your form submission (or parsed email)
- Action: Find Person in Pipedrive by email
- Action: Create Person (only if not found)
- Action: Create Deal (for your deal forms)
- Optional actions:
- Add tags or custom fields
- Send an “intake received” email
- Notify your team in Slack or email
- Add the person to your newsletter tool
Important: Person-first is the safe default
In Pipedrive, a deal is typically linked to a person. In practice, most reliable automations find or create the person first, then create the deal so the deal is properly associated.2
Step 4: Estimate Zapier task costs per submission
Zapier pricing is based on tasks. Each form submission will run your workflow and consume tasks for most “actions.”
In the consultation, a simple rule of thumb was:
- Webhook approach: often 2 to 3 tasks per submission
- Email parsing approach: often 4 to 5 tasks per submission
As a concrete example, Zapier’s basic plan was described as $20/month for 750 tasks. If you budget about 5 tasks per lead, that supports roughly 150 submissions per month on that plan. (as of early 2026 — check current pricing at zapier.com/pricing)
If you want a deeper explanation of what counts as a task (and what does not), see our Zapier task guide: Understanding Zapier Tasks: A Cost Guide for LinkedIn CAPI Integration.
Troubleshooting checklist
If your WordPress → Pipedrive automation is flaky, check these first:
- The form is actually sending the webhook to the correct URL
- The webhook payload includes the fields you expect (especially email)
- Your Zapier trigger is set to the correct webhook (webhooks are unique per Zap)
- You are deduplicating people by email before creating a new record
- Your Pipedrive field mapping matches the right custom fields
Need help setting this up?
If you want an expert to build this with you and train you at the same time, book a free discovery call.
