---
title: "Pipedrive Integration in 2 to 6 Weeks | JustAutomate"
description: "Pipedrive tracks the pipeline but never moves a dead deal. We wire it to invoicing, email and delivery in 2 to 6 weeks. Start with the workshop."
url: "https://justautomate.ai/en/integrations/pipedrive/"
lang: en
---

CRM and sales

# Pipedrive integration with no dead deals in the forecast

Pipedrive keeps the pipeline and the rep's activity in order. It does not know whether the client paid, what was promised after the signature or whether anyone answered their ticket, because those live in tools bolted on beside the CRM. We wire Pipedrive to them through the API and webhooks, set inactivity thresholds per stage, and say plainly when you have outgrown it.

 Book a free consultation [See how the workshop works](https://justautomate.ai/en/services/process-workshop/)

- 14 daysfrom the workshop to the first automation running on your own Pipedrive account, on real deals
- 2 to 6 weeksfrom the workshop to a wired-up Pipedrive, depending on how many tools you have bolted on beside the CRM
- 5 to 10 secondshow long an AI agent takes to answer a question about deals at risk, without opening Pipedrive

The problem

## Why does the Pipedrive pipeline look better than it is?

A deal has been sitting at "proposal sent" for three weeks. Nobody scheduled an activity on it, the client never replied, and the amount still counts towards this month's forecast. Pipedrive does exactly what it promises: it marks the deal red as neglected. That is where it stops. The rep sees the colour, closes the tab and goes back to a deal where something is actually happening.

The second thing follows from the very reason people like Pipedrive. It is cheap and it runs within a week, so it gets into the company fast and stays with sales. Tools grow up around it that Pipedrive will never replace: email in ActiveCampaign or Mailchimp, tickets in Zendesk, invoices in Xero or sevDesk, orders in BaseLinker. Each one holds a different slice of the same customer, and Pipedrive knows only the sales slice. Once the contract is signed, the handover to delivery happens by email, because there is nowhere in the CRM to put it.

The technical layer is not the obstacle here. Pipedrive exposes a public REST API and webhooks on changes to deals, persons and activities, all described in the [Pipedrive developer documentation](https://developers.pipedrive.com/). The moment a deal stops moving can be caught a second after it happens. What is missing is a decision about what should happen then, and one place where that decision is written down.

- A deal with no activity scheduled sits in the forecast until the end of the quarter
- After a win, somebody retypes the VAT number and the contract value into an invoice by hand
- The same company sits in Pipedrive and in the email tool under two different names
- What was agreed with the client stays in the rep's inbox and never reaches delivery
- The pipeline forecast and the invoice list show two different numbers, and nobody knows which one is real

Why now

## What changed, so that wiring up Pipedrive takes weeks and not a quarter?

Pipedrive hands over its data through the API and pushes webhooks on events, so a stage change, a new deal and a missing activity are visible straight away, with nothing polling the system every fifteen minutes. Endpoints, authentication and rate limits we cover separately under [API integration](https://justautomate.ai/en/services/api-integration/). This page is about what that means for the pipeline.

The second change is about where the rule lives. Automations inside Pipedrive are good for anything that does not leave the CRM: a stage change creates an activity with a due date, sets a field, sends a notification. Once a rule has to ask the invoicing system about a payment status or Zendesk about an open ticket, the logic moves to [n8n](https://justautomate.ai/en/services/n8n-automation/), Make or a custom integration, and Pipedrive becomes the place the result is written to. That line is sharper in Pipedrive than in the larger CRMs, because the data model is closed: you cannot create a custom object for a contract, a device or a subscription.

The third change is the AI agent. A rule does what it was told, but it will not answer the question "which deals booked for this month are at risk". BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, reading the close date and the date of the last activity, with no CRM login and no report request.

What changes

## What does the team get once Pipedrive is wired up?

- ### A dead deal reports itself
No activity for an agreed number of days creates a task for the owner, and a second breach goes to their manager. The red colour in the pipeline turns into a due date somebody has to close.
An inactivity threshold set per pipeline stage, not one number for all of them
- ### A won deal issues the invoice
Moving to the won stage creates a proforma in your invoicing system with the details from the record: VAT number, company name, contract value. The document number and the payment status come back onto the deal as fields, not as a note.
Invoice details read from the Pipedrive record, with no VAT number retyped by hand
- ### The handover to delivery stops being an email
A won deal opens a task in the delivery team's tool with what you promised: scope, deadline, the person running it. Delivery no longer starts with somebody asking what we actually sold.
A task in ClickUp, Asana or Jira with fields carried over from the deal
- ### Follow-up runs itself, and the rep gets a task
A stage change fires a reminder sequence in ActiveCampaign or Mailchimp. Silence after an agreed number of days does not end in one more email, it ends in an activity for a human in Pipedrive.
No reply books a call in the rep's calendar, not a fifth email in the sequence
- ### A forecast calculated outside the CRM
Deals, persons, organisations and activities land in a warehouse where we calculate win rate, stage velocity and the forecast. The report does not vanish when somebody rearranges a pipeline or renames the stages.
New records into BigQuery every 15 minutes, a full dump once a day
- ### A pipeline question in a plain sentence
"Which deals are at risk", "how many proposals have waited longer than two weeks", "who has the most deals with no activity". The AI agent answers from Pipedrive data, in plain English.
An answer in 5 to 10 seconds, from the close date and the last activity

What about you

## What if Pipedrive is enough for us?

Sometimes it is, and we say so on the first call. Pipedrive is built around one thing: the pipeline and the rep's activity. If you sell one product, run one pipeline and have three reps who plan the next step on every deal, you need nothing from us beyond a decent set of stages and inactivity thresholds. You outgrow it when customer data splits across four tools, when you need to attach objects to a customer that the Pipedrive model does not have, or when somebody ends up calculating the forecast in a spreadsheet anyway.

If you are looking for something next to this, there are separate pages: [CRM automation](https://justautomate.ai/en/services/crm-automation/) when the problem is the way people work in the CRM, [CRM implementation](https://justautomate.ai/en/services/crm-implementation/) when there is no CRM yet, and [HubSpot integration](https://justautomate.ai/en/integrations/hubspot/) when you are comparing the two systems. Contact data is processed under [Regulation 2016/679](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679), so the retention period for leads that never entered the pipeline is something we set together with you.

- We picked Pipedrive because it is cheap and simple. We do not want that ruined.
And we will not ruin it, because the simplicity of the pipeline is the point here, not a limitation. We do not push things into Pipedrive that it was never built to hold. We wire it to the tools you already run and leave in the CRM what the rep actually comes there for. If the workshop shows that tidying up stages and inactivity thresholds is enough, we say so and the engagement ends at the workshop.
- Our reps do not schedule activities, so automation will not fix this.
It will not, and we are not going to promise it. Automation does not create discipline. It does something else: it turns the lack of it into a visible fact. A deal with no activity past the threshold for its stage becomes a task with a due date, and a second breach escalates to the manager. If the team ignores tasks as well, the problem sits with management rather than with the tool, and we will tell you that.
- We are thinking about moving off Pipedrive to something bigger.
First we check whether it is the tool that is tight or the process, because a migration carries the mess across together with the data. The workshop shows which gaps are genuinely Pipedrive gaps: no custom objects, a thin marketing and support layer, reports that depend on your plan. If the list is short, adding one tool alongside costs less than paying for the move and a few weeks of the team unlearning what they know.
- We have had custom fields for three years and nobody knows what they mean any more.
We read them through the API and give you numbers: which fields are genuinely filled in, how many sit empty, which were created as free text instead of a picklist. A custom field in Pipedrive has a generated key that every integration refers to, so renaming the label breaks nothing, and tidies nothing either. Empty fields we archive, text fields become picklists wherever a rule has to decide on them.

Pipedrive

Deals, leads, persons, organisations, activities, products, custom fields, webhooks, automations

Email and customer support

ActiveCampaign, Mailchimp, GetResponse, Zendesk, Intercom

Invoicing and orders

Xero, sevDesk, Xentral, Comarch Optima, BaseLinker, Shopify, WooCommerce, PrestaShop

Team tools and calendar

Google Workspace, Microsoft 365, Google Calendar, Slack, ClickUp, Asana, Jira, Notion

Data and warehouse

BigQuery, Google Sheets, Google Analytics, SQL databases

Automation layer

Make, n8n, Zapier, custom API integrations

## What Pipedrive does on its own, and what has to be added to it

Seven needs that companies running Pipedrive come to us with. The second column matters more than the third here, because half of these cases need no code from us at all.

| What you need                                    | Does Pipedrive do it                      | What we add                                                       |
| ------------------------------------------------ | ----------------------------------------- | ----------------------------------------------------------------- |
| A pipeline, activities and reminders for the rep | yes, this is its core                     | nothing, beyond setting stages and inactivity thresholds          |
| A task and a notification after a stage change   | yes, in Pipedrive automations             | nothing, as long as the rule does not query another system        |
| Email campaigns with segmentation and consent    | only narrowly, and in a paid add-on       | ActiveCampaign, Mailchimp or GetResponse wired in through the API |
| Support tickets after the sale                   | no, there is no ticket in the data model  | Zendesk or Intercom, with the history back on the person record   |
| Invoice, payment status, due date                | no, this is not an accounting system      | Xero, sevDesk, Xentral or Comarch Optima                          |
| Forecast and a history of stage changes          | partly, report scope depends on your plan | export to BigQuery, forecast calculated outside the CRM           |
| A custom object: contract, device, subscription  | no, Pipedrive has no custom objects       | custom fields, a separate database or a warehouse alongside       |

The rows are a starting point out of the workshop, not a price list. In most companies the first build covers two items from this table, and the order follows from which one takes the most manual work off people.

How we do it

## Five steps from a red deal to a pipeline that closes

Every step ends with something you can judge before you decide on the next one.

1. ### Workshop
We walk the pipeline stage by stage and ask the same thing at each one: what has to happen for a deal to enter here, who plans the next activity, and after how many days of silence you call it dead. We also write down the tools sitting beside the CRM, including the spreadsheet the forecast is born in.
2. ### Pipedrive account review
We read pipelines, stages, custom fields, existing automations and permissions through the API, and we count facts: what gets filled in, how many duplicates there are, how many deals have sat with no activity for over a month. You get the report before anything changes on production.
3. ### Thresholds, rules and where the logic sits
We set an inactivity threshold for each stage and decide what happens once it is crossed. We split the rules: what stays in Pipedrive automations because you will change it yourselves, and what goes to n8n or Make because it has to ask an invoice, a warehouse or a ticket first.
4. ### Pilot on real deals
Rules run alongside the current process first, on deals from recent weeks, including the ugly cases: a deal with no organisation, a company with no VAT number, a win with no products entered. We check how many events go through and which ones fail.
5. ### Production and a check at 30 and 90 days
We switch over with error monitoring and train the person who is going to maintain this without us. At 30 days we look at how many deals crossed a threshold and how many of those somebody actually moved. At 90 days we check whether the pipeline forecast matches the invoices that went out.

Before and after

## How the sales director's week changes

### Before

- At the pipeline review they ask the rep what is happening with a deal from last month
- The Pipedrive forecast drifts away from what actually got invoiced
- After every win somebody retypes the company details into the invoicing system
- What was agreed with the client is known only to the rep who wrote it in an email

### After

- A deal with no activity reports itself before the threshold for its stage runs out
- The forecast is calculated in the warehouse, from the same data the invoices come from
- A won deal creates a proforma from the record details, with no human in the loop
- The handover to delivery is a task with a scope and a deadline, not an email

The first automation runs 14 days after the workshop. At 30 days we measure how many deals crossed the inactivity threshold and how many of those somebody moved. At 90 days we check the forecast against the invoices.

For the person signing this off

## What the person who owns sales gets out of it

A Pipedrive licence is a cheap line item, which is why nobody questions it. The bill turns up elsewhere: in the four tools bolted on beside it, in the hours spent retyping data after a win, and in a forecast you cannot defend because half the deals in it have not moved for three weeks. Once it is wired up, the forecast becomes a number calculated from the close date and the last activity, rather than the sum of the team's optimism.

The second thing takes a bigger decision off your desk. Moving to another CRM is weeks of work plus a team unlearning its habits, and with Pipedrive that question comes back every year. We start with a [process workshop](https://justautomate.ai/en/services/process-workshop/), so you answer it with a document listing the real gaps, not with a vendor deck.

- A forecast based on the close date and the last activity, not on what the rep says
- The decision about changing CRM taken after the workshop, on a list of concrete gaps
- Rules run alongside the current process, so the live pipeline is not the test bed
- Thresholds and task wording changed by one person on your side, with no ticket to us

What it costs

## The workshop has a fixed price, the wiring is quoted after it

The process workshop costs **EUR 3,500 net per week** and runs from one to seven weeks depending on scope. With a single pipeline one week is usually enough, because the scope is narrow: what enters a stage, who plans the activity and what happens after a win. The wiring is quoted after the workshop, once we know how many tools beside the CRM are in play and what state the custom fields are in.

You pay for the Pipedrive licence directly to Pipedrive, and the same goes for its paid add-ons, email campaigns among them. Running scenarios in Make or n8n is billed by the vendor, or costs nothing at all when the scenario sits on your own infrastructure. Where an AI agent is in scope, the model provider charges EUR 0.005 to 0.07 per query. No commission on top from us.

- ### Process workshop
EUR 3,500 net
per week, usually one week for a single pipeline
A self-contained piece of work. It ends with a map of the pipeline with thresholds and a straight answer on whether Pipedrive is enough for you.

  - Account review: pipelines, stages, custom fields, automations and plan
  - An inactivity threshold per stage and the rule for what happens once it is crossed
  - A list of the tools beside the CRM with a call on what stays in Pipedrive
  - An answer on whether you stay on Pipedrive or outgrow it, with the list of gaps
 Start with the workshop
- Most popular
### Workshop and Pipedrive wiring
Quoted after the workshop
scope follows from the number of tools beside the CRM and the state of the data
The option most companies choose. Pipedrive wired up 2 to 6 weeks after the workshop, tested alongside the current process.

  - Everything in the workshop
  - Inactivity rules, escalations and tasks after a stage change
  - Integrations through the API and webhooks: invoices, orders, email, tickets, calendar
  - Handover from sales to delivery as a task with fields from the deal
  - Pilot alongside the current process, switchover with error monitoring, training
 Talk about a rollout
- ### Pipedrive and an AI agent
Quoted after the workshop
for teams that ask about the state of the pipeline several times a day
Everything in the wiring plus BOND, which answers questions about the pipeline in a plain sentence.

  - Everything in the Pipedrive wiring
  - An AI agent reading the pipeline: deals at risk, quiet proposals, load per rep
  - Permissions set separately for reading and for writing
  - Access for reps and for their manager, an answer in 5 to 10 seconds
 Ask about the agent

The workshop ends with a document that stands on its own without us: a map of the pipeline with inactivity thresholds, a list of the tools beside the CRM and a call on what stays in Pipedrive. If the account review shows that the automations you already have are enough, we say so and the engagement ends at the workshop. If it turns out your process has outgrown Pipedrive, we will say that too, instead of forcing the wiring.

## Frequently asked questions

What exactly do you connect to Pipedrive?

Five things most often: the invoicing system (Xero, sevDesk, Xentral, Comarch Optima), the tool for email and sequences (ActiveCampaign, Mailchimp, GetResponse), support tickets in Zendesk or Intercom, the delivery team's tool (ClickUp, Asana, Jira) and a BigQuery warehouse for the forecast. Calendar and Slack on top of that, so activities and notifications do not require opening the CRM. The order is set at the workshop.

Is Pipedrive enough for us, or is it better to move to another CRM?

Pipedrive is enough when the sales process fits into one pipeline and the team plans the next activity on every deal. You outgrow it when you need custom objects, a stronger marketing and customer support layer, or reports that do not depend on your plan. The workshop ends with a list of the real gaps, so you take the decision on a document rather than on a vendor deck.

When are Pipedrive automations enough, and when do you need n8n or Make?

Rule of thumb: if the rule starts and ends inside Pipedrive, it stays in Pipedrive automations, because you will change it there without us. An activity after a stage change, a notification, setting a field, all of that is an automation. If the rule has to query a system next door, a payment status or an open ticket for instance, it goes to an orchestrator, where you can see which step it failed on and run it again.

How do you spot deals that nobody is working on?

By two things at once: no activity scheduled, and the number of days spent at the current stage. We set the threshold separately for each stage, because silence after a proposal means something different from silence after a first call. The first breach is a task for the owner with a due date, the second is an escalation to the manager, with the contact history attached.

Can a won deal issue the invoice by itself?

Yes, and it is one of the first connections people ask about. Moving to the won stage creates a proforma in the invoicing system from the details on the record, and the document number and payment status come back onto the deal as fields you can filter on. We keep an approval step where the amounts need signing off, because an invoice sent automatically to the wrong contact costs more than the two minutes it saved.

What about custom fields that nobody understands any more?

We read them through the API and show you how many times each one was genuinely filled in over the last year. Empty fields we archive, and the text ones that a rule is supposed to decide on become picklists. The key an integration uses to refer to a field is generated by Pipedrive, so renaming the label breaks no connections, and that is exactly why the tidying has to happen on the values rather than on the names.

How long does a Pipedrive integration take?

One week of workshop and 2 to 6 weeks of work, depending on how many tools are in scope. The first automation usually runs 14 days after the workshop, so the team sees an effect before the project ends, and we start with the one that takes the most manual work off people. The longest part is rarely the wiring itself, it is agreeing the thresholds and who picks up an escalation.

Can the AI agent change data in Pipedrive?

It can, but permissions are set separately for reading and for writing, and we almost always start with reading only. Writing goes on after the pilot and on a narrow list of operations: a note, an activity, one field. Every operation the agent runs is logged, so you can see who changed what, and it can be reversed.

## Let us check how many deals in your pipeline are already dead

The free consultation takes 30 minutes. You tell us how many pipelines you run, how many reps work in them and what you have bolted on beside Pipedrive: invoicing, email, support tickets. We show you which connection takes the most manual work off people, and whether Pipedrive is still the right place for that process in your case. You do not have to share access to the account at this stage.

We run at most two rollouts at a time, so that someone is actually sitting on each of them.

[Book a free consultation](https://justautomate.ai/en/contact/)

**PS.** If somebody at your company opened the pipeline this week and saw a deal where nothing had happened for three weeks, that is exactly this problem. Pipedrive showed it in red and stopped there. A rule set once turns that colour into a task with a due date, and a second breach into an escalation, so the forecast stops being a wish list.

## Related

- [CRM automation](https://justautomate.ai/en/services/crm-automation/)
- [CRM implementation and integration](https://justautomate.ai/en/services/crm-implementation/)
- [HubSpot integration](https://justautomate.ai/en/integrations/hubspot/)
- [API integration](https://justautomate.ai/en/services/api-integration/)
- [n8n automation](https://justautomate.ai/en/services/n8n-automation/)
- [BOND, business AI agent](https://justautomate.ai/en/services/bond-business-ai-agent/)

---

**JustAutomate** · contact: contact@justautomate.ai · form: https://justautomate.ai/en/contact/