INTEGRATIONSPIPEDRIVEConnect Pipedrive to your other systems
Salespeople want to track deals in Pipedrive, not retype customer details from the accounting system. With an integration, a won deal automatically becomes a customer, an invoice or a project. And the salesperson can see in Pipedrive whether it's been paid.
ISO 9001 & 27001
- People and organisations goes back and forth with Your other systems
- Deals and stages goes back and forth with Your other systems
- Leads goes back and forth with Your other systems
- Products on deals goes back and forth with Your other systems
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
This is the data organisations most often let flow between systems. Which of it matters to you depends on where work is getting stuck today.
People and organisations
Contacts and the companies they work for. In the accounting system that's a debtor, in your online store a customer. The integration has to be able to match those three to each other.
Deals and stages
A deal moves through the stages of your pipeline. The moment a deal is marked won is the starting point for most integrations: create the customer, prepare the invoice, open the project.
Leads
In Pipedrive, leads sit separately from deals, in the Leads Inbox. Bring enquiries from your website in as leads, so a salesperson assesses them first before they become a deal.
Products on deals
With products on a deal, you know what was sold and at what price. If your items come from an ERP or online store, keep the product list in Pipedrive in line with it.
Invoices and payment status back
Invoices are created in the accounting system. Send the invoice number and payment status back to the deal or organisation, and a salesperson doesn't have to ask whether a customer has paid.
Activities, notes and email
Calls, meetings, tasks and notes. Through email and calendar sync, emails and meetings from your own inbox land on the right person and deal.
For each combination: which data moves back and forth, what the standard integration does and what to watch out for.
- Connect Exact Online to PipedriveConnect Exact Online to Pipedrive: won deals become invoices in Exact, payment status comes back to the deal, and what to watch with people and products.
- Connect Moneybird to PipedriveConnect Moneybird to Pipedrive: a won deal becomes a draft invoice, you see payment status on the customer in your CRM, and duplicate contacts are prevented.
- Connect Pipedrive to Google WorkspaceConnect Pipedrive to Google Workspace: what the built-in sync with Gmail, Calendar, Contacts and Drive does, what it doesn't, and when to go custom.
Not always. If an existing integration for Pipedrive does exactly what you need, we'll tell you.
The Pipedrive Marketplace has apps for accounting, telephony, forms and more. Pipedrive itself syncs with Google and Microsoft email, calendar and contacts, and has a Gmail add-on for creating people, deals and activities from your inbox.
For a small team with a simple process, that's often enough. A won deal becomes a customer in the accounting system, an invoice goes out and the salesperson can move on.
It starts to chafe when you want more. For example, when one deal leads to several invoices, when you work with instalments or when custom fields need to come along. Check whether an app also carries your custom fields, because that's not a given.
- Your accounting system or ERP has no app in the Pipedrive Marketplace.
- One deal leads to several invoices, instalments or a subscription.
- You use custom fields that also need to land in another system.
- A won deal also needs to start a project or schedule, not just an invoice.
- Several Pipedrive accounts or branches need to feed into one set of books.
REST API in two versions
Pipedrive has a REST API with v1 and v2 endpoints. The v2 endpoints, including those for deals, people, organisations, activities and products, are faster and cost fewer tokens. If a v1 endpoint is deprecated, you get at least a year to migrate.
API token or OAuth
For your own integration, you can use an API token. That token belongs to one user and gives access to everything that user can see. Apps offered through the Pipedrive Marketplace use OAuth 2.0.
Webhooks
Webhooks v2 report the creation, change and deletion of deals, people, organisations, activities, leads and products, among others. You can have 40 webhooks per user. If a delivery fails, Pipedrive retries after 3, 30 and 150 seconds.
A daily token budget
Every request costs tokens from a daily budget: 30,000 times a factor for your plan times the number of users. Fetching a list costs more than fetching a single record, and searching is relatively expensive. There's also a per-user limit per two seconds.
Test environment
For development, you request a developer sandbox account. It works like a normal Pipedrive account with sample data. It stays active if you create an app within 45 days.
An integration moves data. In between, AI can read, sort and prepare a suggestion. Where it matters, a person decides.
What Pipedrive can do itself
Pipedrive has AI for writing emails and, in beta, for summarising email threads with an assessment of buying intent and action points. These features are in the higher plans and work on emails that come in through email sync. The Sales Assistant answers questions about your data in Pipedrive.
Preparing a lead
An enquiry comes in through your website. AI checks whether the person or organisation already exists, summarises the request and prepares a draft reply on the lead. The salesperson decides whether it becomes a deal and what the reply says.
When the built-in AI falls short
Pipedrive's AI only sees what's in Pipedrive. If a summary also needs to say that a customer has two unpaid invoices or that a delivery is delayed, that data first has to reach Pipedrive through an integration.
An employee's API token
An API token belongs to one user. If the token is regenerated, the integration stops. If that employee leaves, the integration depends on an account you actually want to close. Use a dedicated user for integrations, or an app with OAuth.
Custom fields with unreadable keys
In the API, a custom field isn't called Industry; it gets a random 40-character key. That key doesn't change if you rename the field. But if someone recreates the field, there's a new key. Record the keys and test after every change to your fields.
Webhooks that silently disappear
If Pipedrive can't deliver a webhook for three days, it's deleted. Your integration won't notice on its own. So check regularly that your webhooks still exist, and fetch missed changes through the API.
One app using up the budget
An app that fetches a lot of lists quickly uses up the daily budget. Other integrations then get error 429 until the budget is topped up again at midnight, and that's midnight in the server's time zone.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: People and organisations, Deals and stages, Leads, Products on deals, Invoices and payment status back, Activities, notes and email.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: REST API in two versions, API token or OAuth, Webhooks, A daily token budget, Test environment.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.
No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Does Pipedrive have an API?
Yes, Pipedrive has a REST API for deals, people, organisations, leads, activities and products, among others. You use an API token or OAuth 2.0. With webhooks, Pipedrive lets another system know that something has been created, changed or deleted.
How many API requests can I make in Pipedrive?
Pipedrive uses a daily token budget: 30,000 times a factor for your plan times the number of users. Every request costs tokens, depending on the type of request. Once the budget runs out, you get error 429 until it's topped up again.
Can I connect Pipedrive to my accounting software?
Yes. For some packages there's an app in the Pipedrive Marketplace; for others you build an integration using both systems' APIs. The usual pattern: a won deal creates a customer and an invoice, and the payment status comes back to the deal.
What happens to the integration when an employee leaves?
If the integration runs on that employee's API token, everything depends on that one account. If the token changes, the integration stops. So connect with a dedicated service user or an OAuth app, and agree who becomes owner of the deals and activities the integration creates.
Can I test a Pipedrive integration without my real data?
Yes, with a developer sandbox account. It's a separate Pipedrive account with sample data, intended for building and testing apps and integrations. It stays active if you create an app within 45 days or publish an app within six months.
Can YTC connect Pipedrive to a system without a standard integration?
Yes. We can connect Pipedrive to any system, even when there's no Marketplace app for it. It then starts with two agreements: which system leads on which data, and which event in Pipedrive sets what in motion.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.
- Pipedrive: Rate limiting
- Pipedrive: Authentication
- Pipedrive: Guide for Webhooks v2
- Pipedrive: API v2
- Pipedrive: Custom fields
- Pipedrive: Developer sandbox account
- Pipedrive Knowledge Base: Leads Inbox
- Pipedrive Knowledge Base: Syncing with your email, calendar or contacts provider
- Pipedrive Knowledge Base: Pipedrive Gmail add-on
- Pipedrive Knowledge Base: Pipedrive AI
- Pipedrive Knowledge Base: AI email summarization