Start free
Per-pair page

Connect Google Drive to Slack in two minutes.

Real-time triggers from Google Drive, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect Google Drive to Slack — start free See reverse direction
Trigger app
Google Drive as the trigger

Workflows fire when something happens in Google Drive.

Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Connect Google Drive to Slack — start free
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Google Drive → Slack

When something happens in Google Drive, do it in Slack.

3 Google Drive triggers wired to 45 Slack actions. Most-used pairing: New File → Add Reaction.

Slack → Google Drive

Or fire it the other way around.

13 Slack triggers wired to 8 Google Drive actions downstream.

See Slack → Google Drive →
Popular pairings

Common Google Drive → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations
When new file in Google Drive, add reaction in Slack.

Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.

When new file in Google Drive, raw api request in Slack.

Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.

When new file in Google Drive, archive channel in Slack.

Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.

When new file in Google Drive, cancel scheduled message in Slack.

Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.

When file updated in Google Drive, add reaction in Slack.

Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.

When file updated in Google Drive, raw api request in Slack.

Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.

When file updated in Google Drive, archive channel in Slack.

Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.

When file updated in Google Drive, cancel scheduled message in Slack.

Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.

When new folder in Google Drive, add reaction in Slack.

Fires when a new folder is created in Google Drive (optionally scoped to a parent). Use for templated folder provisioning or governance audit logs.

How it works

Connect Google Drive and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Google Drive and Slack

    Open TinyCommand, authorize Google Drive and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Google Drive trigger

    Drop the Google Drive → New File trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/google-drive.trigger-file-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Add Reaction action below it. Map fields from the Google Drive payload into the Slack inputs.

    slack.add-reaction
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Google Drive + Slack.

How long does it take to connect Google Drive and Slack on TinyCommand?
Under two minutes. Authorize Google Drive and Slack once each, drop the Google Drive trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Google Drive ↔ Slack integration real-time?
Yes. Both Google Drive and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Google Drive and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What Google Drive events can trigger a Slack workflow?
Any of the 3 Google Drive triggers, including "New File". Each fires in real time when the matching event happens in Google Drive.
Do I need a paid plan to use Google Drive with Slack?
No. There's a free tier that covers most Google Drive+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → Google Drive instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/google-drive page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Google Drive.

+
Google Drive + Gmail
Email
+
Google Drive + Google Sheets
Spreadsheets & Databases
+
Google Drive + HubSpot
CRM & Sales
+
Google Drive + Stripe
Payments
+
Google Drive + Notion
Productivity
+
Google Drive + Airtable
Spreadsheets & Databases
Connect Google Drive to Slack — start free