An admin installs it once, then every person has to connect their own account.
Nothing to buy. An admin installs each app, then every member connects their own account.
Messages, Activities, two-way sync.
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.
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 |
|---|---|---|
| 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 | Both ways | 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. |
One of those five rows moves in both directions. The four that do not are Drive files into Slack, Drive notifications, New Docs, Sheets and Slides and Meeting status, and those are the rows that decide how you design around this rather than the ones in the brochure.
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. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| 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 |
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: eight field mappings, six action rows and three documented exclusions, each one's note, and the three 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.
Read the second table before enabling domain-wide authentication rather than after. It is the single lever that makes this integration actually happen across a company, and it is also the one that takes a choice away from every member, which is a trade worth making on purpose.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 pair most often declared finished before it works.
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-google/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-google.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.
WhyThe 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.
WhyThe 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.
WhyThe 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.
WhyInstalling 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.
WhyDomain-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.
WhyThey 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.
WhySlack 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.
WhySlack 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.
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.
The official Google Calendar + Slack integration is mostly personal - it doesn't automatically create some big shared team view that everyone can just glance at in Slack without lifting a finger. That's why you're only seeing it on the account that owns it.
r/Slack·February 2026·1 points
Answering somebody titled asking what they were missing, which is the right question and has this answer. It lines up with the documentation: Status Sync reads one calendar, channel notices need a per-channel invite, and the recurring digest needs a paid plan.
looking at the docs, you can have multiple calendars configured for Google and Slack, one being your team's shared calendar and I think you can configure alerts and or views into that shared calendar into a specific channel
r/Slack·February 2026·1 points
Correct, and the hedge in the middle is the useful part: it is a documented capability that nobody is certain about. Multiple calendars connect from the Accounts dropdown, and the channel schedule from a shared calendar is the paid-plan feature in the grid above.
Slack's business-tier requirement for user provisioning is definitely a pain point for small teams. While the Slack API does let you create users, it's not super straightforward unless you're comfortable building, hosting, and securing a custom integration yourself.
r/Slack·January 2026·1 points
About provisioning Slack accounts from Google Workspace rather than about these two apps, and worth distinguishing. Connecting calendars and Drive across a domain is free on every plan; creating the Slack users in the first place is the part behind a tier.
If it's possible for the other company to setup a channel, adding the few users you wish to communicate with and adding your 50 users as guests to that channel, it will be free! Single channel guests are free. You can add 5 free guests for every full member on Slack.
r/gsuite·September 2024·1 points
From a thread about bridging Google Chat and Slack, which is the adjacent problem. The ratio is this person's recollection rather than a published figure, so check it against Slack's current pricing before planning around it.
The inability to disable threaded messages, or at least a toggle that forces them to post to the channel by default instead of requiring a user to check a box each time. Too many people miss too many threaded (hidden) messages.
r/Slack·May 2025·5 points
Not about this integration and directly relevant to it. Every Slack pair in this directory ends in a channel message somebody has to see, and the platform's own defaults are working against that. Worth weighing before choosing a busy channel for a schedule post.
The threads are about the gap between what people expect from these two apps and what they do. The recurring disappointment is specific and correct: the official Google Calendar integration is built around the individual, so nobody gets the glanceable team schedule they imagined. The other theme is provisioning, where practitioners describe Slack's own plan tiers as the obstacle rather than Google.
Only the first two are about these apps, and both corroborate the documentation rather than contradicting it. The last one is here because it describes the medium rather than the integration, and every pair on this hub is ultimately a message in a channel that somebody has to notice.
This is the cheapest integration in the directory and the one whose failure mode is purely organisational. There is no tier to buy, no API allocation to budget and no field mapping to argue about. What there is instead is a two-step rollout where only the first step is visible to the person who did it, and a second step that has to happen several hundred times. Teams that treat it as a change-management task, with domain-wide authentication arranged in advance, get it working in an afternoon; teams that treat it as an install get a long tail of people who believe it is broken.
The Drive behaviour is worth stating plainly to whoever owns compliance, because it is easy to assume the opposite. A file shared from Drive into Slack is a link with a preview, not a copy: it stays in Drive, it is searchable from Slack, and it is governed by Google rather than by your Slack retention policy. That is almost always what you want, and it does mean a Slack export is not a record of every document a team exchanged.
Set against the rest of the collaboration layer, this pair is unusual for having no routing problem at all. Every other Slack integration here can be configured into uselessness by enabling every event until the channel gets muted; these two notify about things addressed to you personally. The judgement they need is not what to route but who connects, which is why the useful measure of success is the share of the team that has connected rather than anything in the admin screen.
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, Google 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.
Google Drive lets you create, share and access Drive files from Slack, surfaces comment and access-request notifications in Slack, and makes shared files searchable there. Google Calendar lets you respond to invites, get reminders before meetings, create events and have your Slack status update automatically while you are in one. They are two separate apps with two separate connections.
No, and this is the step teams miss. An admin installs the app once for the workspace, and after that every member who wants to use it has to connect their own Google account. A rollout that stops at the install looks finished and does nothing for anybody, which is why adoption on this pair is usually a communication problem rather than a technical one.
Yes, with domain-wide authentication, and it needs two people. Workspace owners and admins on Free, Pro and Business Plus, or org owners and admins on Enterprise, can turn it on, and authorising it requires a Google Workspace super admin. That is the one path that avoids asking several hundred people to click a button, and it is a conversation with whoever runs Google Workspace rather than a setting in Slack.
No. Slack documents that files shared from Drive stay in Drive. They can be searched from Slack and they are not stored in your workspace, so your Slack retention policy does not govern them and removing a file from Slack does not remove it from Drive. For most teams that is the right behaviour and it is worth saying out loud to anyone who assumed otherwise.
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.