CRM

Your pipeline is only as honest as the leads someone remembered to type in

A lead fills in a form. It becomes an email, and whether it becomes a Deal in Pipedrive depends entirely on whether the person reading that email has five minutes and remembers to do it before moving on to the next thing. Some weeks that works. Some weeks it does not, and the forecast quietly gets a little more wrong.

Pipedrive is built to make a pipeline easy to see and easy to trust. That trust only holds if what goes into it is complete, and a manual step between a form and a Deal is exactly where completeness leaks out.

  • REST API with a per-user API token
  • Persons, Organizations, Deals, Activities
  • From €1,700 plus service fees
The tool

What Pipedrive is, and how its data model is different from a bigger CRM

Pipedrive is a sales-pipeline CRM built around Deals as the central object, with Persons and Organizations attached to them and Activities tracking the follow-up. It is deliberately simpler than Salesforce or Dynamics — fewer configuration layers, a documented REST API, and a Marketplace of ready-made apps rather than a platform for deep custom development.

That simplicity is the appeal for the small and mid-size sales teams who use it, and it is also the limit worth knowing before you scope a connection: there is no equivalent of Salesforce's Apex or Dynamics' plugins for complex server-side logic, so anything more elaborate than field mapping and stage automation tends to live outside Pipedrive, in the integration itself.

What goes wrong

Three things that go wrong between a website and Pipedrive

These are the three that come up in almost every audit of a Pipedrive account fed by a form that only sends email.

The forecast is missing the leads nobody typed in

On a busy week a handful of web leads never make it from inbox to Deal, and they simply do not exist as far as the pipeline is concerned. Management trusts a forecast that was never complete, and finds out why only when the quarter closes short.

What you see instead

Every form submission becomes a Person and a Deal in the right pipeline the moment it arrives, whether anyone is watching the inbox or not. The forecast is complete because nothing depends on someone remembering.

A won deal does not tell the website anything

A deal marked Won in Pipedrive should, in most businesses, trigger something — a welcome email, an account being provisioned, a customer-only price list switching on. Without a connection it triggers nothing, and somebody has to remember to go and start that process by hand, in a second system, from memory.

What you see instead

Marking a deal Won fires a webhook that starts the next step automatically — an account created on the site, a notification to whoever fulfils the order, a welcome sequence — the same second the deal closes.

The same organisation exists under three names

Different form fills spell a company name differently — with or without "B.V.", with or without a typo nobody caught — and Pipedrive creates a new Organization each time instead of recognising the one that is already there. A rep loses the deal history the moment the name does not match exactly.

What you see instead

New Organizations are matched on a more reliable key than a free-text name where one is available — a domain, a KVK number — before creating anything new, so history stays attached to the company it belongs to.

The bill for doing it by hand

What manually entering web leads into Pipedrive costs

At 60 web leads a month and four minutes each to open the email, create a Person and a Deal, and pick the right pipeline stage, that is four hours a month — not large in isolation, but it is four hours where the actual cost is the leads that get skipped on a busy day, not the ones that get typed in slowly.

The real number worth asking is not "how many hours" but "how many leads never became a Deal at all". Ask a sales manager to compare form submissions in the website's own analytics against Deals created in Pipedrive for the same month; the gap between those two numbers is usually the more uncomfortable one.

What we build

We build the thing on the other end too

With Pipedrive the connection tends to be small and the value comes from what happens the moment a deal is won, so it is worth designing the "won" webhook as part of the same project rather than as a later add-on.

A connection needs two ends. Plenty of agencies will build you the API call and hand you a JSON payload; that is the easy half. The harder half is what the data lands in — a website, a webshop, a portal your customers log into, an internal tool that replaces a spreadsheet. JKC builds both ends, which is why the connections we build tend to keep working: nothing about the receiving side is a black box to us.

API integrations

The connection itself: authentication, field mapping, rate limits, retries and a queue that survives the other system being down for an hour. Built against the documented API where there is one, and against whatever the vendor really offers where there is not.

Websites

WordPress sites that read from your systems instead of repeating them by hand: a careers page fed by your HR system, a team page that follows your payroll, prices and availability that are the real ones.

Webshops

WooCommerce shops where the order is the last time anyone types it: it becomes an invoice in your accounting package, a label at your carrier, a stock mutation in your warehouse, and a line in your CRM, on its own.

Web applications

When the process does not fit any standard product: a customer portal, a quoting tool, a planning board, a dashboard that reads three systems at once. Built on your data, with your systems as the source instead of a copy of them.

What can be connected

What can be connected between Pipedrive and your website

Built against the REST API with a scoped API token. Pipedrive's own webhooks cover most of the "something changed" side of this without polling.

  • Web forms as Persons, Organizations and Deals

    Matched against existing Persons and Organizations before creating anything new, placed in the right pipeline and stage based on which form or page it came from.

  • Deal won or lost, as a trigger

    A webhook on stage change that starts whatever should happen next on the website side — account creation, a welcome flow, switching on customer-specific pricing.

  • Activities and calendar

    A meeting booked through the website's own scheduler landing as an Activity on the right Deal, so a rep never has to enter what already happened somewhere else.

  • Products and price lists into a quoting flow

    Pipedrive's Products, read out so a website-based quote builder can offer the same items and prices a rep sees inside the tool.

How it works

How a connection gets built at JKC

The same four steps every time, whichever tool it is. Nothing here is a workshop you pay for: step one exists because scoping a connection wrong is the single most expensive thing that can happen to it.

  1. 1. We look at what is actually being retyped

    Not "which fields exist" but "which fields does somebody currently move by hand, how often, and what breaks when they get it wrong". Most projects turn out to need two or three flows, not a full two-way sync of everything. That conversation is what keeps the quote where it is.

  2. 2. We pick the route, and say why

    A maintained connector from the vendor, a platform like Make or Zapier, or a custom integration against the API. Cheapest first, not custom first: if a supported plugin does exactly what you need, that is the answer and we will tell you so. Custom is for the cases where the off-the-shelf option would need so much configuring that it becomes the fragile option.

  3. 3. We build it to survive the other system

    Every connection ships with retries, a queue and an idempotency key, so an order that arrives while the other side is down is delivered later rather than lost, and a retry does not create a second invoice. On a test environment first where the vendor offers one, so the first thing your real administration sees is a working connection.

  4. 4. We hand it over with the failure modes written down

    Which alerts you will get, what each one means, what to do about it, and who to call. Plus the credentials in your own name, in your own vault — not in ours. A connection nobody but us can maintain is a connection you do not own.

More about system integrations at JKC

After it goes live

A connection that fails silently is worse than no connection

This is the part most quotes leave out. A connection that stops working without telling anyone is worse than manual work, because with manual work at least somebody notices when it does not get done. Every connection JKC builds is monitored, and the monitoring is not an upsell — it is in the service fee.

An alert per failed message, not a monthly report

A message that does not get through raises an alert the same hour, with the record it was about. Not a dashboard you have to remember to look at.

Replay, not re-enter

Anything that failed sits in a queue and can be sent again once the cause is fixed, in order. Nobody goes back through yesterday to find the four orders that did not land.

We watch the vendor's changes, so you do not have to

APIs get versioned, deprecated and rate-limited. When a vendor announces a change that affects your connection, adjusting to it is part of the service fee, not a new project.

What it costs

From €1,700, and the biggest variable is who built the other end

For Pipedrive specifically, this is usually one of the smaller connections in the bank: the API is simple and there is little to configure beyond field mapping, so the €1,700 starting point often covers the whole first project.

A connection starts from €1,700 plus a monthly service fee, which covers the monitoring, the queue and keeping up with the vendor's API changes. Work outside a fixed scope is €95 per hour.

What moves the number is not the tool — it is how well the system on the other end is known. If JKC built your website, your webshop or your web application, we already know its data model, its edge cases and where its stock numbers really come from, and a connection into it is mostly configuration and testing. If it is a system we have never opened, we start with a short technical check of both sides and quote after that, so you are not paying hourly for us to work out the basics.

Two more things that move it, in our experience more than anything else: whether the tool has a real API or only a CSV export, and whether the sync has to go both ways. One-way is roughly half the work of two-way, because two-way means deciding, per field, which system wins when they disagree — and that decision is the expensive part, not the code.

Questions

Frequently asked questions about connecting Pipedrive

Yes, custom fields on Persons, Organizations and Deals are readable and writable through the REST API the same as standard ones, referenced by a field key rather than the label you see on screen.

The only thing to watch is that a custom field's options — a dropdown's list of values, say — have to be created in Pipedrive first; the API cannot invent a new option on the fly, only select from what already exists.

Often next to this one

Tools that often sit next to this one

Almost nobody connects one tool. These are the ones that come up in the same conversation, either because they sit in the same part of the business or because people ask for the two together.

See all integrations

Free, 10 minutes

Not sure where the manual hours actually go?

That is what the Growth Scan is for. Ten minutes, no sales call attached: you get back where the double work sits, which connection would pay for itself first, and which one honestly would not.

Do the free Growth Scan