The automation can fire a request and cannot read the answer, which decides the whole build.
A Reverse Contact API key, a Pipedrive plan with automations, and somewhere outside Pipedrive to receive the webhook
Contacts, Companies, Deals, one way, in.
Pipedrive is the clearest case in this directory of a CRM whose automation builder looks like it can do the job and cannot quite. The webhook action exists, it is well documented and it fires on conditions you define, but the response goes nowhere, so an enrichment is always a round trip: webhook out, a worker in the middle, API call back in. Once you accept that, the build is small and the limits are generous. The mistake is designing for a one-step automation that was never possible.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Trigger | One way, out | An automation on person or organisation created, firing the webhook action to your endpoint. |
| The enrichment | One way, out | Your worker, a Zap or a Make scenario POSTs to /v2/enrich/persons with the email. 2 credits on a match, free on a check. |
| Write-back | One way, in | A PATCH to the Pipedrive API sets the custom fields. 10 tokens a record from the daily budget. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and the worker decides which Pipedrive fields may be written. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
Nothing here is a field mapping, because the enrichment does not happen in Pipedrive. What travels out is a body you compose, what comes back arrives through the API from outside, and the useful detail is what each half costs and what each half is allowed to do.
| In Pipedrive | In Reverse Contact | What to know about the match |
|---|---|---|
| The automation trigger | Nothing yet | A person or organisation created or updated, with whatever conditions you set. Pipedrive notes that automated webhooks can be triggered by all users regardless of their visibility permissions or admin status, which is worth knowing before a condition relies on ownership. |
| The webhook action: Webhook, Method, Body | POST to your worker | The three mandatory fields, plus a path appended to the webhook's base domain. Methods are POST, PUT or DELETE; there is no GET. The body is built with a key-value builder that offers the record's fields from a dropdown, or raw JSON for full control. |
| The response to that webhook | Discarded | This is the whole reason the pair has the shape it does. The documented action has a webhook, a method, a body and a path, and no output, so whatever Reverse Contact answers cannot reach a later step. |
| Your worker, holding the email | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A miss returns null with a confidence score and costs nothing, because every 4xx and 5xx is free. |
| Your worker, holding a domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Run it on the organisation rather than once per person attached to it. |
| The write back in | PATCH a person or organisation, 10 tokens | Through the Pipedrive API with your own credential. Updating one entity costs 10 tokens and reading one costs 2, so the round trip is about 12 against a daily budget of 30,000 times the plan multiplier times seats. |
| A search, if you reach for one | 40 tokens, and 10 requests per 2 seconds | The most expensive endpoint on the budget and the only one with its own burst limit, which is identical on every plan and every authentication type. This is the call that turns a backfill into a queue. |
| Anything outbound to Reverse Contact | Only what your worker sends | Reverse Contact stores nothing back. The direction runs one way, and there is nothing in the product to write to. |
Pipedrive meters the API in tokens rather than calls, weighted by how heavy each endpoint is, and the budget is shared across every user and integration on the account. The arithmetic below is what decides whether a backfill is an evening or a fortnight.
| The call | What it costs |
|---|---|
| The daily budget itself | 30,000 base tokens times the plan multiplier times seats, plus any top-ups. Lite multiplies by 1, Growth by 2, Premium by 5, Ultimate by 7 |
| Reading one person or organisation | 2 tokens |
| Reading a list of them | 20 tokens, so a filtered list beats a loop of single reads |
| Updating one record with the enriched fields | 10 tokens |
| One full enrichment round trip | About 12 tokens, read plus update. The Reverse Contact call itself costs no tokens at all, because it is not a Pipedrive request |
| A search | 40 tokens, and capped at 10 requests every 2 seconds on every plan and every auth type |
| When the budget runs out | 429 until the reset, which is midnight in the server timezone and may not be your midnight |
A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, seven the call rows and four documented exclusions, each one's note, and the seven vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The Reverse Contact half of this build costs no Pipedrive tokens at all, which is easy to miss and changes where to optimise: the expensive part is reading and writing your own records, not enriching them. Pulling a filtered list at 20 tokens instead of a hundred single reads at 2 each is the first saving, and it is entirely on Pipedrive's side of the line.
Three of these four columns move with the plan and the middle one does not. That column is the finding rather than a formatting accident: no Pipedrive plan at any price lets an automation read what its webhook returned, so the thing that decides this build is not a tier at all. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Pipedrive plan | An automation with a webhook action | Reading what that webhook returned | Enriching from outside, through the API | Burst headroom for a backfill, per token |
|---|---|---|---|---|
| Lite, $14 a seat | No | No | Yes | No |
| Growth, $39 a seat | Yes | No | Yes | Workable |
| Premium, $59 a seat | Yes | No | Yes | Yes |
| Ultimate, $79 a seat | Yes | No | Yes | Yes |
Counted off that grid, of sixteen pairings: nine give you yes, one gives you workable, six give you no. So upgrading buys you a trigger and some burst headroom, and never buys you the thing the build actually needs. That is a different kind of gate from the one monday has, where every plan can be made to work and the daily call ceiling decides how many records a day you get, and a different kind again from HubSpot, where one separate hub decides everything.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
A whiteboard, not Pipedrive
The webhook action sends a body to a path and the documented fields are the webhook, the method and the body. Nothing hands the response to a later step, so the shape is always webhook out, worker in the middle, API call back in. Designing for a one-step automation is the mistake this page exists to prevent, and it is only discoverable after you have built the first half.
Zapier, Make, n8n or your own host
The native Zapier app can be the worker with no code and bills nothing when a lookup misses. An n8n instance keeps records on infrastructure you control and handles the live endpoints. Your own service is the cheapest at volume. This is the decision that determines who maintains the pair.
Pipedrive: Settings, Data fields
Custom fields, prefixed, separate from the ones a rep fills in. The write comes back through the API from outside the CRM, which means nothing in Pipedrive is standing between a bad mapping and a field somebody maintains by hand.
Pipedrive: Settings, Webhooks, + Webhooks, Automation webhook
This action is global-admin only, and Pipedrive states that existing webhooks cannot be re-used for automations, so it has to be a new one of this specific type. If no automation webhook exists yet, the webhook action will not even appear in the automation builder.
Pipedrive: the webhook, endpoint URL
Pipedrive requires the endpoint URL to conclude with a slash, an ampersand, a question mark or an equals sign, to stop malformed URLs being assembled from a base domain and a path. It is the most specific and least guessable requirement on this page.
Pipedrive: the webhook action, Method
POST, PUT or DELETE. There is no GET, which is a second reason the automation cannot fetch anything: it is built to send. Use POST and compose the body with the key-value builder or raw JSON, pulling the email straight off the record.
Your worker, against the Pipedrive API
The daily allowance is 30,000 base tokens times the plan multiplier times seats, and reading one record costs 2 tokens while updating one costs 10. So an enrichment round trip is about 12 tokens, and a search is 40 on its own, which is the call to avoid in a loop.
Your worker, reading the response headers
Pipedrive publishes x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset and x-daily-requests-left on responses. Ignoring a 429 and keeping the volume up earns a 403 from Cloudflare as an HTML error page, which is a much worse failure than the one you were retrying past.
The first two steps are the build and the other six are configuration. That is the opposite of the Attio version, where the whole thing is eight blocks in one workflow, and the difference is one documented sentence about whether a response can be read.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/pipedrive-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/pipedrive-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyPipedrive states that if webhooks are not pre-built you cannot add the webhook action, and that existing webhooks cannot be re-used for automations.
Create a new webhook of the Automation webhook type in Settings, as a global admin. A regular webhook already in the account will not appear, however well it works elsewhere.
WhyPipedrive requires the endpoint URL to conclude with a slash, an ampersand, a question mark or an equals sign, to prevent malformed URLs being assembled from a base domain and a path.
Add the trailing character. It is the least guessable requirement on this page and it produces no useful error message.
WhyThe webhook action sends and does not receive. The documented inputs are a webhook, a method, a body and a path, with nothing handed to a later step.
Put a worker in the middle: the native Zapier app, an n8n workflow or your own service. The automation is the trigger, and the enrichment and the write-back both happen outside the CRM.
WhyPipedrive states that if the webhook is not working any more or is missing authentication or permissions, the automation execution will fail. Webhook executions also count against the normal automation execution limits and pause when those are reached.
Check the execution history, which shows the final body and path. A worker returning a 500 fails the automation rather than being retried quietly, which is better behaviour than it feels like at the time.
WhyThat is a burst limit rather than the daily one. Burst limits are per token, per user, on a rolling 2-second window: 20 requests on Lite up to 120 on Ultimate for an API token, and 80 up to 480 for an OAuth app.
Pace the worker and read x-ratelimit-remaining and x-ratelimit-reset. A search is the one to watch: 10 requests every 2 seconds on every plan and every authentication type.
WhyPipedrive documents that continuing to send high volume after a 429 earns a 403, returned as a Cloudflare HTML error page rather than as an API response, and that only high-volume api_token traffic is blocked this way.
Stop retrying, fix the pacing, and parse the rate-limit headers instead of the clock. A worker that treats 429 as a reason to try harder turns a recoverable limit into a block.
WhyThe daily token budget is shared across every user and integration on the account, and the endpoints are weighted: a list read is 20 tokens and a search is 40 against 2 for a single read.
Read x-daily-requests-left, replace loops of single reads with filtered list calls, and check whether something else on the account is spending it. Admins are notified automatically as the budget nears its end.
WhyPipedrive documents that the token budget resets at midnight in the server timezone, which may not be aligned with the timezone you are in.
Schedule a backfill against the server reset rather than local midnight, and confirm the reset time by watching x-daily-requests-left rather than assuming it.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2023 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
Right now, when a lead comes in through our website form, it lands in pipedrive with just a name, email, and company size. Our sales reps waste a ton of time digging through LinkedIn to find the lead's actual job title, tech stack, and location before they make the first call. I want to automate this enrichment step the second a deal is created.
r/pipedrive·June 2026·2 points
The clearest statement of the job this pair does, from a Pipedrive user rather than a vendor. The phrase worth noticing is the second it is created, because that is the part Pipedrive can do: an automation can fire on creation and send a request, and the answer has to come back in through the API.
We track job changes adn intent signals in a separate sheet (pipedrive's data gets stale fast). For enrichment we ended up plugging Prospeo into our workflow. their verification catches the bad emails before they hit the CRM. Competitive intel still lives in Notion though, haven't found a good way to get that into pipedrive cleanly
r/pipedrive·May 2026·1 points
A different provider and the same architecture: enrichment in a workflow outside the CRM, with the check happening before anything is written. The parenthesis is the honest reason the whole pair exists, and the last clause is a reminder that what cannot be modelled as a field stays outside whatever you build.
You are right that CRMs like Pipedrive often fall short with enriched data and competitive intel, which means a lot of people end up juggling spreadsheets or plugging gaps with manual research.
r/pipedrive·May 2026·1 points
The rest of that comment is a product pitch, and the first sentence is a fair summary of where the threads land. Spreadsheets and manual research are what the round trip on this page replaces, and the thing that makes the round trip necessary rather than optional is one documented absence: the webhook action cannot read its own response.
Honestly, our main focus isn't on reselling licenses. The real value and where we spend most of our time is in customizing the CRM, tailoring automations, integrations, and workflows so it fits how each team actually operates.
r/CRM·November 2025·3 points
From somebody implementing Pipedrive commercially, answering an agency considering a move away from Salesforce. Automations and integrations being where the effort goes is consistent with the plan grid above: the automation builder is capable and the gap it leaves is specific, so most of the work on this pair is in the worker rather than in the CRM.
1. Get an account enrichment tool (like zoominfo) 2. Tie CRM master data to erp master data. Pick a source of truth and sync them 3. Budget 20k/year and find an architect to guide you 4. Tackle one process end to end per quarter. Pull in executive sponsor, end users, etc. diagram the workflow, reach agreement, and then implement that one fix
r/salesforce·February 2024·26 points
From a Salesforce thread, and it transfers because the first step is a category rather than a product. The budget figure is this person's own and is worth holding against a route whose cost is a worker you already run plus credits, which is the argument for doing the smallest version of step four first.
Nobody discusses this pair by name, so the search was for the job: enriching an inbound Pipedrive lead before a rep calls it. One thread is somebody asking for exactly this build, and the answers in it are products rather than methods. What the threads agree on is that the enrichment and the stale-data tracking both end up outside Pipedrive, which is the conclusion this page reaches from the documentation.
Two of the five are Pipedrive users describing this build before reading anything about it, which is the strongest evidence that the round trip is the normal answer rather than a workaround. What nobody in the threads says is why, and the grid above is the reason: no plan at any price lets the automation read what its own webhook returned, so the worker is not a preference.
The reason this pair is worth a page rather than a row is that Pipedrive gets you most of the way and then stops at exactly the wrong place. An automation can watch for a new person, evaluate conditions and send a request with a body you compose from the record. What it cannot do is take the answer and put it in a field, and no feature list anywhere says so. Teams find out after they have built the first half.
Compare it with the CRM that does the same job in one step. Attio hands the response back to the next workflow block, status and body both, with a Parse JSON step to pull out the fields. Same category of product, same kind of builder, opposite answer, and the difference costs an afternoon and a hosted worker. Neither vendor frames it as a difference because neither thinks of the response as a feature.
The good news is that the round trip is cheap and the budget is roomy. The native app on Zapier can be the worker without anyone writing code, and the enrichment there bills nothing when there is no match. If the stack is already running scheduled sweeps rather than triggers, a table does the same job in bulk, which is the pattern the Zoho build also falls back to when the in-CRM route is gated behind an edition.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Pipedrive, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Not as an app, and the shape of the one you build is decided by a single documented absence. A Pipedrive automation can fire a webhook carrying a body you compose from the record, and nothing in that action hands the response to a later step, so an enrichment is always a round trip: webhook out, a worker in the middle, API call back in.
It can send the request and it cannot use what comes back. Pipedrive documents a webhook action inside automations that posts a body to a path you define, with execution history you can inspect, and nothing in that documentation hands the response to a later step. So the automation is the trigger, not the enrichment: something outside Pipedrive receives the call, enriches, and writes the fields back through the API.
Pipedrive's support article says automations and webhooks in automations are available on Advanced and higher plans, while plain webhooks are on every plan. The pricing page now sells Lite, Growth, Premium and Ultimate, and automations appear in the feature list from Growth. The article has not caught up with the renaming, so confirm against your own account rather than against either page.
A global admin, and only a global admin. The webhook has to be created first in Settings as an Automation webhook, existing webhooks cannot be reused for this, and the action will not appear in the builder until one exists. That is three facts that each look like a bug when you meet them in the wrong order.
Unlikely, and it is worth knowing the shape anyway. Pipedrive meters a daily token budget of 30,000 base tokens times a plan multiplier times seats, where the multiplier runs from 1 on Lite to 7 on Ultimate. Updating one record costs 10 tokens and reading one costs 2, so a ten-seat Growth account has 600,000 tokens a day against perhaps a few thousand for an enrichment loop.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.