A thousand API calls a day until Pro, which is the whole design constraint.
A Reverse Contact API key, a monday plan with automations, and a receiver for the webhook
Contacts, Companies, Custom objects, one way, in.
monday CRM is the least opinionated CRM in this directory and the most constrained to enrich, for one reason that has nothing to do with features: 1,000 API calls a day until you reach Pro. Everything else works. Webhooks are solid, the GraphQL API is pleasant, columns take whatever you write into them. But a read and a write per record against a four-figure daily ceiling means this is a trickle rather than a sweep until the plan changes, and the right build is one that enriches on creation and never backfills.
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 | A webhook on create_item or a column change, verified with monday's challenge handshake. |
| The enrichment | One way, out | Your receiver, a Zap or a Make scenario calls /v2/enrich/persons with the email from the item. 2 credits. |
| Write-back | One way, in | A GraphQL change_multiple_column_values mutation sets the columns. One call against the daily count. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and the receiver decides which columns 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.
The enrichment never happens inside monday, because there is no HTTP step in its automations. What the board contributes is a trigger and a set of columns, and everything interesting about the mapping is that columns are identified by id rather than by name.
| In monday | In Reverse Contact | What to know about the match |
|---|---|---|
| A board event | Nothing yet | Created through the create_webhook mutation with a board, a url, an event and a config, so an event can be scoped to one column and one value. Custom automations are metered separately from API calls, starting at 250 a month on Standard and rising to 25,000 on Pro. |
| The webhook payload | Your receiver, over POST | Carries a JWT in the Authorization header when the webhook was created with an integration app token, verifiable against the app Signing Secret. Requests retry once a minute for thirty minutes, so a receiver that is briefly down loses nothing. |
| Your worker, holding an email | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. Costs nothing on a miss, because every 4xx and 5xx is free, and nothing from monday's budget either because it is not a monday call. |
| Your worker, holding a domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Worth running once per account board item rather than once per person linked to it, which also halves the monday calls. |
| A live refresh, if you want one | POST /v2/fetch/persons/live, 2 credits | Genuinely available on this route, unlike most of the CRM pages here, because the worker is outside monday and can poll. Polling is free and off the rate-limit clock. |
| change_multiple_column_values | Every enriched column, in one call | The mutation that matters for the budget. One call carrying six values costs one of your daily allowance; six calls cost six, and on 1,000 a day that decides your throughput. |
| A column id | Not a column name | Mutations address columns by id. Renaming a column in the interface is harmless and duplicating a board mints new ids, so a write can land nowhere without anything reporting a failure. |
| Anything outbound to Reverse Contact | Only what your worker sends | This is a read layer. Nothing travels back, and there is nothing in the product to write to. |
monday meters four different things at once and each has its own error. The daily call limit is the one that decides whether this pair is viable, and it is also the only one of the four that a small integration will ever reach.
| The budget | What it is and what happens at the end of it |
|---|---|
| Daily call limit | 1,000 on Free, Basic and Standard, 10,000 on Pro, 25,000 on Enterprise, resetting at midnight UTC. Returns DAILY_LIMIT_EXCEEDED |
| Minute limit | 1,000 queries a minute on other tiers, 2,500 on Pro, 5,000 on Enterprise. Returns a minute limit error with a Retry-After header |
| Concurrency limit | 40 simultaneous requests on other tiers, 100 on Pro, 250 on Enterprise. Returns a concurrency error |
| Complexity limit | 5,000,000 points for a single query, and a per-minute budget on a sliding window: 5,000,000 each for reads and writes on an app token, 10,000,000 combined on a personal token, 1,000,000 on trial, NGO and free accounts. Returns ComplexityException |
| A request that hit any rate limit | Counts 0.1 of a call against the daily limit rather than a full one, and returns retry_in_seconds |
| A request that simply failed | Counts in full. monday states that all requests count toward the limits, even those that fail or return an error |
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, six the budget 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.
Writing every enriched value in one change_multiple_column_values call rather than one call per column is the single highest-leverage decision on this page, because it multiplies your daily throughput by however many fields you are filling. It is also the sort of thing that never shows up in testing, where one record at a time always works.
monday meters the API by the day and the ceiling is low enough to be the design rather than a footnote: 1,000 calls on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, resetting at midnight UTC. The grid assumes two calls per record, one to read it and one to write every enriched column back in a single mutation, which is the cheapest this build can honestly be. Pick one on each side and the grid marks the answer.
Pick one on each side.
| What you are trying to run | Free, Basic or Standard | Pro | Enterprise |
|---|---|---|---|
| Enrich 100 new items a day | Comfortable | Comfortable | Comfortable |
| Enrich 500 a day | At the limit | Comfortable | Comfortable |
| Enrich 2,000 a day | Over the daily budget | Comfortable | Comfortable |
| Backfill 20,000 items in one pass | Over the daily budget | Over the daily budget | At the limit |
| Run it beside another integration | Over the daily budget | At the limit | Comfortable |
Counted off that grid, of fifteen pairings: eight give you comfortable, three give you at the limit, four give you over the daily budget. The second row is the one worth sitting with: five hundred records a day is the whole Standard budget, and it is shared. That makes monday the one CRM in this set where the honest recommendation is to enrich on creation and never backfill, unless the plan changes. Pipedrive gates the capability and monday gates the volume, and the volume gate is the easier one to miss, because nothing fails until the day somebody imports a list.
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 calculator, not monday
The daily API call limit is 1,000 on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, resetting at midnight UTC and shared with every other integration on the account. An enrichment round trip is at least one read and one write, so anything below Pro is a few hundred records a day and never a backfill.
monday: the board
A board is columns somebody named rather than a contact object with agreed semantics. Mutations address columns by id, so renaming one in the interface breaks nothing and duplicating a board for another team produces new ids that break everything silently. Write the ids down somewhere outside monday.
Your own host, or n8n
monday posts a randomly generated token in a challenge field to prove you control the URL, and expects the identical value returned in a challenge field of your JSON response. A receiver that does not implement that cannot be registered at all, so this is step one of the build rather than a detail. The URL is also capped at 255 characters.
monday: a monday app with an integration feature
Two things follow from doing it this way. Requests then carry a JWT in the Authorization header that you can verify against the app Signing Secret, and end users cannot disable the webhook, which monday documents as deliberate so a curious user cannot toggle an integration off.
monday: the create_webhook mutation
The mutation takes a board, a url, an event and a config, so a status-column event can be scoped to one column and one value. Every event that fires is a round trip against a four-figure daily budget, so the filter is the budget.
Your worker, or an n8n workflow
monday has no HTTP step in its automations, so the call to Reverse Contact always happens outside. That also means the live endpoints are available here in a way they are not on most of these pages, because a worker can poll and a CRM automation cannot.
Your worker, against the monday API
One mutation carrying every enriched column is one call against the daily limit; six mutations are six. On a 1,000-call budget that distinction is the difference between 400 records a day and 70.
Your worker, on every response
monday returns RateLimit-Policy and RateLimit headers in the IETF format, reporting minuteRate, concurrency and complexityMinute with a remaining value and a reset. Every rate-limit error also carries retry_in_seconds. Honouring those is cheaper than retrying, because all requests count toward the limits even when they fail.
Step one is unusual in this set because it can honestly end the project: on Standard there is no volume at which this pair is a sweep rather than a trickle. That is a different kind of constraint from the one Pipedrive has, where every plan can be made to work and the automation simply cannot read a response.
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/monday-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/monday-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.
WhyThe daily call limit is 1,000 on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, shared across every personal token, private app and public app on the account.
Collapse the write into one change_multiple_column_values call, narrow the webhook event, and find out what else on the account is spending the budget. An increase can be requested through the API analytics dashboard if the account consistently exceeds it.
Whymonday posts a randomly generated token in a challenge field to verify you control the URL, and expects the identical value back in a challenge field of your JSON response body. The URL is also capped at 255 characters.
Implement the challenge before anything else. It is four lines in most frameworks, and no webhook exists until it passes.
WhyA webhook created with a personal token can be toggled by end users. monday documents that webhooks created with an integration app token cannot, specifically so an app is not disrupted by a curious user.
Create a monday app with an integration feature, generate an OAuth token for it, and call create_webhook with that. The same change is what puts a verifiable JWT in the Authorization header.
WhyMutations address columns by id rather than by name, so a wrong id is a well-formed mutation against a column that is not the one you meant.
Keep the column ids written down outside monday, and re-check them after any board is duplicated. Duplicating a board for a new team mints new ids and breaks nothing visibly until the first write.
WhyComplexity is a separate budget from the call count: 5,000,000 points for a single query, and a per-minute budget on a sliding window that is 1,000,000 on trial, NGO and free accounts.
Add the complexity field to the query to read the cost before and after, request only the fields you need, reduce nesting, and use the page and limit arguments. monday recommends exactly those three.
WhyAll requests count toward the limits even when they fail, and every rate-limit error carries a retry_in_seconds field that a retry loop usually ignores.
Read the RateLimit header, which reports minuteRate, concurrency and complexityMinute with a remaining value and a reset in seconds, and throttle before the remaining value reaches zero.
WhyReverse Contact returns null rather than a best guess when it is not confident, and a worker that maps the response straight into a mutation writes the absence.
Branch in the worker on the field being present and omit it from the mutation otherwise. A column left alone costs nothing; a column overwritten with nothing costs a rep's trust in the board.
Why/v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026.
Change both paths in the worker. This is the one route where that fix is in ordinary version-controlled code rather than inside a CRM automation nobody can diff.
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 2022 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.
enrichment only matters if a field changes what a rep does. Pick 2 3 fields that drive a decision, like employee count for routing and industry for which case study gets sent, and wire them into lead assignment and sequence choice. Hide the rest from the default contact view. If no field changes routing, priority, or messaging, you're paying for decoration
r/CRMSoftware·October 2026·1 points
The single most useful piece of advice in these threads and it happens to be the cheapest change on this pair. Two or three fields written in one mutation is one call against a daily budget of 1,000 on anything below Pro; twelve fields written individually is twelve, and the grid above turns that difference into a throughput ceiling.
We started using data enrichment at my company a couple of months ago and as it is, I'm starting to wonder if we're missing the whole point. [...] Most of our reps still open the contact, skim the information and carry on with the same sales process they were using before. It feels like we've gone from having 5 fields nobody looks at to having 20 fields nobody looks at.
r/CRMSoftware·October 2026·3 points
From a B2B software company with a sales team of eight, two months in. The last sentence is the failure mode no vendor page describes and it is not about data quality at all: the enrichment worked and nothing downstream of it changed. Deciding what a field will trigger is the prerequisite, not the follow-up.
Enrichment only pays off when it triggers something. 20 fields a rep has to read is just more homework. [...] Give the rep one line instead of 20 fields. Something like "Strong fit: 200 employees, logistics, VP Ops. Similar to Acme deal." That's what actually changes how they open the call. The data was never the problem. Nobody had time to turn it into a decision.
r/CRMSoftware·October 2026·1 points
Composing one summary line in the worker and writing it to a single column is also the cheapest possible shape on this pair, because the write is one call whatever the line says. The last two sentences are the honest verdict on most enrichment projects, including ones built exactly as documented.
I'd start by asking your reps which details they normally look up before contacting someone. Those are the fields worth putting front and centre. [...] If a field doesn't change who gets contacted, what you say, or how much research a rep has to do, it's fair to question whether you need it.
r/CRMSoftware·October 2026·1 points
A three-part test that can be applied in an afternoon and before any of this is built. It is also the right way to pick which Reverse Contact call to make: a current title and a current employer answer the first two, and the full history and skills answer none of them on most teams.
The ideal solution would involve using automation tools like Make.com or zapier which can help automate the process of extracting LinkedIn lead data and pushing it directly into Monday.com with minimal manual effort.
r/mondaydotcom·January 2025·2 points
Answering a small team asking for a one-click route from a profile into monday CRM. The answer is a middle layer because there is no HTTP step in a monday automation, which is the documented fact behind the whole shape of this page, and the rest of that comment goes on to recommend scraping tools, which is a different legal question from calling a provider's API.
Nobody discusses this pair by name, so the search was for the job: filling monday board columns from outside and getting any value from it. The best thread is somebody asking whether enrichment was worth buying at all, because their reps ignored the twenty new fields, and the answers to it are the most useful editorial guidance in the whole harvest. On a pair with a four-figure daily call ceiling, picking fewer fields is also the cheapest thing you can do.
Four of the five are from one thread and that is deliberate, because it is the only thread in the harvest where practitioners argue about whether enrichment is worth having rather than which vendor to buy. On this pair that argument has a second edge, since every field you decide not to fill is a call you do not spend against a daily ceiling, and the grid above shows how little room there is below Pro.
Most integration pages for monday talk about the complexity budget, because it is the striking number and it is in the first paragraph of monday's own rate-limit documentation. For enrichment it is almost never the binding constraint. Five million complexity points a minute is enormous; a thousand API calls a day is not, and the second figure is the one that decides whether a build is a trigger or a sweep. Reading the limits in the order monday presents them leads to exactly the wrong design.
The absence that shapes this page is an in-product HTTP step. monday automations fire webhooks and run recipes; they do not call an arbitrary API and hand you the response the way an Attio workflow does. So the middle layer is not optional here, and the cheapest honest version of it is the native app on Zapier, which bills nothing when a lookup misses, or a worker you host if the volume makes a task meter silly.
What monday gives back is the schema freedom, and it is real. Columns are whatever you make them, so the enriched fields sit next to the ones a rep owns without a mapping argument, and a board for a motion that is not contacts-and-deals works as well as one that is. That is the same trade Pipedrive declines to make and the same one Attio makes deliberately, which is a useful way to choose between the three.
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 monday, 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 monday has no HTTP step in its automations, so the enrichment always happens outside it. The shape is a board event firing a webhook, a receiver that enriches and writes back through the API, and a daily call ceiling that decides how many records a day that covers. Below Pro that ceiling is 1,000 calls, shared with every other integration on the account.
The daily call count, not the complexity budget everyone reads about first. monday allows 1,000 API calls a day on Basic and Standard, 10,000 on Pro and 25,000 on Ultimate, resetting at midnight UTC. An enrichment loop that reads a row and writes it back is two calls, so a Standard account can enrich roughly 500 records a day before the API stops answering.
A webhook fires on item creation or a column change, something outside monday calls Reverse Contact, and a GraphQL mutation writes the values back into columns. monday has no in-product HTTP block of the kind Attio has, so the middle step is always somewhere else: the native Zapier app, a Make scenario, or your own worker.
Custom automations are metered separately, 250 a month on Standard and 25,000 on Pro, and they are what fires the webhook. The API calls that write the enriched values back come out of the daily call count. Two different budgets, and a design can run out of either.
monday retries once a minute for 30 minutes. It also verifies the endpoint when you create the webhook by posting a challenge token that your URL has to echo back in a challenge field, so a receiver that does not implement that will never be registered in the first place.
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.