CRM integration · Updated November 15, 2026

Pipedrive integration

We connect Pipedrive to WordPress, Webflow, Astro or Next.js sites and custom software, so each site enquiry becomes a lead or a deal with the right person attached. We use Pipedrive's web forms, its API or both, and record consent on the contact.

Rated 5.0 out of 5,72 Google reviews

Pipedrive at a glance

Connects
Web Forms and the chatbot from LeadBooster, the Leads Inbox, the REST API and webhooks.
WordPress
A Web Forms embed snippet, or your form plugin sending entries to the API from the server.
Webflow
A Web Forms snippet in an Embed element, or native Webflow forms sent to the API by a function we host.
Astro or Next.js with Sanity
Our own form, with a server route that creates the person and then the lead or deal.
Custom software
The REST API (v2 where it exists, v1 for leads) and v2 webhooks.
Complexity
Low to medium. Embeds are simple; API work has to fit Pipedrive's daily token budget.
Typical setup
1 to 2 days for Web Forms, 3 to 8 days for API forms with deal routing.

How we connect Pipedrive

  • WordPress

    Each Pipedrive web form gives you a link and a code snippet to paste into a block. The only official Pipedrive plugin on WordPress.org is the LeadBooster chatbot. Connectors for Contact Form 7, WPForms and Gravity Forms come from third parties, so we often send entries to the API from our own small plugin, which also checks for an existing person first.

  • Webflow

    Neither Webflow's nor Pipedrive's marketplace lists a native app. We paste the Web Forms snippet into an Embed element, or keep the native Webflow form and send it to the API through a small function we host, since a standard Webflow site can't run server code. Embedded Pipedrive forms let you change colours, fonts and field shapes, but not add your own CSS.

  • Astro or Next.js with Sanity

    Our own form posts to a server route. The route finds or creates the person, then adds a lead to the Leads Inbox or a deal in the right pipeline and stage, tagged with the page and campaign it came from. The API token stays on the server.

  • Custom software

    Booking tools, quote calculators and portals create deals through the REST API and hear about changes through webhooks, which default to v2 since March 17, 2025. Pipedrive is moving endpoints from v1 to v2 a piece at a time, and adding a lead is still v1 only, so we watch its deprecation notices.

What organizations use Pipedrive for

  • Sales pipelines for growth-stage companies

    A demo request or quote form becomes a deal in the right pipeline and stage, owned by the right rep, with the source page attached.

  • Quote requests for energy and industrial suppliers

    Requests with project size, location and timing land as leads, so sales can qualify them before they turn into deals.

  • Sponsorship pipelines for nonprofits

    Sponsor and partner enquiries get their own pipeline, kept apart from the donor database, with each stage and next step visible.

What to watch out for

  • Consent and privacy

    Pipedrive's web forms have no consent field by default, so we add a required opt-in field with your policy text. Marketing status starts at "No consent", and Campaigns only emails Subscribed contacts; double opt-in records the date, time and IP address, which is the proof CASL asks for. Pipedrive opened a Montreal data centre in May 2026 for Canadian sign-ups; ask Support where an existing account sits.

  • Plans and deal limits

    Web Forms are part of LeadBooster, which comes with Premium and Ultimate and costs extra on Lite and Growth. If your account is at its open-deals limit, a form set to create deals fails and Pipedrive saves only the contact and a note.

  • API budget

    As of November 15, 2026, each company gets a daily budget of 30,000 tokens times a plan multiplier times seats, plus a burst limit per 2 seconds. A list call costs 20 tokens and a search 40, so a sync that polls every few minutes can run out before the day ends. We use webhooks instead of polling, and a dedicated integration user, because each API token belongs to one user and only one can be active.

Sources

Checked against Pipedrive's docs on November 15, 2026.

  1. Web Forms Leads or deals, embed code, styling.
  2. LeadBooster add-on Included in Premium and Ultimate.
  3. Consent on web forms No default consent field.
  4. Leads Inbox
  5. Pipedrive API v2
  6. Leads API
  7. API authentication
  8. Rate limiting Daily token budget and burst limits.
  9. Webhooks v2 by default since March 17, 2025.
  10. Data security and data centres
  11. Montreal data centre Announced May 13, 2026.
  12. Double opt-in for marketing contacts
  13. LeadBooster Chatbot by Pipedrive The official WordPress plugin.
  14. Webflow and Pipedrive No native app.

Questions about Pipedrive

Do we need LeadBooster for Pipedrive web forms?

Yes. Web Forms are part of LeadBooster, which is included in Premium and Ultimate and sold as an add-on for Lite and Growth. Without it, we send your site form to the API instead.

Should site enquiries become leads or deals?

Leads, if someone qualifies each enquiry first: they wait in the Leads Inbox until someone converts them. Deals, if every enquiry should go straight into a pipeline stage.

Can Pipedrive keep our data in Canada?

Pipedrive says new Canadian accounts are hosted in its Montreal data centre, which opened in May 2026. Ask Pipedrive Support where an older account is hosted and whether it can move.

Can the forms be in French?

Web form labels and messages are text you write, so a French form is a second form with French wording, placed on the French pages. Check the built-in text, such as error messages, before launch. Your team can also switch Pipedrive itself to French.

Want site enquiries in Pipedrive?

Tell us what your forms collect and how your pipeline runs. We'll say whether Web Forms or the API fits, and what it takes.

Book a call