---
name: slack-google-integration
description: Connect Slack and Google Workspace: what syncs, which editions carry it, the setup order, and the failures to expect. Covers messages, activities. Use when the user wants to set up, audit or troubleshoot Slack and Google together, or asks why data is not moving between them.
---

# Slack and Google Workspace

> Generated from https://www.reversecontact.com/integrations-hub/slack-integrations/slack-google-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:** Nothing to buy. An admin installs each app, then every member connects their own account.

**What moves:** messages, activities, both ways.
**How it is built:** native, marketplace app. **Effort:** minutes.

## The short version

The Slack Google Workspace integration is one of the five here that costs nothing extra on either side, and the one most likely to be declared finished before it works. An admin installs the Drive and Calendar apps once, and then nothing happens for anybody until each person connects their own Google account. The fix for that at scale is domain-wide authentication, which needs a Slack admin and a Google Workspace super admin in the same conversation. Get those two steps right and this is fifteen minutes; skip the second and you have a workspace where the integration is installed, invisible and quietly blamed.

## Which parts need a paid Slack plan

Rows: Slack plan. Columns: What you want from it. Nothing here costs anything on the Google side, and the apps themselves are free. Two capabilities are gated, and they are not the two anybody guesses: the big administrative one is on every plan, and the small recurring digest is not.

| Slack plan | Members connect their own accounts | Domain-wide authentication | A daily or weekly schedule in a channel | Installing across workspaces from one place |
|---|---|---|---|---|
| Free | Available | Available | Not available | Not available |
| Pro or Business+ | Available | Available | Available | Not available |
| Enterprise Grid | Available | Available | Available | Available |

- **Available.** Slack documents domain-wide authentication as available on all plans, for Workspace Owners and Admins on Free, Pro and Business+ and Org Owners and Admins on Enterprise. The org-level install of the Drive app is an Enterprise organization feature.
- **Not available.** Slack states the daily or weekly schedule notification, both to a channel and as your own daily digest, as a paid-plan feature. Everything else about the apps keeps working on Free.

Counted off that grid, of twelve pairings: nine give you available, three give you not available.

The first two columns read the same all the way down, and that is the finding worth taking away: the capability that decides whether this integration reaches a whole company costs nothing, while the recurring digest that makes it visible in a channel needs a paid plan. Most teams discover those in the wrong order.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Drive files into Slack | One way, in | Create, share and open Drive files from Slack, and search shared files there. The files stay in Drive and are not stored in your workspace. |
| Drive notifications | One way, in | Comment and access-request updates arrive in Slack, which is the half that actually changes how quickly people respond. |
| New Docs, Sheets and Slides | One way, out | Created from inside Slack, which is the lightest version of starting a document where the conversation happened. |
| Calendar invites | Two-way sync | Respond to invites and create events from Slack, with reminders before a meeting starts. |
| Meeting status | One way, in | Slack status updates automatically during a meeting, and syncs only with the primary calendar of the connected Google account. |

## Which field lands where

There is nothing to map here. What there is instead is a set of capabilities split across two separate apps, with a few of them gated by plan and one of them gated by a channel invite, and knowing which is which is the whole job.

| In Slack | In Google | What to know about the match |
|---|---|---|
| Create a Drive file from Slack | Slash command, document, presentation or spreadsheet | Takes a title and an optional message, and offers to share it with a person or channel as it is created. Unchecking that box creates the file without sharing it. |
| Share an existing Drive file | Add from Google Drive | Slack prompts to adjust file permissions when members of the channel cannot view, comment or edit. The prompt is the governance, and it is per share. |
| Drive comments | Replies from inside Slack | Notification scope is managed in Google Drive rather than in Slack: open the file, the comments icon, then Notifications. |
| Your own calendar | The Google Calendar app Home tab | Today, Tomorrow or a chosen date, with event details, guest list and location behind the three-dots menu. Multiple calendars can be connected from the Accounts dropdown. |
| Event responses | The app's Messages tab | Where you accept or change a response. Worth telling people, because the Home tab shows the schedule and does not take the answer. |
| Channel notifications | Only after /invite @google calendar | A per-channel invite rather than an app setting, and the most common reason a correctly configured channel receives nothing. |
| A daily or weekly schedule in a channel | Paid Slack plans | Slack states the recurring schedule notification from a shared calendar is a paid-plan feature, and the same applies to your personal daily schedule. |
| Slack status | Status Sync, off until you turn it on | Written from the calendar you connected. One calendar drives it, which is why a team calendar and a personal one do not combine into one status. |

### What domain-wide authentication changes, beyond saving the setup

| The action | How it reads on the record |
|---|---|
| Who can enable it | Any Workspace or Org Owner or Admin, on all plans including Free |
| What it needs on the Google side | A Google Workspace Super Admin to authorise access |
| Who gets connected | Every member with an email address on the verified domain, automatically |
| What members lose | The ability to disconnect their Google account while it is enabled |
| What members gain without asking | An automatic subscription to event reminder notifications, which they can turn off in Settings |
| Whether one domain covers both apps | No. Calendar and Drive each have their own Add domain step |

**What does not cross:**

- A shared team view of everybody's calendar. The integration is built around the individual, which is the gap practitioners most often describe when they expect a glanceable team schedule in a channel.
- Governance of Drive file access from inside Slack. Permissions stay Google's, and Slack only prompts at the moment of sharing.
- Anything at all in a channel the Calendar app has not been invited to.

## Connect it, in this order

**Who has to do it:** A Slack Workspace or Org Owner or Admin to install, and a Google Workspace Super Admin if you want the domain-wide route. Otherwise every member, one at a time.
**How long:** Twenty minutes to install. Weeks, in practice, waiting for people to connect their own accounts.

### 1. Install each app from the Slack Marketplace

*Where:* Slack Marketplace: Google Drive, Google Calendar

Add to Slack, Add the app, Allow. These are two separate apps with two separate installs, and installing one does nothing for the other. On Enterprise organizations an Org Owner or Admin can install at the org level and push the app to the workspaces that need it.

### 2. Decide now whether members connect themselves or you do it for them

*Where:* Slack: the app Home tab, Settings

The default is per person, and it is where these projects stall. Domain-wide authentication connects every member with an email on your domain automatically, and Slack documents it as available on all plans rather than as an enterprise feature.

### 3. Get a Google Workspace Super Admin for the domain route

*Where:* Slack: Domain-wide Authentication, Add domain

Any Slack owner or admin can start the process, and authorising access on the Google side needs a Super Admin. The two apps each have their own Add domain button, so a domain verified for Calendar is not verified for Drive.

### 4. Understand what the domain route takes away

*Where:* The same screen

Once a domain is verified, members cannot disconnect their Google accounts, and connected members are automatically subscribed to event reminder notifications. They can turn the notifications off in the app's Settings; they cannot turn the connection off.

### 5. Invite the Calendar app into any channel that should get notices

*Where:* Slack: the channel

Type /invite @google calendar in the channel. A channel the app has not been invited to receives nothing, and this is a per-channel step rather than a setting on the app.

### 6. Configure the channel schedule if you are on a paid plan

*Where:* Slack: Google Calendar Home, Channel Notifications

Slack documents the daily or weekly schedule from a shared calendar as a paid-plan feature, both for channels and for your own daily schedule. On Free the app still works; the recurring digest is what is missing.

### 7. Turn Status Sync on deliberately

*Where:* Slack: Google Calendar Home, Settings

It writes your Slack status from your calendar. Worth a conversation before switching it on for a team, because a meeting title is not always something you want posted beside your name.

### 8. Know the reset before you need it

*Where:* Slack Marketplace: Google Calendar, Configuration

Slack's own fix for missing or out-of-date events is to click Revoke under Your Authorization and then Add to Slack again. That is the documented repair rather than a support ticket.

Two of those eight steps are installs and the other six are decisions about people: who connects, who can disconnect, which channels hear anything, and whether your calendar writes your status. That is what makes this the [collaboration layer](layer:collab) pair most often declared finished before it works.

## How to check it worked

- Check a colleague's account rather than your own. Installing the app and connecting your account are different jobs, and the admin who installed it is always the first person connected.
- Invite the app to one channel and confirm something arrives. A channel without the invite is silent and looks identical to a broken integration.
- Share a Drive file with a channel where somebody lacks access. Slack prompts you to adjust the file permissions, which is the behaviour to show people once rather than explain twice.
- If you enabled domain-wide authentication, confirm with one member that they cannot disconnect. That is documented behaviour and it is better discovered in a test than in a complaint.

## 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 |
|---|---|---|
| A channel receives no calendar notifications at all | The Google Calendar app has not been invited to that channel. It is a per-channel step, not an app-wide setting. | Type /invite @google calendar in the channel. Then configure the notifications from the app's Home tab under Channel Notifications. |
| Events are missing or out of date in the app | The authorisation has gone stale. Slack documents this as its own fix rather than a support path. | Open the Google Calendar page in the Slack Marketplace, Configuration tab, click Revoke under Your Authorization, then Add to Slack to reconnect. |
| There is no daily or weekly schedule option | The workspace is on the Free plan. Slack marks the recurring schedule notification as a paid-plan feature in two places. | Nothing to configure. The rest of the app works on Free, and a human posting the schedule is the honest substitute until the plan changes. |
| The integration works for the admin and nobody else | Installing the app and connecting an account are different jobs. The admin who installed it connected themselves in the process. | Either chase every member through the Home tab, or enable domain-wide authentication and connect everybody at once. |
| A member wants to disconnect their Google account and cannot | Domain-wide authentication is enabled, and Slack documents that members cannot disconnect while it is. | There is no per-member exemption. They can turn off the event reminder notifications they were automatically subscribed to, which is usually the real complaint. |
| Drive is connected and Calendar is not, or the reverse | They are two separate apps with separate installs, separate authorisations and separate Add domain steps. | Repeat every step for the second app. A domain verified for one is not verified for the other. |
| Somebody shared a Drive file nobody in the channel can open | Slack prompts to adjust file permissions when members lack access, and the prompt can be dismissed. | Fix the sharing in Google Drive. Slack never owns these permissions, which is worth saying out loud to a team that assumes posting a file grants access to it. |
| The Agents and tools tab is not in the sidebar | Slack renamed it, and older workspaces still show the previous label. | Look for a Tools tab instead, and click More if neither is visible. Slack notes this on both app articles. |

## What breaks, from the vendors' own docs

- **Install and connect are different jobs.** An admin installs the app for the workspace; every member who wants it then connects their own Google account. Nothing about the admin screen suggests the rollout is incomplete, so the usual failure is a workspace where the apps are installed, a handful of people connected in the first week, and everybody else concluded the integration does not work.
- **Domain-wide authentication needs two admins.** It is available to workspace owners and admins on Free, Pro and Business Plus and to org owners and admins on Enterprise, and authorising it requires a Google Workspace super admin. In most companies those are two different people on two different teams, which makes this a scheduling problem rather than a configuration one. It is also the only route that scales past a few dozen people.
- **Status syncing reads one calendar.** Slack syncs status with the primary calendar of the connected Google account and no other. A person who keeps client meetings on a second calendar shows as available through all of them, and there is no setting that adds one. The same shape of limit as HubSpot's calendar sync, for the same reason.
- **Drive files are not yours to govern in Slack.** Files shared from Drive stay in Drive and are not stored in the workspace. Slack retention does not apply to them, an export will not contain them, and revoking access happens in Google rather than in Slack. That is the correct design and it matters to anyone who assumed a Slack export was a complete record of what was shared.

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

### Slack

- **Base:** `https://slack.com/api`
- **Auth:** `Authorization: Bearer xoxb-...` (bot token). Scope `chat:write`, plus `chat:write.public` to post to a channel the bot has not joined.

| Call | Request | What it does |
|---|---|---|
| `POST /api/chat.postMessage` | `{ "channel": "C0123", "text": "...", "blocks": [...] }` | The only call most of these workflows need. Use this when you need to choose the channel at runtime. |

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

- **HubSpot's Slack workflow action cannot route to the channel associated with the record.** It sends to a channel chosen at design time. If you need per-record routing, look the association up yourself and call `chat.postMessage` directly.
- Creating a Slack channel from a HubSpot workflow requires HubSpot Professional or Enterprise.
- Route only events a named human must act on within minutes. A channel that fires forty times a day gets muted, and a muted channel is indistinguishable from a working one in the admin screen.

Docs: https://api.slack.com/methods/chat.postMessage

## 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

- Slack help centre: Google Drive for Slack: https://slack.com/help/articles/205875058-Google-Drive-for-Slack
- Slack help centre: Google Calendar for Slack: https://slack.com/help/articles/206329808-Google-Calendar-for-Slack
- Slack help centre: enable domain-wide authentication for calendar and file apps: https://slack.com/help/articles/360047862573-Enable-domain-wide-authentication-for-calendar-and-file-apps-in-Slack
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-google-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-google-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.*
