The Business plan buys the webhook. It does not buy the throughput.
ClickUp Business or above for task webhooks, a ClickUp API token, and a Reverse Contact API key
Tasks, Contacts, Companies, one way, in.
ClickUp can start this and cannot finish it. A Call webhook automation sends a task out at exactly the right moment, which is the hard half of most builds, and then there is no documented way to read the reply back into a custom field, so the answer returns through the API as a separate write. Two plan gates decide whether it is worth doing, and they do not line up: Business turns the webhook on and leaves you on the slowest rate limit ClickUp publishes.
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 |
|---|---|---|
| The trigger | One way, out | A Call webhook automation on a task change, sending the payload to your endpoint with headers you set. |
| The lookup | One way, out | POST /v2/enrich/persons from your middle layer. 2 credits on a match, nothing on an error. |
| The write-back | One way, in | The ClickUp API sets the custom fields on the task, against 100 requests a minute on most plans. |
| The status change | One way, in | Move the task when the lookup resolves, so an unenriched task is visible rather than merely unchanged. |
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.
A person in ClickUp is a task, so the field map is a task map. The useful part is not which value goes where, which is obvious, but which leg of the journey each value travels on, because the trip out and the trip back use different machinery.
| In ClickUp | In Reverse Contact | What to know about the match |
|---|---|---|
| An email on the task, in a custom field | The Call webhook payload | ClickUp sends information about the task that triggered the automation. Dynamic variables such as the task ID can go in the URL, which is how your endpoint knows what to write back to. |
| That email | POST /v2/enrich/persons, 2 credits | Identity, the current role and the company behind it on one schema. A miss returns null with a confidence score and costs nothing. |
| A company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain. Run it against the account task rather than once per person attached to it. |
| A profile URL already on the task | POST /v2/fetch/persons, 1 credit | Half the price, and unmetered from the $249 plan rather than the $699 one. Worth checking for before paying for a reverse lookup. |
| currentPosition.title | A text or dropdown custom field | A dropdown if you intend to filter or group on it, because a free-text title is unfilterable in practice once a few hundred variants arrive. |
| currentPosition.companyName | A comparison, then a field | Compare it against the account the task is filed under before writing it. A disagreement means the person has moved, which is the most useful thing this response carries. |
| metadata.updatedAt | A date custom field | Store it and the next sweep can skip everything refreshed recently instead of paying to resolve it again. |
| The resolved values | The ClickUp API, as a separate call | Not a return value from the automation. The webhook is outbound only, so the write is a new request against 100 a minute on most plans. |
ClickUp describes its webhooks as sending information proactively rather than requesting it, and that single sentence is why this build has four legs instead of two. Each row below is one leg and where it has to run, which is the thing to get straight before anybody opens a settings screen.
| The leg | Where it runs, and why there |
|---|---|
| Noticing that a task needs enriching | ClickUp, and this is what it is good at. A Call webhook automation fires on the exact task change you name, which is the part that is awkward everywhere else |
| Sending the identifier out | ClickUp, from Business upwards. Headers and URL parameters are yours to set, so the credential travels properly |
| Doing the lookup | Your middle layer. There is no step inside ClickUp that calls Reverse Contact, and no app on either side that supplies one |
| Getting the answer back onto the task | The ClickUp API, as a fresh request. This is the leg people assume ClickUp provides and it does not: the automation has no documented way to read the response |
| Starting an automation from outside | ClickUp's Webhook received trigger, which exists but is a second automation rather than a reply to the first |
| Knowing it worked | A status change you write yourself. Automations history is one day on Business, so the task has to carry its own evidence |
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 leg rows and four documented exclusions, each one's note, and the eight 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.
Read the second table as a budget rather than a diagram, because three of the six legs are yours to build and host. The one ClickUp genuinely contributes is the first, and it is worth more than it looks: knowing precisely when a record became worth enriching is the thing most of these integrations get wrong.
This pair is gated twice and the gates are on different floors. One is the Automations allowance that decides whether ClickUp can call out at all, the other is the API rate limit that decides how fast the answer can come back, and the plan that fixes the first leaves the second exactly where it was. Every figure is from ClickUp's own documentation. Pick one on each side and the grid marks the answer.
Pick one on each side.
| ClickUp plan | The Call webhook action exists | Actions enough for a 1,000-row pass | API fast enough for a backfill | Conditions to gate the trigger |
|---|---|---|---|---|
| Free Forever | No | No | No | No |
| Unlimited and Core | No | Just | No | No |
| Business | Yes | Yes | No | Yes |
| Business Plus | Yes | Yes | Yes | Yes |
| Enterprise | Yes | Yes | Yes | Yes |
Counted off that grid, of twenty pairings: eleven give you yes, one gives you just, eight give you no. The third row is the sentence this grid exists for: on Business you get the webhook, the Actions and the conditions, and you are still on the same 100 requests a minute as somebody on the free plan. So the upgrade that makes this build possible is not the upgrade that makes it fast, and a backfill of any size on Business is a scheduling exercise rather than a job you start and watch.
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.
ClickUp: Settings > Plan
Task webhooks are unavailable on Free Forever and on Unlimited and Core. There is no configuration, no workaround inside the product and no partial version: either the Call webhook action is there or this build has to happen before the task is created instead.
ClickUp: ClickApps, as an admin or owner
Automations have to be switched on at Workspace level by an admin or an owner before anybody can create one. Guests cannot create Automations at all, and limited members can only do so where they already have edit permissions on the location.
ClickUp: Custom Fields on the List
Use fields the enrichment owns outright rather than ones a person edits between calls. Remember that a custom field has to be added to each List or Space you want to combine it in, so decide the scope now rather than after the first dashboard comes back half empty.
ClickUp: Manage Automations > Webhooks
Custom headers take an Authorization value, which is where the credential belongs, because a URL parameter ends up in a log. Note before you save that ClickUp will not show you the header value again, so record which key went in somewhere you trust.
ClickUp: Test webhook
The Test webhook button sends an example payload, which is enough to confirm the endpoint, the headers and the shape. Point the first one at a request bin rather than at the enrichment, so that a mistake costs nothing and tells you more.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a backfill spends 2 credits only where the answer is genuinely missing. Every 4xx and 5xx costs nothing either, which means a miss on a thin list is free on the Reverse Contact side even though it still spends a ClickUp Action.
ClickUp: the public API, with a personal or OAuth token
The write is a separate call rather than a return value, and on Business the ceiling is 100 requests a minute per token. Read X-RateLimit-Remaining rather than assuming the number, because the limit depends on the plan of the Workspace hosting the token rather than on your own.
ClickUp: a status, not just a field
A task whose enrichment silently failed looks exactly like one that was never triggered, because an empty custom field is the default state. A status change makes the difference visible to a human, which is the only monitoring this build gets on a plan with one day of Automations history.
ClickUp: Automations usage
Actions are the meter that will actually bite, because exceeding them pauses every Automation in the Workspace rather than just this one. A hundred-task pass tells you the real cost per enriched record in Actions, and that number against the monthly allowance is the answer to whether a backfill is possible at all.
The first step is the only one that cannot be worked around, and it is a billing decision rather than a technical one. Everything after it is ordinary, with the single oddity that the answer comes back by a different road than it left by, which is the thing to hold in mind when something stops working.
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/clickup-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clickup-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.
WhyTask webhooks are listed as unavailable on Free Forever and on Unlimited and Core.
Check the plan rather than the permissions. There is no setting that adds it, so the options are Business or enriching before the task is created, which a Zap or a Make scenario on the inbound form does without any ClickUp gate.
WhyThe monthly Action allowance was exceeded, and ClickUp pauses the Workspace's Automations for the rest of the month rather than throttling the one that ran hot.
Route the 90% email that goes to owners and admins somewhere people read, and count Actions per enriched record before a backfill. Actions reset on the first of the month, PST.
WhyThe automation sent the payload and nothing wrote the answer back. The Call webhook action has no documented way to read the HTTP response.
Add the write as a separate ClickUp API call keyed on the task ID, which is why the task ID belongs in the webhook URL as a dynamic variable. There is no version of this where the automation returns the value.
WhyThe API allows 100 requests a minute per token on Free, Unlimited and Business, and the limit follows the plan of the Workspace hosting the token.
Honour X-RateLimit-Reset, which is a Unix timestamp, and read X-RateLimit-Limit rather than hard-coding a number that changes with somebody else's plan.
WhyClickUp states that URL headers are sensitive and that once saved the values cannot be viewed to edit them.
Keep the record outside ClickUp, and rotate by replacing the header rather than inspecting it. Treat the saved header as write-only from the moment you click save.
WhyA custom field has to be added to the other Spaces and Lists before data from them can be combined in a single card.
Decide the field scope when you create it, not when the first report is due. This is a modelling decision in ClickUp rather than a reporting one.
WhyAutomations usage history is one day on Free, Unlimited, Core and Business, and 30 days only from Business Plus.
Make the task carry its own evidence: a status for enriched, a status for tried and unresolved, and a date field for when. The record outlives the log on every plan this build runs on.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS.
Watch quotas.workspace.credits.left on every response and check GET /v2/usage on a schedule, because it keeps answering when the lookups do not. Note that the automation still spends a ClickUp Action either way.
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 28 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.
You can use it as a database, but you have to know that above all every database item is a task. inside a list of tasks you can set the custom fields, and the relationships but at the end of the day all you have as a huge list of tasks tat belong to different lists, in folders, under separate spaces.
r/clickup·September 2023·1 points
The structural fact the whole page rests on, put more plainly than the documentation puts it. A contact is a task with custom fields on it, which is why the field map above is a task map and why the enriched values have to be modelled as fields on a List rather than as properties of a person. It also explains the scoping problem lower down: fields belong to Lists, so a person who appears in two Lists is two tasks.
Some of the things that are easy to accomplish in other platforms are just impossible to do in ClickUp such as: [...] Automate and integrate Custom Fields with external data (unless it's through the API).
r/clickup·February 2023·1 points
Three years before this page was written, somebody listing what they found impossible in ClickUp named the exact limitation and the exact workaround, in a parenthesis. It corroborates the documentation rather than adding to it, which is the right use for a comment: ClickUp can send a task to a URL and cannot bring an answer back to a field, so the API is the return journey.
This is where ClickUp lacks most imho. While the options they offer look plentiful, in reality a lot of things can not actually be achieved with automations. They do add automations from time to time, but it's moving slowly.
r/clickup·December 2024·2 points
Written about automations between boards rather than about webhooks, and it generalises accurately. The list of available actions reads as though a round trip ought to be configurable, and the thing that is missing is not an action but a direction. Budget for a middle layer from the start and this stops being a disappointment.
When you make a custom field/column, ClickUp requires that you add it to other spaces/lists to be able to combine data in a single card on a dashboard. So while Monday lets you pull together any similar field into one chart (whether it makes sense or not), ClickUp only pulls that one field.
r/clickup·December 2024·1 points
This is the thing that makes an enrichment build in ClickUp look broken three weeks after it works. The writes succeed, the field is populated, and a dashboard covering two Lists shows half the data, because the field was only ever added to one of them. Decide the scope when the field is created, which is step three of the checklist above for exactly this reason.
Our agency hace unlimited plan for over two years now. We pay for Clickup Brian also. Use the free plan first and try to setup examples of what you need. The pay walls are annoying. Things like move a custom field location from one place to another is behind a pay wall.
r/clickup·December 2024·1 points
Good advice with one exception that matters here, and the misspellings are theirs. Modelling the Lists and fields on the free plan is sensible and cheap, and the one thing you cannot rehearse there is the integration itself, because the Call webhook action is not on that plan. So prototype the data model free and price the Business upgrade as the cost of the build rather than discovering it at the end.
Nobody discusses this pair by name, so the search was for the job: holding people and company records in ClickUp and getting external data onto them. Almost every thread came back from r/clickup itself, which is thinner material than the other pages here get and unusually consistent in what it says. The recurring complaint is the exact shape of this page: the automations look capable until you want one to fetch something.
This is the thinnest harvest of the seven Reverse Contact pairs and it is thin in a useful direction: nobody is comparing tools, everybody is already in ClickUp and working out what it will not do. Two of the five name the webhook limitation independently of the documentation, which is the corroboration this section exists for, and the fourth is the one that will cost you a week if you skip it.
The reason this page exists is that plenty of teams run their pipeline in ClickUp and have no CRM, so the task is the record. That works until something has to be looked up, because a task is a container for work rather than for facts about a person, and the moment you want a job title on it you are building an integration rather than configuring one.
What ClickUp genuinely gives you is the trigger. A Call webhook automation fires on exactly the task change you name, with headers you control, which is the part that is fiddly in a spreadsheet and absent in Slack. What it does not give you is the return journey, and that asymmetry is the whole design: one automation out, one API call back, and no way to express the round trip as a single step.
If the ClickUp plan is the obstacle rather than the shape, the cheaper move is to enrich before the task exists. A Zap or a Make scenario on the inbound form can call the Reverse Contact app and create the task already filled, which needs no ClickUp webhook and therefore no Business plan. That is a better build in most cases and this page would be dishonest not to say so.
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 ClickUp, 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.
No. Reverse Contact maintains apps on Clay, Zapier and Make and nothing inside ClickUp, and ClickUp lists no Reverse Contact app. The build is a Call webhook automation out, an enrichment in the middle, and a write back through the ClickUp API, which is three parts and about an afternoon once the plan allows it.
It can do the first half only. ClickUp describes webhooks as sending information proactively rather than requesting it, and the Call webhook action has no documented way to read the HTTP response back into a field. The answer has to arrive separately, either through the ClickUp API or through the Webhook received trigger, which is a second automation rather than a return value.
Business, because task webhooks are listed as unavailable on Free Forever and on Unlimited and Core. That is the gate worth pricing before anything else: without it there is no documented way to get an identifier out of ClickUp at the moment a task changes.
Not on Business. The rate limit is 100 requests a minute per token on Free, Unlimited and Business alike, rising to 1,000 on Business Plus and 10,000 on Enterprise. So the plan that unlocks the webhook leaves you at the slowest tier, and a 10,000-task backfill is an hour and a half of polite waiting.
ClickUp pauses your Workspace's Automations for the rest of the month. Actions reset on the first, PST, and owners and admins get emails at 90% and 100% of the allowance, which is the warning worth routing somewhere people read.
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.