Free on every plan, and only the person who set it up can extend it.
Nothing beyond both accounts. Guests and limited members cannot use it.
Tasks, Messages, two-way sync.
One of the five integrations in this directory that costs nothing extra on either side, and the only one whose main failure mode is an org chart problem. It does what you want: task, Doc and comment links unfurl with real detail, a message becomes a task or a comment without leaving Slack, and ClickUp activity syncs into the channels you choose. Two things decide whether it survives contact with a real team. Guests and limited members are excluded entirely, and only the person who created the Workspace connection can add new activity locations, so the integration quietly depends on one named individual still working here.
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 |
|---|---|---|
| Task, Doc and comment links | One way, out | Unfurl in Slack with the title, a description preview, status, assignees, priority and location. Needs a personal connection to appear. |
| A Slack message to a task | One way, in | Added as a ClickUp comment, styled as a quote, with a link back to the original Slack message. |
| New tasks | One way, in | Created with the /clickup new command or the Create Task action. Tasks can also be edited straight from a task preview. |
| ClickUp activity | One way, out | Task creation, status changes, comments, attachments and assignee changes, per Space, Folder, Subfolder or List. Public and private channels on a personal connection, public only on a Workspace connection. |
| Slack messages into search | One way, in | Connected Search indexes selected public channels back one year, and the indexing pass can take up to 24 hours. |
| Messages to a Super Agent | One way, in | Sent from the message menu. Attachments are not included. |
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.
Nothing is mapped field to field. What moves is a link, a message or an activity, and each has its own rule about where it can land.
| In Slack | In ClickUp | What to know about the match |
|---|---|---|
| A ClickUp task, Doc or comment link | An unfurled Slack preview | Title, a description preview and status, shown to everybody in the channel regardless of their ClickUp permissions. |
| A Slack message | A ClickUp comment on a task | Styled as a quote with a link back, from the message action menu. |
| A Slack message | A new ClickUp task | Through the slash command or the Create Task action, so the thread that spotted the work becomes the work. |
| ClickUp activity | A mapped channel | Creation, status changes, comments, attachments and assignments, chosen per action rather than all at once. |
| Selected public Slack channels | ClickUp Connected Search | Indexed, and searchable only by people who are members of both sides. |
Three 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: five field mappings and three documented exclusions, each one's note, and the four 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.
The unfurl is the row to think about twice: a private task's title and description become visible to everyone in the channel, and that is a disclosure decision rather than a formatting one.
ClickUp lists this integration as available on every plan, so price is not the gate. The two things that actually decide what works are how you connected and who is asking. Pick one on each side and the grid marks the answer.
Pick one on each side.
| How you connected | Public channel | Private channel |
|---|---|---|
| Personal connection | Activity sync works | Activity sync works |
| Workspace connection | Activity sync works | Not available |
| Guest or limited member | Not available | Not available |
Counted off that grid, of six pairings: three give you activity sync works, three give you not available. The middle row is where teams get caught: a Workspace connection is the tidier thing to govern and it is the one that cannot reach a private channel, which is usually where the work being discussed actually lives.
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: App Center, Slack
A personal connection can sync ClickUp activity to public and private Slack channels. A Workspace connection can only sync to public ones. Teams that run deal or project work in private channels pick the Workspace connection for the governance and then find the channels they care about are unavailable.
The same decision
Only the creator of a Workspace connection can set up new locations for ClickUp activity messages. Admins and owners cannot add new ones; they can only map existing messages to more Spaces, Folders, Subfolders or Lists. Connect as somebody who will still be here next year.
App Center: Slack, Connect an app
You can select specific public channels or choose All public channels. This is a scope decision rather than a convenience one, and the OAuth scopes are published in ClickUp's own table if security needs to read them before you click.
ClickUp: Slack notification settings
Sync Spaces, Folders, Subfolders and Lists to the channels that should hear about them, then choose which task and Doc actions actually notify. Mapping everything is the mistake: a channel that reports every status change gets muted in a week.
ClickUp: AI Command Bar
Initial indexing can take up to 24 hours and you can watch the progress. After that, a new Slack message takes up to ten minutes to become searchable, so neither number is a fault to report.
ClickUp: user roles
Guests and limited members cannot use the integration at all. On a workspace that runs with contractors or clients as guests, that is a meaningful share of the people in the channel.
The first two steps are the ones to slow down on: between them they decide which channels work and who can change the setup later, and both are awkward to undo.
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/slack-clickup/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-clickup.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.
WhyClickUp names three reasons: the channel was deleted, you have not joined it, or it is new.
Join the channel, then wait. A newly created or joined channel can take five minutes to appear, and no logout is needed.
WhyA Workspace connection syncs to public channels only. A personal connection reaches both.
Decide which you want. Changing it means reconnecting, so it is worth settling before the mapping work.
WhyOnly the creator of the Workspace connection can add locations. Admins and owners can map existing messages to more locations and nothing else.
Go back to the connection creator, or recreate the connection under an account the team will keep.
WhyIndexing. A new message takes up to ten minutes to become searchable, and the initial index can take 24 hours.
Check the progress in the AI Command Bar before reconnecting anything.
WhyA link unfurl shows the title and description preview to the channel, whatever that person's ClickUp permissions are.
Treat pasting a task link as publishing its title. There is no permission check on the preview, so the control is which channel you paste into.
WhyGuests and limited members are excluded from the integration.
A full member seat is the only route. Plan around it rather than troubleshooting it.
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 2024 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.
I will save you some time. No. And it will not. You should not expect a project management tool to replace a communications tool
r/clickup·September 2024·6 points
Transcribed with the contractions expanded, and it is the majority view in these threads. If that is right, the integration is not a stopgap before consolidation, it is the permanent arrangement, and it deserves the configuration attention above.
I am migrating my team from Slack to ClickUp and will use this thread to share the positive and negative points we have observed throughout the transition
r/clickup·June 2026·26 points
The most upvoted thread in the set, which says something about how live this question is. Worth reading before committing either way, because it is one of the few accounts that covers the weeks after the decision rather than the day of it.
I am a love/hate with clickup due to new features like chat being fantastic in principle, but unusable in practice
r/clickup·March 2025·14 points
A useful warning for the integration too. The features in the table above are real, and the ones teams abandon are abandoned for configuration reasons rather than capability ones, usually a channel mapped to too much.
Switched my small business of 3 people and were happy with it. Only real downside is the video chat SyncUp feature does not ring like Slack does. So sometimes people miss the notification.
r/clickup·March 2025·7 points
Three people is the scale where consolidation works. The integration exists for everybody above that, and the thing that breaks at scale is the same thing: whether a notification actually reaches a person.
Teams often struggle using ClickUp and Slack together because Slack is great for quick chat but not for task management, while ClickUp is structured for tracking work.
r/clickup·January 2026·4 points
Which is what the mapping step is really for. Decide that work lives in ClickUp and Slack reports on it, then map only the actions somebody would act on, and the integration stops being a notification firehose.
Almost nobody posts about configuring this integration, so the search was for the decision behind it: whether to run both tools or let one absorb the other. ClickUp has been shipping chat features aimed squarely at that question, and the threads are a running verdict on how it is going. The consistent answer from people who have tried both is that the integration is the realistic arrangement and the replacement is not, which makes the setup choices above the ones that matter.
The threads make the case for configuring this carefully rather than for choosing between the two tools, which is convenient, because the two decisions that matter here are both made in the first ten minutes.
The integration is cheap, quick and genuinely good, which means the interesting question is not whether to install it but how it fails. Two of its limits are about people rather than data, and both are invisible at install time. Guests and limited members cannot use it, so in any workspace where clients or contractors hold those roles, a chunk of the channel watches a workflow they cannot join; and on a Workspace connection, only the creator can add new activity locations, which turns a convenience feature into a dependency on one named person. Install it as an admin whose account will outlast the project, and write down who that was.
The configuration decision worth making deliberately is which connection type to use, because it trades reach for control. A personal connection covers public and private channels, which is what most delivery work actually needs, and ties the setup to an individual. A Workspace connection is the admin-sanctioned route and reaches public channels only. Teams that want private channel notifications and central ownership are asking for something that is not on offer, and the usual compromise is a personal connection owned by a service account rather than by a person.
What makes this pair worth a page at all is that it is the rare integration where the volume problem has been solved for you. Every other Slack pairing in this directory can be configured into uselessness by enabling every event type until the channel gets muted; here there is no limit on how many activity messages you set up and duplicates are suppressed when several people configure the same one. That still leaves the judgement call: route the activity a named human must act on, keep the rest in ClickUp where it belongs, and remember that the closed won handover works precisely because it moves one event rather than all of them.
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 Slack, ClickUp 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.
None in particular. ClickUp documents the Slack integration as available on every ClickUp plan, including Free Forever, and there is nothing to buy on the Slack side either. The restriction is by role rather than by plan: guests and limited members cannot use the integration at all, which in agencies and client-facing workspaces excludes a meaningful share of the people in the channel.
Yes, that direction works. The reverse does not: a ClickUp Workspace can only be connected to one Slack workspace at a time. So a company running two Slack workspaces after an acquisition has to pick which one its ClickUp Workspace talks to, and the answer is a decision rather than a setting.
Scope and reach. A personal connection can sync ClickUp activity to both public and private Slack channels. A Workspace connection, which only ClickUp Workspace owners and admins can enable, reaches public channels only. The awkward part is ownership: only the creator of the Workspace connection can add new locations for activity messages. Admins and owners can map existing messages to additional Spaces, Folders, Subfolders and Lists, but they cannot add a new one.
The preview will show. ClickUp states that links to private ClickUp tasks or Docs will be seen by everyone in a channel, and an unfurled task preview carries the title, a description snippet, the status, assignees, priority and location. That is the right trade for most teams and the wrong one for a few, and it is worth saying out loud to anyone who keeps sensitive work in ClickUp before you install this.
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.