WS Form PRO - Pipedrive

The form decides which stage each deal is born in

Your sales team works a pipeline with well-defined stages. Contacts arrive from the services page, from a campaign landing page and from a demo form, and all three end up in the same inbox.

With this integration, the stage a deal starts in is set by the form, not by the person who receives it, so each entry point calls for its own form.

WS Form Pro with the Pipedrive integration adds an action that creates deals in a specific pipeline and stage of your account. Pipeline and Stage are two settings of the action. A general contact form can leave the deal in the first stage and a demo form in the one that fits someone who already asked to talk.

What the Pipedrive action does

• When it runs: on save, on submit or in both cases.
• Pipeline and Stage: the pipeline and stage that receive the deal.
• Field mapping: links form fields to fields of the deal, the organization or the person. Each object needs its minimum field mapped: Deal Title for the deal, Organization Name for the organization and Person Name for the person.
• Custom mapping: sets a Pipedrive field to a value or a WS Form variable, for example #submit_id inside the deal title.
• Notes: adds notes to the deal, organization or person that are created, and you choose which ones each note goes to.
• Deduplication: optional check for existing records by Organization Name, Person Name, Person Email or Deal Title.
• Form from a pipeline: in Add New, Pipedrive tab, you pick a pipeline and a stage and WS Form builds the form already configured.

An example with the demo form

A demo form can map the name to Person Name, the email to Person Email, the company to Organization Name and the message to a note. A custom mapping with #submit_id in the deal title leaves an identifier that links the deal to the form submission.

If you want to avoid the same person generating repeated records, turn on deduplication by Person Email. That option only works if you have mapped an email field to the person's email field.

This is a setup suggestion; adapt it to your pipeline.

Mapping minimums and the action scope

The action asks for a minimum per object: Deal Title for the deal, Organization Name for the organization and Person Name for the person. Deduplication by email depends on an email field mapped to the person.

The integration is an add-on for WS Form Pro, not for WS Form Lite, and it needs a Pipedrive account. Each action points to one pipeline and one stage; if you need several stages, the most direct way is one form per entry point.

Connecting the form to Pipedrive

1. Install the add-on the same way as WS Form Pro.
2. Open WS Form, Settings, Pipedrive tab, press Connect and follow the steps.
3. For a ready-made form, go to WS Form, Add New, Pipedrive tab, click a pipeline and choose the stage. If one is missing, use the refresh icon.
4. For an existing one, open Actions, press Add and choose Add to Pipedrive.
5. Define Pipeline, Stage, the minimum mapping and, if you want, deduplication; save.

Forms and CRMs in the catalog

For the base plugin, see WS Form Pro. To send forms to other CRMs, the catalog includes Ninja Forms HubSpot, Gravity Forms HubSpot and WPForms Salesforce Addon.

Answers about WS Form Pipedrive

What is created when someone submits the form?

A deal in the chosen pipeline and stage, along with the organization and person data you have mapped.

Which fields do I have to map at minimum?

One per object: Deal Title for the deal, Organization Name for the organization and Person Name for the person.

Can duplicates be avoided?

Yes, with the optional deduplication by organization, person, the person's email or the deal title.

Can I add notes to the deal?

Yes, and you choose whether they go to the deal, the organization or the person.

Does it work with WS Form Lite?

No. It requires WS Form Pro.