Pipedrive Webflow Integration

Overflow builds your website in Webflow and connects it to Pipedrive, so every inquiry becomes a lead or deal your reps can act on. Book a call

Out of the box, a Webflow form does two things. According to Webflow's own Pipedrive guide, it stores the visitor's details in Webflow and sends an email notification. That's it. Nothing routes the inquiry to a rep. Someone copies it into Pipedrive by hand, or forgets to.

And here's the part most teams don't expect: neither the Webflow Marketplace nor the Pipedrive Marketplace lists a native app for this integration. Every Webflow Pipedrive integration is an embed, an automation platform or a custom build. That makes the connection a design decision, not an install.

That's what we engineer. Pipedrive keeps the pipeline your sales team likes. Webflow becomes the website marketing runs without developers. A mapped, tested and documented connection sits in between.

• Publish and launch campaigns without waiting for developers.
• Send every website lead into Pipedrive complete, deduplicated and with its source.
• Keep the pipeline stages, automations and notifications sales already uses.

Let's talk, or first see how we approach Webflow integrations.

Why there's no one-click Webflow Pipedrive integration

There is no native Webflow app for Pipedrive and no Pipedrive app for Webflow. You connect them through Pipedrive embeds, an automation platform or the two APIs.

This surprises teams coming from HubSpot. Webflow's Form Connector app supports Salesforce, HubSpot, Slack, Airtable, Notion, Attio and Snowflake. Pipedrive isn't on that list. So the app you expect to find simply doesn't exist.

The Pipedrive Marketplace does list third-party connectors for Webflow forms, such as the Webflow Forms Sync app by Outfunnel. Those are tools you subscribe to, not an official Webflow or Pipedrive integration. That's also why most of what ranks for this topic is tool vendors explaining why you need their middleware.

The old way: install whatever template a tool vendor suggests. Find out months later that half the leads are duplicates and nobody knows which campaign they came from.

The Overflow way: map the data flow first. Pick the least complex method that meets it. Document it so your team owns it.

Read more about how we approach Webflow integrations, or browse the full Webflow integrations hub.

Who this is for

B2B marketing leads, founders and commercial directors whose sales team works in Pipedrive. Your website is either a WordPress site marketing can't update without a developer, or a Webflow site where leads still get copied over by hand.

The trigger is usually one of these: a funding round, a rebrand, new service lines or markets, organic traffic that has gone flat, or sales complaining that web leads arrive late or incomplete.

Is the problem Pipedrive, or the website?

Teams sometimes start looking at another CRM when the friction actually sits in the publishing layer: slow page builds, rigid templates, forms nobody can change. If Pipedrive works for your reps, replacing the website is the smaller project. So we ask that question first.

On HubSpot or Salesforce instead? See our Webflow HubSpot integration and Webflow Salesforce integration.

Four ways to connect Webflow and Pipedrive

Webflow's guide groups the options into four methods, and they can be combined. Our rule: use the least complex method that meets the requirements. Here's each one on the same terms.

Pipedrive Web Forms, Chatbot and Web Visitors embedded in Webflow

Pipedrive Web Forms placed in a Webflow Code Embed element send submissions straight into Pipedrive as leads or deals. No third-party tool sits in between, and new deals trigger your Pipedrive notifications and automations.

• Best for: teams already paying for LeadBooster who want the fastest route and can accept Pipedrive's form styling.
• Pipedrive requirement: Web Forms and the Chatbot are part of the LeadBooster add-on, included on Premium and higher and available as a paid add-on on Lite and Growth. Creating forms needs deals admin permission.
• Webflow requirement: a paid Site plan or paid Workspace plan for Code Embed.
• Design control: low. The form is styled in Pipedrive, not Webflow.
• Limits: images only show in the standalone shared link, not the embed. Each page can run only one Chatbot playbook.

The Chatbot offers four playbook types: get more leads, book more meetings, qualify and route leads, and chat with your leads. It's installed as site-wide head code. The Web Visitors tracker is a separate paid add-on, not part of LeadBooster. It reports visiting companies under Leads > Web Visitors and goes in the site head or through Google Tag Manager.

Native Webflow forms through Zapier, Make or n8n

Keep native Webflow forms, with full design control and submissions stored in Webflow. An automation platform then creates the Pipedrive person, organization, lead, deal or activity. Zapier, Make, n8n and viaSocket all list Webflow to Pipedrive integrations.

• Best for: marketing-designed forms, and leads that also need to reach a second tool such as Slack or a spreadsheet.
• Pipedrive requirement: any plan. No LeadBooster needed.
• Design control: full. The form is built in Webflow.
• Limits: a cost per task or operation, one more system to own and monitor, and duplicates if nobody adds a search step before "create". Zapier also needs the Webflow form to have received at least one submission before you can connect it. Polling triggers run on a schedule, instant triggers fire on the event.

Custom build with the Webflow and Pipedrive APIs

A Webflow form_submission webhook sends each submission to your own endpoint. That's a serverless function or a Webflow Cloud app, because Webflow sites don't run backend logic. The endpoint searches Pipedrive for the person and only creates one if none exists.

• Best for: custom deduplication, complex field logic, multi-step forms, or data flowing back into the website.
• Pipedrive requirement: the Pipedrive API covers persons, organizations, deals, leads and activities, authenticated by API token or OAuth 2.0. Every Pipedrive plan includes an API token.
• Design control: full, plus logic before the data reaches Pipedrive.
• Limits: development time and upkeep. We only use it when the data flow needs it.

Upkeep is real. Webflow deprecated its Data API v1 on 31 March 2025. Pipedrive's v1 endpoints went out of support on 1 August 2026, while lead creation still runs on v1 in the current reference. APIs change, so a custom connection needs an owner, not just a builder.

MCP servers for AI-assisted work

Both products publish a hosted MCP server, so an AI assistant can read Pipedrive records and edit Webflow content in one session. Useful for content and pipeline work. But as Webflow's guide says plainly, MCP is assistant-driven: nothing fires on its own when a form comes in at night. It's not a lead-routing method. More on Webflow MCP.

Can a native Webflow form send data to Pipedrive without middleware?

Yes, through a form_submission webhook pointed at your own endpoint, or a custom form action.

There's a catch with the second option. According to Webflow, a custom form action bypasses Webflow's form handling. Submissions are no longer stored in Webflow, email notifications stop and native reCAPTCHA won't work as expected. That's why we usually prefer the webhook route: it keeps the Webflow record as a fallback.

What you get when Overflow connects Webflow and Pipedrive

You don't get "a Zap". You get a connection that's mapped, tested and documented, so your team knows where every lead goes.

A data-flow map before anything gets built

We list every form on the site with the event it represents (demo request, quote, download, newsletter), the Pipedrive object it should create (a lead in the Leads Inbox or a deal in a pipeline stage), the fields it fills and who owns follow-up. Same rule as every Overflow integration: map the trigger, fields, permissions, destination, failure handling and owner before installing anything.

Leads or deals: matched to how your sales team works

Pipedrive works with persons, organizations, leads and deals. Leads are potential deals that wait in the Leads Inbox. Deals move through pipeline stages. So we decide with sales: does a demo request become a deal straight away, or a lead to qualify first? Leads inherit their custom field structure from deals, so fields are designed once and work for both.

No duplicate persons

Search before create. That's a Find or Create Person step in Zapier, a search-then-create flow in n8n, or a persons search call in the API, always before any lead or deal is made. Without it, returning visitors and multiple forms create a second person record every time, and reps lose the history.

Source and campaign data sales can see

Pipedrive leads and deals carry source fields: a system-set source origin and an editable source channel that admins configure in Company Settings > Data fields. On top of that, hidden fields on your Webflow forms pass UTM and landing page data into custom Pipedrive fields. Marketing can tie a deal back to the campaign that started it.

We only promise the attribution the chosen method supports, and we say upfront where it stops. For example, every lead created through the API gets the origin "API", whichever campaign brought it in. Your hidden fields carry the detail.

Consent handled, not assumed

Pipedrive's Chatbot and Web Forms don't detect consent management signals, so the site has to block those scripts until consent is given. Embedded Web Forms set a Cloudflare cookie, and spam protection adds a reCAPTCHA cookie. We configure the consent behaviour. For the legal assessment, check with your own advisor.

One form component across CMS templates

Services, events and resources usually live in Webflow CMS collections. We build one reusable form component into your CMS templates, with hidden fields that tell Pipedrive which page or offer the lead came from. Add a new service page, and its form already works.

A plan for when something fails

We decide upfront where the backup record lives, who gets alerted and who checks it. With native Webflow forms plus a webhook or automation, the submission stays in Webflow as a fallback. One detail shows why ownership matters: a Pipedrive webhook is deleted after three consecutive days without a successful delivery.

Tested on the live site, handed over to marketing

We send test submissions from the published site, check the records in Pipedrive and confirm automations and notifications fire. Then we hand over: documentation, live training and video walkthroughs. Ownership, not dependency.

What usually breaks, and how we prevent it

The dangerous failures don't throw an error. The form still says "thank you", the visitor leaves happy, and the problem only surfaces when sales asks where the leads went. Here's what fails silently, how you'd notice, and the rule we follow.

• Duplicate persons. What fails silently: every new submission creates a new person, so a returning buyer ends up with split history. You notice when a rep finds the same contact twice. Our rule: find-or-create logic on every flow, before any lead or deal is made.
• Blank fields after a rename. What fails silently: someone renames a Webflow field or a Pipedrive custom field, the lead still arrives, but the field is empty. You notice when a rep can't see the budget or service the visitor picked. Our rule: a field map in the docs and a test submission per field.
• Leads stop after a form edit. What fails silently: Zapier triggers are tied to a specific form, so a duplicated or rebuilt form no longer feeds Pipedrive. You notice when the Leads Inbox goes quiet. Our rule: handover docs show marketing exactly what to check after every form change.
• A Pipedrive webhook disappears. What fails silently: after three consecutive days without a successful delivery, Pipedrive deletes the webhook, and any reverse sync to Webflow stops. Nothing on the website looks wrong. Our rule: a named owner and an alert on every webhook.
• Phone numbers or dropdown values in the wrong format. What fails silently: values land in Pipedrive unusable for filters or automations. Our rule: normalise them before they reach Pipedrive.
• Every CMS page reports as the same form. What fails silently: leads arrive, but nobody knows which service or event page they came from. Our rule: hidden fields with page context on every template.
• Scripts firing before consent. What fails silently: LeadBooster components don't read consent signals, so they load regardless of the banner. Our rule: block them until consent is given.

Which method fits your setup?

Start from your situation, not from a tool.

• You already pay for LeadBooster and your forms are simple: embed Pipedrive Web Forms.
• Design matters and forms are short: native Webflow forms plus an automation platform, with a find-or-create step.
• Qualifying questions, multi-step demo forms or pricing calculators: a native Webflow form plus webhook and API, so the logic runs before data reaches Pipedrive.
• Leads also need to reach another tool: an automation layer with a named owner.
• The website needs Pipedrive data back, for example case studies or customer logos updated when deals close: API or automation in reverse, from Pipedrive webhooks to Webflow CMS items.

We choose during strategy, based on your Pipedrive plan, your forms and who edits them after launch. Not on habit.

Moving your site to Webflow without losing rankings or leads

Many Pipedrive teams run on WordPress, often with a plugin or an embedded Pipedrive form. The worry is always the same: lost rankings, or leads that stop the week you launch.

Here's what we protect:

• Every old URL mapped with 301 redirects in Webflow.
• Metadata, schema markup and internal links.
• Every form rebuilt and mapped to the same Pipedrive fields, so your automations keep firing.

Pipedrive stays untouched. Persons, deals, pipelines and automations don't move. Only the publishing layer does.

How fast? We migrated Nedcargo from WordPress to Webflow in 4 weeks. Our typical builds take six to eight weeks. Your timeline depends on your site, so we agree it after discovery, not before.

More on Webflow migration, WordPress to Webflow migration, Webflow vs WordPress and our Webflow SEO services.

How we deliver your Webflow Pipedrive integration

It's the same six-step process as every project at our B2B Webflow agency, with Pipedrive built into each step.

1. Strategy and discovery. We audit the site, forms, Pipedrive pipelines, fields, automations and add-ons (LeadBooster, Web Visitors), and write the data-flow plan.
2. Design system in Figma. Including form components and their default, error and success states.
3. Webflow development. CMS, components and the Pipedrive connection, using the method chosen in strategy.
4. Content migration and technical SEO. With SEO and AI Search built in from the start.
5. QA. Live test submissions, Pipedrive records, consent behaviour and performance.
6. Handover. Documentation, training and support.

Cost and timing are agreed upfront. Communication is fast. One client put it this way: "they keep their promises."

Proof from B2B teams we've built for

To be straight with you: we don't have a published Webflow Pipedrive integration case yet, so you won't find duplicate rates or monthly lead counts here. We'd rather show nothing than numbers we can't back. What we can show is how we build and migrate B2B websites in Webflow.

• Nedcargo: migrated from WordPress to Webflow in 4 weeks, with 98+ Lighthouse performance.
• BlinkLab: 7 weeks from strategy to launch, built for its next growth phase after a $17.5M raise.
• Aumatics: 300%+ marketing ROI and 8+ new high-ticket clients.

"Communication was always smooth and fast, the quality of their work was excellent." Marketing Manager, Informer Group

"Communication is excellent, and they keep their promises, something we cannot always say about other online marketing agencies." Quinten van der Kraaij

Evaluating any partner for this, us included? Ask how many forms they connected, how fields were mapped and how they prevent duplicates. See all client cases.

Who does the work

Overflow is an official Certified Webflow Partner. Jort Steinebach, Certified Webflow Developer with 40+ Webflow sites, leads development, CMS architecture and the integration. Niels Voshol covers strategy, SEO and AI Search, with 40+ B2B projects behind him.

Worried a small team can't carry it? The two senior specialists you talk to are the two who build it. No handoff to juniors. More about us.

What does a Webflow Pipedrive integration cost?

There's no public price list. We scope the work and agree a fixed price and timeline before we start, so you know both before you commit.

What drives the scope

• The number of forms and CMS templates.
• The method: an embed is lighter than an automation, and both are lighter than an API build.
• A connection on an existing Webflow site, or part of a full build or migration.
• How much source and campaign data you need in Pipedrive.
• Languages and markets (see Webflow localization).

For timing: typical builds take six to eight weeks, and we migrated Nedcargo from WordPress to Webflow in 4. Your timeline is agreed after discovery, not guessed before it.

When we'll tell you not to buy the build

Our rule is the least complex method that meets the requirements. So if you already pay for LeadBooster, your forms are simple and you can live with Pipedrive's styling, an embedded Pipedrive Web Form may be all you need, and we'll say so. The same goes for an API build: if an automation with a find-or-create step covers your data flow, we won't sell you custom code to maintain.

Third-party costs you own

• A paid Webflow Site or Workspace plan, needed for Code Embed and custom code.
• Your Pipedrive plan (current prices on Pipedrive's pricing page).
• LeadBooster, if you embed Pipedrive forms on Lite or Growth. It's included on Premium and higher.
• Web Visitors, as a separate add-on, if you want it.
• Automation platform fees for Zapier, Make or n8n, if that's the method.

You see all of it before we start. No funnies, no surprises. Book a call and we'll scope it with you.

Webflow Pipedrive integration FAQ

Does Pipedrive have a native Webflow integration?

No. Neither marketplace lists a native app, so you connect through Pipedrive embeds, an automation platform or the APIs.

Do I need LeadBooster to connect Webflow to Pipedrive?

Only if you want to embed Pipedrive Web Forms or the Chatbot. Native Webflow forms connected through automation or the API don't need it. LeadBooster is included on Premium and higher, and a paid add-on on Lite and Growth.

Should Webflow forms create leads or deals in Pipedrive?

It depends on how sales qualifies. Leads land in the Leads Inbox to be qualified; deals go straight into a pipeline stage. We decide per form with your sales team.

How do I stop duplicate contacts in Pipedrive?

Search before you create. Add a find-or-create person step before any lead or deal is made, in Zapier, n8n or your own API code.

Is the Webflow Pipedrive sync two-way?

It can be. Form data usually flows from Webflow to Pipedrive. Deal changes can update Webflow CMS items through Pipedrive webhooks and the Webflow API, or an automation template. That takes extra build and an owner.

Can I track which campaign a Pipedrive deal came from?

Yes, within limits. Hidden fields pass UTM and landing page data into custom Pipedrive fields, alongside Pipedrive's own source channel field. We tell you upfront what the chosen method can and can't capture.

Do embedded Pipedrive forms work with a cookie banner?

Not automatically. Pipedrive's Chatbot and Web Forms don't read consent signals, so the site has to block them until consent is given. For the legal side, check with your own advisor.

Which Webflow plan do I need?

A paid Site plan or paid Workspace plan. Code Embed elements and site-wide custom code, which Pipedrive embeds and tracker scripts rely on, aren't available on the free Starter plan.

How long does a Webflow Pipedrive integration take?

It depends on the number of forms, the method and whether it's part of a build or migration. Typical builds take six to eight weeks; we agree your timeline after discovery.

Do you connect only the forms, or build the whole site?

Both are possible. Most clients have us build or migrate the site and engineer the connection as part of it, so forms, templates and tracking are designed together.

Ready to keep Pipedrive and give marketing a faster website?

Your website shouldn't be the reason a lead waits in an inbox. Keep Pipedrive for sales, move the website to Webflow, and we engineer the connection so every lead arrives complete and attributed.

Let's talk.

Want to show up in ChatGPT, Gemini, Perplexity and AI Overviews too? Start with an AEO audit.