# Pipedrive Integration Developers UK

Source: https://dijituldevelopments.co.uk/pipedrive-integration/
Updated: 2026-10-18

> dijitul developments builds Pipedrive integrations for UK businesses: connecting deals, people and products to Xero, your website, quoting tools and in-house systems through Pipedrive's API v2 and webhooks. We design within Pipedrive's token-based rate limits so syncs keep running. Every integration starts with a free chat and a fixed-price quote.

## Problems this solves

- Won deals are retyped into Xero and the job system
- Web enquiries arrive by email and someone copies them into Pipedrive
- A Zapier chain broke and nobody noticed for a fortnight
- Integrations stop mid-afternoon with "429 Too Many Requests"
- Product prices in Pipedrive do not match the price list
- Your team cannot see invoices or payments from inside Pipedrive

## Key facts

- Pipedrive's plans are now Lite, Growth, Premium and Ultimate, renamed in 2025
- API v2 endpoints cost fewer rate-limit tokens than their v1 equivalents
- Each company account has a daily token budget, based on plan and seats, shared by all integrations
- Burst limits apply per user over a rolling two-second window
- Webhooks push deal and person changes to us instead of polling
- Custom fields are addressed by hash keys, so we map them explicitly

## Why Pipedrive integrations matter

Pipedrive is popular with UK sales teams because it is simple: a visual pipeline, quick activity logging and little admin. The simplicity ends at the edge of the pipeline. Once a deal is won, someone usually retypes it into the accounting system, sets up the job or project, and emails the office. Enquiries arrive from the website by email and get copied in by hand. Those gaps are where we come in.

We start by watching the process for a day or two: where information enters, who touches it, what gets retyped and what goes wrong. That usually turns up more than the obvious Xero step, such as a project folder created by hand, a welcome email that is sometimes forgotten, or a stock reservation that depends on someone remembering.

Typical builds connect Pipedrive to Xero or QuickBooks for invoicing, to your website forms, to a quoting or pricing tool, and to job, booking or stock systems. Information flows back too, so a salesperson can see invoices, payments and order status on the deal without leaving Pipedrive.

## Pipedrive's plans and what they mean for integrations

Pipedrive's knowledge base explains that its plans were restructured in 2025: Essential became Lite, Advanced became Growth, Professional and Power merged into Premium, and Enterprise became Ultimate. The plan matters for integrations because it sets your API budget, as well as features such as automations, custom fields and permissions. We check your plan and seat count at the start so the design fits.

## Working within token-based rate limits

During 2025 Pipedrive moved from simple request counts to token-based rate limits. Each company account gets a daily token budget calculated from its plan and number of seats, and every API call spends tokens, with heavier calls such as searches costing more. The budget is shared by every integration on the account, so one badly written sync can starve the rest. Run out and requests return 429 errors until the budget resets. A separate burst limit applies to each user over a rolling two-second window.

Pipedrive's guide to optimising API usage says its API v2 endpoints cost up to half as many tokens as the original endpoints, so we build on v2 wherever an endpoint exists. We also:

- Use webhooks to learn about changes instead of polling for them.
- Fetch lists with cursor pagination and only the fields we need.
- Queue writes and pace them, backing off when the burst limit is reached.
- Cache reference data such as users, pipelines and stages.
- Track token spend per integration, so you can see which one is using the budget.

## Details that trip up integrations

Pipedrive identifies custom fields by long hash keys rather than their labels, and options in dropdown fields by numeric IDs. Integrations that look fields up by name break the first time someone renames one. We map fields explicitly, store the keys in configuration, and alert if a mapped field disappears.

Authentication depends on who the integration is for. A private integration for your company can use an API token belonging to a dedicated integration user. Anything installed by several Pipedrive accounts, or that needs per-user permissions, uses OAuth 2.0 through a Pipedrive Marketplace app with scoped access. Tokens are stored encrypted and never in client-side code.

Deletions and merges need thought too. When two people records are merged in Pipedrive, the losing record disappears, and an integration that still holds its ID will fail or recreate it. We listen for merge and delete events and update our own mappings, so linked invoices and jobs follow the surviving record.

Every message is logged with its result. Failures retry automatically, and anything that keeps failing raises an alert with the deal and reason, so problems are fixed in minutes rather than found at month end. We are happy to replace fragile no-code chains where they have become hard to trust; see Zapier vs custom integration for when each makes sense.

## Getting started

Tell us what happens before and after a deal is won, and which systems are involved. We will check your plan, API budget and existing automations, then give a fixed-price quote for a defined scope. See also CRM integration and webhook development, or get in touch.

## What we deliver

- An integration design: entities, fields, direction and triggers
- Two-way sync using Pipedrive API v2 and webhooks
- Won-deal automation into Xero, QuickBooks or a job system
- Website and form lead capture with source tracking
- Product and price sync from your price list or ERP
- Token-aware queues, retries, alerts and an audit log
- Documentation and a handover session

Technologies: Pipedrive API v2, Webhooks, OAuth 2.0, Xero API, Node.js, Laravel, Redis

## FAQs

### What are Pipedrive's current plans?

Pipedrive restructured its plans in 2025 into Lite, Growth, Premium and Ultimate, replacing Essential, Advanced, Professional, Power and Enterprise. The plan affects your API token budget and features, so dijitul checks it before designing an integration.

### Why does our Pipedrive integration return 429 errors?

Your account has run out of its daily API token budget, or a user has hit the two-second burst limit. The budget is shared by all integrations. dijitul fixes this with webhooks instead of polling, API v2 endpoints, caching and paced queues.

### Should integrations use Pipedrive API v1 or v2?

Use v2 wherever an endpoint exists. Pipedrive says v2 endpoints cost up to half as many rate-limit tokens as the originals, and they are where new development happens. dijitul builds on v2 and only falls back to v1 where no equivalent exists yet.

### Can you connect Pipedrive to Xero?

Yes. dijitul builds integrations so won deals create Xero invoices with the right contact and line items, and invoice and payment status show back on the Pipedrive deal, using webhooks and the Xero API with OAuth 2.0.

### Can you replace our Zapier automations?

Yes, where they have become fragile or expensive. dijitul rebuilds the important flows as owned code with logging, retries and alerts, and leaves simple low-risk automations where they are if they work well.

### How is a Pipedrive integration priced?

dijitul gives a fixed-price quote after a free chat and a short scoping stage covering systems, fields, volumes and triggers. You own the code and documentation at the end, with no ongoing licence to us.

## Pricing and contact

Every project gets a fixed-price quote after a free initial chat and a short scoping stage. You own the code and the data. Book a free chat: https://dijituldevelopments.co.uk/contact/ · 01623 650333 · info@dijitul.uk