The Business plan buys the webhook. It does not buy the throughput.
- Moves: Tasks, Contacts, Companies
- Needs: ClickUp Business or above for task webhooks, a ClickUp API token, and a Reverse Contact API key
Four integrations, and three of them are gated. What is unusual about ClickUp is that the gate sits on a different side each time: once on HubSpot, twice on ClickUp itself, and the one that costs nothing is the one most teams use every day.
Two-way automation between the deal and the work.
ClickUp is free to start, and that is exactly what makes its integration pricing hard to read. The Slack pair costs nothing on either side, so the first integration anybody tries confirms the impression that this is a free tool. The next three do not: the HubSpot handover wants HubSpot Professional for the automated direction, and both ClickUp-side builds want Business or above.
The second thing to know is that ClickUp gates twice, on two different floors. Business turns task webhooks on and leaves the API at the same 100 requests a minute the free plan gets, with 1,000 a minute arriving only at Business Plus. So a team can buy the plan that makes an integration possible and still be running on the throughput of a free account.
The failure shape here is the Automations allowance rather than the API. Actions are metered per month, 100 on Free and 1,000 on Unlimited and Core, and when the allowance runs out the automations stop until the month turns over. That is a silent stop rather than an error, which is why the Reverse Contact build spends longer on the meter than on the webhook, and why the rest of the collaboration layer is worth reading beside it.
ClickUp sits in the collaboration layer, with 2 other tools in this directory. Counted across the whole directory it reaches 4 of the other 22 tools, and the integration matrix shows that row against every other.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for freeThe Business plan buys the webhook. It does not buy the throughput.
The rare pair where each vendor built the half that runs inside the other.
Two integrations, both on Business Plus, and only the names sync both ways.
Free on every plan, and only the person who set it up can extend it.
4 things that decide whether a ClickUp integration will work for you, in the order they usually bite.
Three of the four integrations here need a paid plan somewhere, and the side that pays changes each time. The HubSpot pair needs HubSpot Professional for the automated direction and nothing extra from ClickUp. The Salesforce pair and the Reverse Contact build both need ClickUp Business or above and nothing extra from the other vendor. Work out which side the gate is on before you price the upgrade, because upgrading the wrong one buys nothing at all.
ClickUp lists task webhooks, Automations integrations and Chat webhooks as unavailable on Free Forever, Unlimited and Core, and available from Business. The API rate limit is a separate staircase: 100 requests a minute on Free, Unlimited and Business alike, 1,000 at Business Plus and 10,000 at Enterprise. Buying Business therefore makes the integration possible without making it fast. If the build is a bulk sweep rather than a per-task trigger, the plan that matters is Business Plus.
Actions are metered per month rather than per minute: 100 on Free, 1,000 on Unlimited and Core, 10,000 on Business, and 25,000 or 100,000 on Business Plus depending on how old the plan is. When the allowance is spent the automations stop until the month turns over, and nothing throws an error a rep would see. Count what a busy month will spend before you design the automation, because the ceiling is the thing that fails rather than the connection.
ClickUp treats URL headers as sensitive and says that once they are saved you cannot view the values to edit them. That is good security and poor operations, because a rotated API key means rebuilding the automation rather than editing it. Usage history is one day on Business and below, so a failure over a weekend can age out before anybody looks at it. Write the header values down somewhere you control before you save them.
Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.
The Business plan buys the webhook. It does not buy the throughput.
One way, in → 02The rare pair where each vendor built the half that runs inside the other.
Two-way sync → 03Two integrations, both on Business Plus, and only the names sync both ways.
Two-way sync → 04Free on every plan, and only the person who set it up can extend it.
Two-way sync →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.
Free trial, no card required, and 500 credits to start.
The questions that come up before anyone opens a setup guide.
Three of the four in this directory. The Salesforce sync needs ClickUp Business Plus or Enterprise and is documented as beta behind a contact form. The Reverse Contact build needs ClickUp Business, because that is where task webhooks start. The HubSpot pair needs HubSpot Professional rather than anything from ClickUp, and the Slack integration needs nothing beyond both accounts.
Yes, documented at developer.clickup.com, authenticated with a personal API token or OAuth. The limit is per token and depends on the plan of the Workspace hosting the token: 100 requests a minute on Free, Unlimited and Business, 1,000 on Business Plus and 10,000 on Enterprise. That means a Business workspace has the same API throughput as a free one, which surprises most teams who upgraded for the webhook.
The most common cause is the monthly Action allowance rather than anything broken. Actions are capped per month and automations stop when the cap is reached, with no error a rep would notice. The second most common is a rotated credential: ClickUp will not show you a saved header value, so an automation built on an old key has to be rebuilt rather than edited.
It can send the request and it cannot read the reply. A Call webhook automation fires at exactly the right moment, which is the hard half of most builds, and ClickUp documents no way to take the response and write it back onto the task. Anything that needs the answer has to come back through the API from outside, which is why the Reverse Contact route on this hub runs through a middle layer.
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.