---
name: hubspot-clickup-integration
description: Connect HubSpot and ClickUp: what syncs, which editions carry it, the setup order, and the failures to expect. Covers deals, contacts, companies, tasks. Use when the user wants to set up, audit or troubleshoot HubSpot and ClickUp together, or asks why data is not moving between them.
---

# HubSpot and ClickUp

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clickup-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** HubSpot workflows for the automated direction, so Professional or above

**What moves:** deals, contacts, companies, tasks, both ways.
**How it is built:** native, marketplace app, zapier, make or n8n. **Effort:** minutes.

## The short version

Best in class for the handover problem, and thin exactly where you would expect. ClickUp actions run inside HubSpot workflows and HubSpot actions run inside ClickUp automations, so a closed-won deal can spawn a delivery list and a status change in delivery can move the deal. Companies, contacts, deals, line items, products, tasks and tickets can all be created and linked. Custom fields are where teams fall back to Make.

## Which plans actually carry this

Rows: HubSpot tier. Columns: ClickUp plan. ClickUp lists the app as working on Free Forever, Unlimited, Business and Enterprise alike, so the three columns below are identical on purpose: every gate on this pair is on the HubSpot side.

| HubSpot tier | Free Forever | Unlimited or Business | Enterprise |
|---|---|---|---|
| Free or Starter | ClickUp Automations only | ClickUp Automations only | ClickUp Automations only |
| Professional | Plus HubSpot workflows | Plus HubSpot workflows | Plus HubSpot workflows |
| Enterprise | Plus HubSpot workflows | Plus HubSpot workflows | Plus HubSpot workflows |

- **ClickUp Automations only.** The ClickUp side still works: Automations can act in both tools and are where custom field mapping happens anyway. What you do not get is a deal stage creating the work automatically.
- **Plus HubSpot workflows.** Deal-based HubSpot workflows that create Spaces, Folders, Lists and tasks, which is the half people mean when they say the handover is automated.

Counted off that grid, of nine pairings: three give you ClickUp Automations only, six give you plus HubSpot workflows.

A grid with identical columns is the finding rather than a formatting accident: upgrading ClickUp buys you nothing here, and upgrading HubSpot buys you the whole automated direction.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Deal to task or list | One way, out | A HubSpot workflow creates ClickUp work with deal context attached. |
| Task status to deal | One way, in | A ClickUp automation updates the HubSpot record when delivery moves. |
| Contacts and companies | Two-way sync | Created and linked on either side, so the work item knows whose account it is. |
| Line items and products | One way, out | What was sold travels with the handover, which is the point of doing this at all. |
| Tickets | Two-way sync | Support work and delivery work in the same place as the revenue record. |

## Which field lands where

Field mapping on this pair is restricted in two ways at once, and both are documented by ClickUp rather than by HubSpot.

| In HubSpot | In ClickUp | What to know about the match |
|---|---|---|
| Deal | Task, List, Folder, Subfolder or Space | Deal-based triggers can create any of those five, including from a task template. |
| Deal name, type and amount | Task name and description | Carried as Deal tokens rather than as mapped fields, which is why they land as text rather than as structured values. |
| A HubSpot field | The equivalent ClickUp Custom Field | Only within ClickUp Automations, and only to a matching type: an email field maps to an Email custom field. |
| Task status | The deal or ticket record | Driven by a ClickUp Automation rather than by the HubSpot workflow, so delivery progress coming back is a separate build from work going out. |

**What does not cross:**

- Custom fields, in a HubSpot workflow. ClickUp states that custom field mapping is not supported there, so the HubSpot side can create work and cannot fill it in.
- A HubSpot field whose type has no ClickUp equivalent. Mapping is type to type with no coercion.
- The second automation in a chain. An object created by a HubSpot Automation does not trigger another one.

## Connect it, in this order

**Who has to do it:** A ClickUp Workspace owner or admin to authenticate, and a HubSpot admin to build the workflow.
**How long:** Ten minutes to connect. An hour per handover workflow you actually want.

### 1. Authenticate from the ClickUp side

*Where:* ClickUp: App Center, HubSpot, Manage

Click Add to HubSpot and pick the HubSpot account in the authorisation popup. ClickUp requires a Workspace owner or admin for this, so a team lead cannot do it alone.

### 2. Decide which direction you are automating before you build anything

*Where:* A whiteboard

There are two engines here and they are not equivalent. A HubSpot workflow can create ClickUp work from a deal trigger; a ClickUp Automation can act in either tool and is the only one that maps custom fields. Picking the wrong one means rebuilding rather than reconfiguring.

### 3. Build the deal-based workflow in HubSpot

*Where:* HubSpot: Workflows, Create workflow, Deal-based

Set up triggers with Filter type Deal, then add a ClickUp action. The first time you do this you will be asked to connect the app from inside the workflow editor.

### 4. Point the action at a place in the ClickUp hierarchy

*Where:* The ClickUp action panel

Choose the Workspace, then an existing or new Space, Folder or Subfolder and List. Creating new ones from the workflow is possible and is how a tidy hierarchy turns into hundreds of orphan Spaces, so prefer existing ones and name the pattern now.

### 5. Use Deal tokens to carry the context across

*Where:* The task name and description fields

Click Deal token next to a field to inject HubSpot data such as the deal name, type and amount. This is the only route for deal data into a task created by a HubSpot workflow, because custom field mapping is not supported there.

### 6. Map custom fields in ClickUp Automations instead, by matching type

*Where:* ClickUp: Automations

A HubSpot field can only map to the equivalent ClickUp Custom Field type, so an email field maps to an Email custom field and nothing else. Build the field-level work here rather than in HubSpot.

### 7. Publish, then check what your automations do to each other

*Where:* HubSpot: Review and publish, then Turn on

An object created by a HubSpot Automation will not trigger another HubSpot Automation. A chain that assumes it will looks correct in the editor and silently stops after the first link.

The two-engine split is the thing to take away: HubSpot workflows move work across, ClickUp Automations move fields, and a plan that uses only one of them will hit a wall it cannot configure past.

## How to check it worked

- Move a test deal to the stage that fires the workflow and confirm the task lands in the List you intended, not in a newly created one.
- Open the task and check the Deal tokens resolved to real values rather than to empty strings.
- Change a mapped custom field in HubSpot and confirm the ClickUp field updates. If it does not, the mapping is in the wrong engine.
- Deliberately chain two automations and watch the second one not fire. Knowing that is cheaper than discovering it in a live handover.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| The workflow created the task but every field is empty | Custom field mapping is not supported in HubSpot workflows. Only Deal tokens in the name and description carry anything across. | Put the values you need into the description as tokens, and build real field mapping as a ClickUp Automation instead. |
| A field will not map even inside an Automation | Mapping is type to type. A HubSpot email field maps only to a ClickUp Email custom field, and there is no conversion. | Create the matching custom field type in ClickUp first, then map. Renaming does not help, the type does. |
| The second automation in a chain never fires | An object created by a HubSpot Automation does not trigger another HubSpot Automation. | Collapse the chain into one automation, or trigger the second step from something a person does rather than from something an automation made. |
| Nobody can authenticate the integration | ClickUp requires a Workspace owner or admin to connect HubSpot. | Get the Workspace owner to do the App Center step. It takes a minute and cannot be delegated by permission alone. |
| ClickUp is full of Spaces nobody meant to create | The workflow action offers to create a Space, Folder or List as well as to pick one, and a trigger that fires on every deal will keep taking it. | Point actions at existing Lists, and decide the naming pattern before the workflow goes live rather than after a quarter of deals have run through it. |

## What breaks, from the vendors' own docs

- **Custom fields are the ceiling.** The native integration covers common objects well. Workflows that depend on custom fields are where teams move to Make, which has fuller custom-field support on the ClickUp side. Check your specific fields before you design around the native path.
- **The automated half needs Professional.** Manual linking works lower down, but "when a deal closes, do this" is a workflow, and fully customisable workflows start at HubSpot Professional. On Starter you get up to 50 simple workflows and should check yours fits.
- **Two automation engines, two places to debug.** Half the logic lives in HubSpot workflows and half in ClickUp automations. That is the price of both directions being native. Write down which side owns which rule before you build the second one.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

### ClickUp

- **Base:** `https://api.clickup.com/api/v2`
- **Auth:** `Authorization: pk_...` (personal token) or OAuth.

| Call | Request | What it does |
|---|---|---|
| `POST /list/{list_id}/task` | `{ "name": "...", "description": "...", "custom_fields": [...] }` | Create a task. Use this only if the native HubSpot action does not cover your fields. |
| `ACTION ClickUp action inside a HubSpot workflow` | - | The native path, and the one to prefer. Both vendors built into the other, so both directions are first-class. |

**Rules that will cost you time if you skip them:**

- The native integration covers common objects well and **thins out at custom fields**. Workflows that depend on custom fields usually move to Make.
- One rule per direction. HubSpot owns "a deal changed, create or update work"; ClickUp owns "work changed, update the deal". Writing to the same field from both sides is a loop.

Docs: https://developer.clickup.com/

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- ClickUp help: HubSpot integration: https://help.clickup.com/hc/en-us/articles/7925934313111-HubSpot-integration
- HubSpot App Marketplace: ClickUp: https://ecosystem.hubspot.com/marketplace/apps/clickup
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clickup-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clickup-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
