CRM · via Zapier

Connect Zunoform to Pipedrive via Zapier

This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Pipedrive button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.

New responses arrive in Pipedrive as a person and a deal in the stage you choose, so an inbound enquiry is already in the pipeline before anyone reads it.

Start free — no card See native integrations

The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.

Example workflow

Keep the person and the deal connected

For a service enquiry, capture the contact separately from the potential project. A returning customer may submit several projects, so one person can legitimately be linked to several deals. Decide whether a repeated enquiry should update a deal or create another one.

Prepare your Pipedrive account

Choose the pipeline and initial stage in Pipedrive. If your Zap uses separate person and deal actions, pass the person identifier from the first action into the second; a name typed twice is not a reliable link.

Four steps, start to finish

Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.

Create a Zap with a Catch Hook trigger

In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.

Paste the URL on the Zapier card in Zunoform

Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.

Submit a test response so Zapier learns the shape

Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.

Map your fields to Pipedrive

Add an action step and choose Pipedrive. Connect your account, then pick the action that creates a person, an organization, or a deal. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.

Suggested field mapping

Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.

Contact email: Destination: Person lookup or identity; Use a search/update step where supported to avoid creating the same person repeatedly.
Project summary: Destination: Deal title; Use a short description that remains readable in the pipeline.
Budget answer: Destination: Deal notes or value; A budget band is text; do not map it straight into a numeric amount.
Fixed pipeline and stage: Destination: Deal destination; Keep initial routing under your control rather than accepting arbitrary respondent values.

What Zapier receives

The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.

Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Pipedrive action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.

Test before sharing your form

Send two enquiries using the same email but different project names. Inspect the person-to-deal links and confirm the number of deals matches your chosen process.

If the result is missing or wrong

A person may be created even if the later deal step fails. Inspect both actions before replaying the run, and reuse the existing person instead of starting with another create action.

Check the current Pipedrive actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.

Questions people ask

Can one response create both a person and a deal?

Yes. Add two action steps in the same Zap — create the person first, then create the deal and reference the person ID that the first step returns. Map the returned person ID into the deal action explicitly.

How do I route responses into different pipelines?

Use a Zapier filter or paths step keyed on one of your form's answers. A dropdown asking which product someone is interested in can send each option to a different pipeline or stage.

Is this a native Zunoform integration?

No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.