WPForms Pipedrive - WordPress Plugin

How to Configure WPForms Pipedrive to Send Form Submissions to Your CRM

WPForms Pipedrive is useful not on its own, but as part of a specific workflow: someone submits a form on your WordPress site, and a sales rep sees a new contact or deal in Pipedrive without manually copying data. This guide focuses on the practical setup rather than marketing copy: what to prepare, how to connect the account, which fields to map, how to verify the result, and where problems usually show up.

The main goal is to make sure each website submission reaches your CRM in a clear, usable format. Clicking the connect button is not enough. You need to decide in advance what should be created in Pipedrive: a contact, a deal, or a sequence of related actions; which form fields must be required; and which values should go into the pipeline, stage, amount, owner, and custom fields.

This guide is intended for site owners, marketers, web admins, or WordPress administrators who already use WPForms and want to connect their forms to Pipedrive. We will also look at custom field limitations, test submission checks, scenarios for different form types, troubleshooting, and close alternatives.

Where the Plugin Fits Into the Lead Flow

With a standard contact form, the site administrator gets an email and manually transfers the data into the CRM. That approach breaks down quickly as submission volume grows: an email can be missed, a customer name can be copied incorrectly, the lead source can be lost, and the sales rep may learn about the inquiry too late. WPForms integration with Pipedrive solves exactly that part of the process by turning a form submission into an action inside the CRM.

According to the WPForms documentation, the add-on can create or update a contact in Pipedrive and create a deal linked to a person and an organization. It is important to understand this before you start configuring it. If you only need a list of people for follow-up, Create/Update Person is enough. If each submission should go straight into your sales pipeline, you need Create Deal with a selected pipeline and stage.

You should not treat the integration as a replacement for a well-designed form. Pipedrive only receives the data the user submitted and that you mapped correctly. If the form does not include a phone number, budget, service, or lead source, the CRM cannot fill those fields in on its own. That is why setup starts not with authorization, but with planning the submission itself.

What Happens After the Form Is Submitted

The workflow looks like this: the visitor fills in the fields, WPForms validates required values and format, and then triggers the configured Pipedrive integration for that specific form. The add-on then sends the data through the Pipedrive API, and the CRM creates or updates the entity based on the action you selected.

This leads to a practical rule: if the form submits successfully but nothing appears in Pipedrive, do not check only the CRM. The cause may be conditional logic, a mismatch in custom field types, an unselected pipeline, a disabled add-on, or a JavaScript error on the form page.

Which Entities You Need to Distinguish

In Pipedrive, a contact and a deal serve different purposes. Person stores information about the individual: name, email, phone number, and relationship to an organization. Deal describes a sales opportunity: title, value, pipeline, stage, owner, and deal-specific custom fields. WPForms Pipedrive supports both workflows, but the fields are not interchangeable.

If you create a custom field in Pipedrive for a lead/deal, it belongs to deals and leads. That field will not automatically become available for the Create/Update Person action in WPForms. For person data, you need a separate field on the Person side. This is a common reason administrators do not “see” the field they need in the mapping dropdown.

Who This Integration Works Well For, and When Another Route Makes More Sense

WPForms Pipedrive works especially well for websites where the form is the starting point of the sales process. That includes consultation requests, quote requests, service selection forms, demo bookings, catalog requests, B2B inquiries, partner forms, and landing page leads. In those cases, the sales rep needs more than an email notification - they need to see the lead in the pipeline, assign an owner, and continue the process inside the CRM.

The integration is especially convenient if your team already works primarily in Pipedrive. In that case, the WordPress form becomes a data source rather than a separate storage layer you constantly have to reconcile with the CRM. For marketers, it also helps enforce lead-handling discipline: the submission does not sit in an inbox, it becomes a pipeline item.

When the Setup Is a Good Fit

• Your site uses lead generation forms, and every submission should be sent to Pipedrive without manual transfer.
• You need to create a deal in the right pipeline and at the right stage immediately after the submission.
• You need to map standard form fields to person, deal, or organization fields.
• You need conditional sending, for example, sending only submissions with a selected service or a budget above a certain threshold.
• Your team wants to use Smart Tags for the deal title, value, or other dynamic details.

When You Should Consider an Alternative

If your site already runs a complex automation flow with dozens of conditions, repeated actions, webhook chains, duplicate checks, and data exchange with multiple services, the direct add-on may be too limited. In that case, it makes sense to evaluate an integration through Zapier, Make, Uncanny Automator, or a form solution where the Pipedrive feed supports more objects and error logging.

If Pipedrive is not your primary CRM and you only need to send emails, store submissions in WordPress, or export CSV, connecting a CRM may be unnecessary overhead. The right integration should reduce manual work, not create one more place to monitor.

What to Check Before Installing It on WordPress

Before installation, it helps to put together a workflow checklist rather than a purely technical one. If you skip this step, the settings may look simple, but after testing you may discover that the deal is created without an owner, the budget field does not appear, and the sales rep has no idea where the customer came from.

Pipedrive Version, Access, and User Role

The official WPForms documentation says the Pipedrive add-on is available at the Elite level and requires a current version of WPForms that supports this add-on. This article does not cover purchasing or activating a license, but before setup you should confirm that the add-on is available in your installation and appears under WPForms - Addons.

On the Pipedrive side, you need a user who can grant the app access to data and who can see the required pipelines, stages, organizations, and custom fields. If permissions are limited, the connection may succeed only partially, and the needed fields or pipelines may not appear in the form.

Form Structure

A minimum CRM form usually includes a name, email or phone number, a message, and consent to data processing. But for Pipedrive, it is better to add the fields that help qualify the lead right away: service, budget, city, urgency, lead source, customer type, page URL, or selected package.

Not every field has to be visible to the user. For example, WPForms hidden fields can be used for internal data, including UTM parameters passed through Smart Tags with query variables. This does not replace full attribution tracking, but it helps you send at least a basic lead source into the CRM when a visitor arrives through a parameterized link.

Pipedrive Fields and Data Types

The most important limitation involves custom fields. The WPForms documentation lists the field types supported for mapping: text, large text, numerical, phone, and date. Other Pipedrive field types may not appear in the builder dropdown. Because of that, it is usually better to create simple fields in Pipedrive for your form data rather than assume every complex field type will be available in WPForms.

Practical check: if a field exists in Pipedrive but does not show up in WPForms, first check the entity and the type. A deal field will not behave like a person field, and an unsupported type is often best replaced with a simple text or numeric field if that works for your process.

Installing the Add-on and Making the First Pipedrive Connection

Installation starts in the WordPress admin dashboard. Go to WPForms - Addons, find Pipedrive, and install the add-on. After activation, it should become available in integrations. If the add-on list does not refresh, the WPForms documentation recommends using Refresh Addons on the add-ons page.

After activation, go to WPForms - Settings - Integrations. Open the Pipedrive section and click Add New Account. The site will redirect you to the Pipedrive login page, where you need to grant WPForms access to your data. After confirmation, you will return to WordPress and see the Connected status.

How to Tell the Connection Worked Correctly

A green connection status is only the first check. It shows that the WordPress site was granted permission to work with Pipedrive. But that still does not mean every form is already sending submissions into the CRM. The integration must be enabled separately inside each individual form.

Open the form you need in the builder, go to Marketing - Pipedrive, and click Add New Connection. The connection nickname is visible only to the administrator, so use a clear name such as “Consultation Request - deal” or “Catalog Request - person.” That makes maintenance easier when one form ends up with multiple Pipedrive actions.

What Not to Do at This Stage

Do not build a complex form with dozens of fields right away. Start by testing the minimum setup: name, email, phone number, one service field, and a message. Once a test submission consistently appears in Pipedrive, you can add budget fields, UTM fields, owner assignment, labels, and conditional logic.

Configuring Submission Actions: Person, Deal, Pipeline, and Stage

The most important screen is not in the global settings but inside the form itself. This is where you choose what WPForms should do after the form is submitted. The official documentation describes two actions: Create/Update Person and Create Deal. On a real website, you often need not one universal option, but a deliberate combination.

Create/Update Person Action

This option works well when the main goal is to create a contact or update an existing person by email. In the settings, you map name, email, phone, organization, and any additional fields. This scenario is useful for consultation signup forms, material requests, or forms where the deal is created later by a sales rep after qualification.

The main advantage of this action is that it lowers the risk of duplicate contacts. If the email matches an existing person, Pipedrive can update that record instead of creating a new one. But this is not a magic database cleanup tool: if users enter different email addresses or phone numbers in inconsistent formats, duplicates are still possible.

Create Deal Action

This action is the right choice when every qualified submission should go directly into the pipeline. In the settings, you specify Deal Title, Deal Value, pipeline, stage, person name, person email, phone, organization, and custom fields. Pipeline and stage are pulled from Pipedrive, so they need to be prepared in advance.

It is best to make the deal title dynamic, but keep it short. For example, you can build it from the person’s name, service, and city using Smart Tags. Titles that are too long make the CRM harder to work with, while overly generic ones like “New Inquiry” force the sales rep to open every card just to understand what it is.

When to Use Multiple Connections

The WPForms tutorial for a custom Pipedrive form notes that you can add more than one Pipedrive connection to a single form. In practice, this is useful if you need to create both a person and a deal with different logic or different field sets. But start with one connection first. That makes it much easier to find the problem if the test submission does not go through.

A safe setup rule: start with a minimal deal sent to a separate test stage, then add extra fields and conditions. If the integration stops behaving as expected after you add a new field, go back to the last working configuration and verify the field type in Pipedrive.

Field Mapping Without Losing the Meaning of the Lead

Field mapping is where the administrator turns a form into a CRM record. Errors here do not always look like obvious technical failures. The integration may successfully create a deal, but the sales rep ends up with a blank phone number, the wrong organization, or an unclear budget. That is why mapping should be checked as business logic, not as a form where you simply “fill in the dropdowns and save.”

Standard Fields

Name, email, and phone are best collected through separate WPForms fields rather than one large text field. That makes them easier to map to person fields in Pipedrive and lets you use the email address to update an existing contact. If the form accepts international inquiries, check the phone format in advance and avoid forcing a local pattern that could block legitimate users.

Use the organization field carefully. If the site handles B2B inquiries, organization may be required. For B2C submissions, the company field is often empty, and that is perfectly normal. Do not force users to enter a company name just for the sake of the CRM if your workflow does not actually need it.

Deal Title, Value, and Owner

Smart Tags are convenient for the deal title. For example, the title can include the service and the person’s name: {field_id="service"} - {field_id="name"}. Take the exact field IDs from the builder rather than copying them from someone else’s example. Map Deal Value only to a numeric field or another clearly controlled value, otherwise the CRM may receive a value that your team cannot actually use for forecasting.

Owner should be assigned based on a clear rule. If all submissions go to one department, you can assign a single owner. If the form includes a branch or service selector, the owner may depend on the user’s answer, but that kind of setup needs especially careful testing. An owner error does not stop deal creation, but it does break the follow-up process.

Custom Fields and Hidden Data

Additional fields are useful for UTM tags, submission page, selected service, preferred contact time, newsletter consent, or customer status. WPForms Hidden Field and Smart Tags let you collect internal values the user does not see. This is especially helpful for Pipedrive: later, a marketer can filter deals by source or campaign.

But there is a limitation: complex Pipedrive field types are not always available in WPForms. If you need to pass a dropdown, multiple options, monetary, or address field, first confirm that the type is supported in the current mapping screen. If it is not, use a simple text field in Pipedrive or keep the exact value in notes/message so the data is not lost.

Practical Example: A Consultation Request Becomes a Deal

Let’s look at a concrete scenario. A services website has a “Get a Consultation” form. The team wants qualified submissions to create a deal in Pipedrive immediately, enter the sales pipeline, preserve the traffic source, and show the sales rep which service the visitor selected. This is a common setup for an agency, repair service, B2B consulting company, education provider, or local business.

Goal and Preparation

The goal is to create a deal after form submission with contact details, phone number, email address, selected service, and source. Before setup, prepare a pipeline in Pipedrive, a stage for new submissions, simple custom fields for service and source, and the user who will own the deals. In WPForms, prepare a form with the fields Name, Email, Phone, Service, Budget, Message, and a Hidden Field for source.

Setup Steps

1. Open the form in the builder and make sure the required fields are actually marked as required.
2. In Marketing - Pipedrive, add a new connection and name it after the form scenario.
3. Select the Create Deal action, then choose the connected account.
4. Build the Deal Title from the selected service and the user’s name using Smart Tags.
5. Select the pipeline and stage where new submissions should land.
6. Map person name, email, and phone to the corresponding individual form fields.
7. Map service, budget, and source to the appropriate custom fields if they are available.
8. Enable conditional logic if only submissions with a selected service or a filled email field should be sent to the CRM.
9. Save the form and send a test submission with clear demo data.

Expected Result

After submission, the user should see the confirmation message in WordPress, the administrator should see the entry in WPForms, and the sales rep should see a new deal in Pipedrive at the selected stage. The deal card should include the name, email, phone number, and additional fields. If you passed UTM values through a hidden field, verify that the value landed not in some empty field, but in the correct custom field.

A Note About Conditional Logic

Conditional logic is useful, but it is also a common source of “invisible” problems. If the condition is too strict, the form may submit, the email may be sent, but the Pipedrive connection will not run. For the first test, temporarily disable the condition or use test data that definitely meets it. Then re-enable the condition and run a second test.

How to Verify Everything Before Launching the Form

Testing should cover three levels: the public-facing form, the WPForms record, and the Pipedrive deal card. If you check only one level, it is easy to miss a partial failure. For example, the form may show success while the CRM does not create the deal, or the deal may be created while the notification email never arrives because of a mail configuration issue.

Checking the Public Form

Open the page in a regular browser window and in incognito mode. Submit the form with valid data, then try skipping a required field and entering an invalid email address. WPForms should show validation errors and refuse to send an incomplete submission. If the button spins forever or the form does not respond, check JavaScript, caching, and optimization conflicts first.

Checking Entries and Emails

If your WPForms version stores entries, open the test submission record and compare its values to what was sent to the CRM. Check the notification email separately as well. According to WP Mail SMTP recommendations, email delivery problems are often caused not by WPForms itself, but by the site’s WordPress mail configuration and the lack of SMTP or proper domain authentication.

Checking Pipedrive

In Pipedrive, locate the created deal by title, email, or stage. Check the owner, pipeline, stage, person, organization, and custom fields. If the budget field did not populate, go back to the mapping and inspect the data type. If the person was created but the deal was not, check which action is selected in the connection and whether any conditional logic is skipping the deal scenario.

Quick conclusion: a form is only ready to go live when the test submission is visible on the page, in the entry, in the email, and in Pipedrive exactly in the form the sales rep needs in order to act on it without asking the administrator for clarification.

Practical Use Cases for Different Types of Forms

The same integration can support multiple use cases if you avoid trying to build one universal form for the entire site. It is better to create separate forms for different user intents and choose the appropriate Pipedrive logic inside each one.

Quote Request Form

For a pricing or estimate form, it is important to send the selected service, approximate budget, and comment into the deal. If the budget is chosen from a range, it is not always a good idea to send it as the actual deal value. In many cases, it is more reliable to store the range in a custom field and let the sales rep set the exact amount after the conversation.

Demo or Consultation Request

Here the key outcome is speed of response. Add phone number, preferred contact time, company, and a source field. You can send the deal to an early stage such as “New Inquiry” so the sales rep sees it at the beginning of the pipeline and does not confuse it with already qualified opportunities.

Lead Form on an Ad Landing Page

For a landing page, hidden fields with UTM data and the page URL are especially important. If the user came through an ad link, those values help tie the deal back to the campaign. After testing, check not only whether the deal exists, but whether the source fields are populated when the page is opened through a URL with parameters.

Partner or Dealer Form

Partner forms usually need more context: region, company type, website, request volume, and area of interest. Not all of that belongs in the deal title. Some of it is better stored in custom fields so the pipeline does not become cluttered while the sales rep still gets enough information for the first conversation.

Why a Submission Did Not Reach Pipedrive and How to Find the Cause

It is best to troubleshoot from simple to complex. Do not start by reinstalling the plugin. First determine where in the chain the submission disappears: the form does not submit, no entry is created, the email does not arrive, the Pipedrive connection does not run, or the CRM rejects part of the fields.

The Form Submits, but No Deal Is Created

Symptom: the user sees a successful submission message, but no new deal appears in Pipedrive. Possible causes include: no connection added to this form, person selected instead of deal, conditional logic not met, or the pipeline or stage having been changed in Pipedrive after setup.

What to Check

• Open Marketing - Pipedrive for this specific form, not just the global integration settings.
• Check whether the correct connection is enabled and whether the action Create Deal is selected.
• Temporarily simplify the condition so the test submission definitely passes.
• Save the form again after changing the pipeline or stage.

If the deal appears after simplifying the setup, add the conditions back one at a time. That will show you which rule was blocking the submission.

The Required Custom Field Is Not Visible in WPForms

Symptom: the field exists in Pipedrive but does not appear in mapping. Most often, the cause is the field entity or type. A lead/deal field belongs to the deal side, while a person field belongs to the contact side. On top of that, WPForms supports only a limited set of custom field types for Pipedrive mapping.

How to Fix It

Create the field in the correct Pipedrive entity and use a simple supported type if that does not break your workflow. Then refresh the builder page in WordPress. If the field still does not appear, check the Pipedrive user’s permissions and save the connection again.

The Email Does Not Arrive, but Pipedrive Received the Submission

Symptom: the deal exists in the CRM, but the administrator did not receive the email. At that point, the problem is no longer the Pipedrive add-on. Check Settings - Notifications for the form, along with the recipient address, sender settings, and SMTP. If the site sends mail through the default WordPress mail function, deliverability may depend on the hosting provider and the domain’s DNS settings.

The Form Does Not Submit on the Page

Symptom: the button spins, nothing happens, or the form shows an error. Start by testing the form in WPForms preview. If everything works in preview, the issue may be on the page itself: caching, JavaScript minification, a theme conflict, a popup, deferred script loading, or an optimization plugin.

A safe test is to temporarily exclude the form page from aggressive optimization, clear the cache, and test again. If that helps, re-enable optimization settings gradually. Do not disable form protection and validation just to work around the error.

Deals Are Created, but the Data Is Incomplete

Symptom: the deal exists in the CRM, but the phone number, budget, service, or source is missing. Check whether the corresponding field is filled in the WPForms entry. If the value is present in the entry, the issue is in mapping or in the Pipedrive field type. If the value is empty in the entry, the issue is in the form itself, the hidden field, the query parameter, or the field’s conditional logic.

Quick Troubleshooting by Failure Point

Where the Problem Appears	Likely Cause	First Action
Public form	Validation, JavaScript, cache, or theme conflict	Check preview and disable optimization for the test page
WPForms entry	The field was not filled in or the hidden value was not inserted	Check field options, Smart Tags, and the test URL
Pipedrive connection	Incorrect action, condition, or pipeline	Simplify the connection and send a test submission
Pipedrive card	Unsupported custom field or wrong entity	Verify entity, type, and user permissions

Safe Improvements Without Editing the Plugin

WPForms Pipedrive usually does not require PHP snippets. The official documentation already provides enough built-in tools: Smart Tags, Hidden Field, conditional logic, themes, custom CSS, and separate Pipedrive connections. Because of that, it is safer to improve the workflow through settings rather than by editing plugin files.

Pass the Lead Source Through Hidden Fields

If you run advertising campaigns, add hidden fields for source, medium, and campaign. As the default value, you can use Smart Tags with query variables if that approach fits your site. Then map those hidden fields to simple text custom fields in Pipedrive.

The check is simple: open the form page with parameters in the URL, submit a test form, and confirm that the values appear both in the entry and in the deal. If a value is blank, do not blame Pipedrive right away. First verify that the query parameter name matches the one specified in the Smart Tag.

Style the Form With Built-In WPForms Themes

WPForms supports form styling through Settings - Themes. For lead generation, this is more practical than using random CSS from the internet: the styles are saved together with the form, and preview lets you see the result before publishing. If the form is embedded through a block or Elementor, keep in mind that local styles may apply only to that specific page.

Do Not Modify Core or Add-on Files

Any edits to WPForms or add-on files will disappear after an update and may break form submission. If you need to change the appearance, use the form theme settings or separate CSS in a safe WordPress location. If you need to change the CRM submission logic, first look for a built-in option in the connection settings, field mapping, or conditional logic.

When WPForms Pipedrive Is the Right Choice

WPForms Pipedrive is a strong choice if your WordPress site already collects inquiries through WPForms and your sales team works in Pipedrive and wants contacts or deals delivered without manual transfer. The main strength of the solution is the direct path from form to CRM, along with a clear builder, field mapping, pipeline and stage selection, conditional logic, and custom field support within the confirmed field types.

Before publishing, do not stop at successfully saving the settings. Create a test submission and review the entry, the notification email, and the Pipedrive card. Make sure the sales rep gets enough information for the first contact, and that the marketer can see the source or campaign if the form collects that data.

If the workflow fits your site after testing, you can download the ZIP archive and roll out the integration on one form first, then apply the working setup to the rest of your forms. A phased launch like this is safer than connecting every submission to the CRM at once without a test pipeline and a clearly verified mapping.