Collaboration

The collaboration layer, and what reaches a human

A stack that works perfectly and tells nobody has not finished the job.

collaboration 3 tools
layerCollaboration
forWhere the team works
tools here3
integrations15
with a guide15
checked Tool hubs 3 of 3
The short version

What this layer is actually for

Where the team works. In this directory that is Slack, ClickUp and Google.

This layer is the one people underrate, because its integrations are usually simple: a notification, a channel message, a task. The value is not in the complexity, it is in the fact that a person now knows.

The thing worth checking here is direction. Pushing a message into a channel is almost always available; doing something useful back from that channel, without leaving it, is the part that varies between tools and tiers.

In this layer

The 3 tools this directory covers in the collaboration layer

A tool can sit in more than one layer, and several here do. The layers on each card are the full set, not just this one.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 3 of 3

Slack

Where the stack tells a human
10 integrations
LayerCollaboration
Guides +2

Slack is the integration that decides whether the rest of the stack gets used. A pipeline that enriches, scores and routes perfectly still fails if a rep finds out about it tomorrow. The limits here are about routing, not about the connection.

  • A HubSpot workflow can send to a static channel, not to the channel on the record
  • Deal and company records can each be associated with a channel
  • Creating a channel from a workflow needs HubSpot Professional or Enterprise
Entry price$0/mo Visit See the 10 integrations

ClickUp

Turning a closed deal into delivery work
4 integrations
LayerCollaboration
Guides

The reason this pair comes up constantly is handover. A deal closes in the CRM and something has to happen in the place delivery actually lives. ClickUp is the one that put both halves of that in place: its actions run inside HubSpot workflows, and HubSpot actions run inside ClickUp automations.

  • ClickUp actions available inside HubSpot workflows
  • HubSpot actions available inside ClickUp automations
  • Custom fields are where teams fall back to Make
Entry price$0/mo Visit See the 4 integrations

Google Workspace

The integration everybody installs first
3 integrations
LayerCollaboration
Guides

Not a sales tool, and the most consequential integration in most stacks anyway. Gmail and Calendar are the top two installs on HubSpot's marketplace by a wide margin, because they are the ones that decide whether activity data exists at all.

  • Gmail is the most-installed app on the HubSpot marketplace, at 532,000 installs
  • Google Calendar follows at 289,000, ahead of Outlook at 247,000
  • Sheets remains the most common handover format between tools that will not talk
Entry price$0/mo Visit See the 3 integrations

The useful question is whether somebody can act from the notification, or only read it and go elsewhere to act.

Across the edge

15 integrations that touch this layer

Each record carries the layers it spans, so an integration appears here when this layer is one of them. Start with how it is built, because a native app and a webhook you maintain are the same feature with completely different owners.

15 of these 15 have a full guide behind them, HubSpot and ClickUp and HubSpot and Slack among them. 4 of the 8 worked stacks here run on this layer, among them Inbound speed to lead and Agent-written account briefs.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 15 of 15
↔

HubSpot and ClickUp

Two-way sync
BuiltNativeMarketplace appZapier, Make or n8n
WatchNeeds a higher plan

The rare pair where each vendor built the half that runs inside the other.

  • Moves: Deals, Contacts, Companies, Tasks
  • Needs: HubSpot workflows for the automated direction, so Professional or above
Needs a higher plan · minutes Read the guide
⋅

HubSpot and Slack

Events only
BuiltNativeMarketplace app
WatchNeeds a higher plan

Notifications are easy. Routing to the right channel is the part nobody built.

  • Moves: Activities, Messages, Deals, Companies
  • Needs: HubSpot Professional or Enterprise to create a channel from a workflow
Needs a higher plan · minutes Read the guide
⋅

Salesforce and Slack

Events only
BuiltNativeMarketplace app
WatchNeeds a higher plan

The one pair where the same company owns both sides.

  • Moves: Deals, Activities, Messages, Contacts
  • Needs: Sales Cloud, plus a Slack workspace you can install apps into
Needs a higher plan · minutes Read the guide
↔

Salesforce and ClickUp

Two-way sync
BuiltNativeMarketplace app
WatchNeeds a higher plan

Two integrations, both on Business Plus, and only the names sync both ways.

  • Moves: Tasks, Deals, Companies
  • Needs: ClickUp Business Plus or Enterprise, a Salesforce admin, and beta access for the sync
Needs a higher plan · hours Read the guide
⋅

Slack and Gong

Events only
BuiltNativeMarketplace app
WatchPaid licence first

Channel alerts come from streams, and a stream has to be the standard kind.

  • Moves: Messages, Activities
  • Needs: A Gong contract, a Slack admin to install the app, and a Gong admin to connect it
Paid add-on or licence · minutes Read the guide
⋅

Slack and Outreach

Events only
BuiltNativeMarketplace app
WatchPaid licence first

Connected once for the whole instance, then every notification is personal.

  • Moves: Messages, Activities
  • Needs: An Outreach contract, an Outreach admin, and permission to add apps to Slack
Paid add-on or licence · minutes Read the guide
⋅

Slack and Zapier

Events only
BuiltZapier, Make or n8nMarketplace app

One message a second per channel, and a bot message cannot start a Zap.

  • Moves: Messages
  • Needs: A Zapier plan sized to your task volume, and a free app slot on a free Slack plan
Metered by usage · minutes Read the guide
↔

Slack and n8n

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

The trigger needs a bot token and the node wants OAuth, so you build both.

  • Moves: Messages
  • Needs: An n8n instance you host or rent, and a Slack app with the right token type
Metered by usage · hours Read the guide
↔

Slack and Google

Two-way sync
BuiltNativeMarketplace app
WatchNo upgrade needed

An admin installs it once, then every person has to connect their own account.

  • Moves: Messages, Activities
  • Needs: Nothing to buy. An admin installs each app, then every member connects their own account.
Included on both sides · minutes Read the guide
↔

Apollo and Slack

Two-way sync
BuiltNativeMarketplace appBuilt on the API
WatchNo upgrade needed

Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.

  • Moves: Messages, Activities, Contacts
  • Needs: An Apollo plan and a Slack workspace. An Apollo admin to connect it, and professional or organization for agents.
Included on both sides · minutes Read the guide
The data layer

Where Reverse Contact sits under this layer

Reverse Contact is not a collaboration tool and has no marketplace app in this layer. It is the data layer underneath it: one API that resolves an email, a domain or a profile URL into a verified people and company record, so that what this layer moves is worth moving. This directory documents 3 routes into this layer, 3 of them with a full guide.

Every documented route into a stack sits on the Reverse Contact hub.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every number on this page is derived from those records rather than typed, and each record was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-28
Sources
2 vendor documents
Paid placement
None

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.

Ask an assistant