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

# Salesforce and ClickUp

> Generated from https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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:** ClickUp Business Plus or Enterprise, a Salesforce admin, and beta access for the sync

**What moves:** tasks, deals, companies, both ways.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

Two integrations share this pair and both sit on ClickUp Business Plus or Enterprise, which rules it out for most of the teams who ask about it. Salesforce Sync turns accounts and opportunities into ClickUp tasks in a dedicated Space, which is genuinely useful for a delivery team working off closed deals. What makes or breaks it is the field model: names and opportunity statuses sync both ways and everything else is dumped into the task description as text. If your delivery process needs to filter on close date or amount, that is a text blob rather than a field, and this is not the integration you wanted.

## Which plan carries it, and who has to connect

Rows: ClickUp plan. Columns: Who has connected. One gate and one quirk. ClickUp puts both halves on the same two plans, and then requires every user to connect individually rather than letting an admin do it once.

| ClickUp plan | Package installed only | Package installed and user connected |
|---|---|---|
| Free, Unlimited or Business | Nothing | Nothing |
| Business Plus or Enterprise | Nothing | Previews, search and creation |

- **Nothing.** Either the ClickUp plan is below Business Plus, or that particular person has not authorised their own connection. The managed package being installed is necessary and not sufficient.
- **Previews, search and creation.** Link previews across tasks, comments, Docs and Chat, the Salesforce panel on a task, Connected Search over Salesforce content, and record creation from the AI Command Bar.

Counted off that grid, of four pairings: three give you nothing, one gives you previews, search and creation.

Three of the four cells are empty, and the one that is not needs two separate things to have happened, which is worth knowing before anybody reports the integration as broken.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Account names | Two-way sync | The only account field that is a field on both sides. Accounts only sync at all if they are related to an opportunity. |
| Opportunity names and statuses | Two-way sync | Edit the task in ClickUp and the change reaches Salesforce. |
| Every other account and opportunity field | One way, out | Written into the ClickUp task description as text. Readable, not filterable, not automatable. |
| Salesforce records into search | One way, out | Connected Search covers tasks, opportunities, contacts, leads, accounts, quotes, contracts and cases. It previews rather than syncs. |
| New Salesforce tasks and leads | One way, in | Created from ClickUp's command bar through Connected Search, without opening Salesforce. |

## Which field lands where

Nothing is mapped field to field. What this integration moves is context: a Salesforce record rendered inside ClickUp, and a couple of creation commands going the other way.

| In Salesforce | In ClickUp | What to know about the match |
|---|---|---|
| A Salesforce record URL | A dynamic preview in ClickUp | In task descriptions, comments, Docs and Chat messages alike. The preview type can be changed by hand from the ellipsis menu. |
| Every Salesforce link in a task | The Salesforce panel in the task sidebar | Appears after the first link is pasted, and collects the rest. |
| An AI Command Bar command | A new Salesforce task or lead | Create New Salesforce Task and Create New Salesforce Lead, typed rather than clicked. |
| Salesforce content | ClickUp Connected Search | Searchable from ClickUp, on the same Business Plus and Enterprise gate as the rest. |

**What does not cross:**

- Anything, for a user who has not made their own connection. Only personal connections are supported.
- Anything, below ClickUp Business Plus.
- Fields, in either direction. This is a context and creation integration rather than a sync.

## Connect it, in this order

**Who has to do it:** A Salesforce admin to install the package, then each ClickUp user individually. There is no workspace-wide connection here.
**How long:** Twenty minutes for the admin, then a minute per person.

### 1. Check the ClickUp plan first

*Where:* ClickUp: billing

Both halves, Connected Search and Salesforce Sync, are Business Plus and Enterprise features. Below that there is nothing to configure, and ClickUp notes that pricing and packaging are subject to change.

### 2. Have a Salesforce admin install the managed package

*Where:* The ClickUp install package link, logged in as a Salesforce admin

Only Salesforce admins can install or upgrade it. If an earlier version is present the button says Upgrade rather than Install, and upgrading keeps the existing data.

### 3. Connect from the ClickUp App Center, per person

*Where:* ClickUp: App Center, Salesforce

Click Connect and follow the authorisation. Only personal connections are supported, which means every user who wants this does it themselves and an admin cannot do it for the team.

### 4. Paste a Salesforce link and watch the preview appear

*Where:* A task description, comment, Doc or Chat message

Link previews work in all four surfaces. After the first Salesforce link in a task, a Salesforce icon appears in the task sidebar listing every link posted there, which is the part that makes the task a place to work from rather than a reference.

### 5. Use the AI Command Bar for creation

*Where:* ClickUp: AI Command Bar

Create New Salesforce Task and Create New Salesforce Lead are commands rather than buttons, so they are discoverable only if somebody tells the team they exist.

The per-person connection is the detail that decides adoption: this integration does not arrive for the team when an admin turns it on, it arrives one person at a time.

## How to check it worked

- Paste a Salesforce record link into a task and confirm it renders as a preview rather than a URL.
- Check the Salesforce icon appears in that task's sidebar afterwards.
- Have a second person open the same task. If they see a bare link, they have not made their own connection, which is expected.
- Try Create New Salesforce Lead from the AI Command Bar and confirm it reaches Salesforce.

## 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 |
|---|---|---|
| One person sees previews and another sees a bare link | Only personal connections are supported. The second person has not authorised their own. | Have them connect from the ClickUp App Center. No admin action will do it on their behalf. |
| The integration is not available in the App Center | The ClickUp plan is below Business Plus. | That is a plan question for both halves, Connected Search and Salesforce Sync alike. |
| A Salesforce URL does not render as a preview | Not every Salesforce URL type generates a dynamic preview, and the preview type can be set by hand. | Hover over the link and change the type from the ellipsis menu before concluding it is unsupported. |
| Nobody uses the creation commands | They live in the AI Command Bar as typed commands rather than as visible buttons. | Tell the team the exact phrases. Discoverability is the whole problem here. |
| A Salesforce admin cannot find the upgrade | With an earlier version installed, the button reads Upgrade rather than Install. | Use it. ClickUp documents that upgrading keeps the existing data. |

## What breaks, from the vendors' own docs

- **Business Plus is the floor, for both halves.** Salesforce Sync and Salesforce Connected Search are each documented as Business Plus and Enterprise features. ClickUp's free and lower paid plans carry neither. Guests and limited members cannot use Connected Search at all, which matters in any workspace where clients hold those roles.
- **Only names and statuses are really synced.** Account names sync both ways and opportunity names and statuses sync both ways. Everything else on both objects is added to the ClickUp task description. A description is not a field: you cannot build a view, a filter or an automation on the close date if the close date is a line of text inside a paragraph.
- **No opportunity, no account.** Accounts only sync if they are related to a Salesforce opportunity. If you expected ClickUp to hold your account list, it will hold the subset with open or closed deals against it and nothing else, and there is no setting that changes this.
- **The sync is in beta and gated behind a form.** ClickUp documents the sync integrations as beta, and the setup instructions tell you to click Contact Us and submit the beta form before you can proceed. The first sync can take several hours depending on volume, and failures arrive as task comments from the admin who set it up rather than in a log, so nobody sees them unless they open the task.

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

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

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

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

### 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 centre: Salesforce Sync integration: https://help.clickup.com/hc/en-us/articles/29231790107031-Salesforce-Sync-integration
- ClickUp help centre: Salesforce Connected Search integration: https://help.clickup.com/hc/en-us/articles/24113074235927-Salesforce-Connected-Search-integration
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-clickup-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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.*
