- Integrations
- /
- Google Drive
- /
- with Slack
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.
Workflows fire when something happens in Google Drive.
- New FileWebhook
- File UpdatedWebhook
- New FolderWebhook
Workflows do something in Slack, instantly.
- Raw API RequestAPI
- Add ReactionAPI
- Archive ChannelAPI
- Cancel Scheduled MessageAPI
- Create CanvasAPI
- Create ChannelAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Google Drive, do it in Slack.
3 Google Drive triggers wired to 45 Slack actions. Most-used pairing: New File → Raw API Request.
Or fire it the other way around.
13 Slack triggers wired to 8 Google Drive actions downstream.
See Slack → Google Drive →Common Google Drive → Slack workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
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.
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.
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.
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.
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.
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.
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.
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.
Fires when a new folder is created in Google Drive (optionally scoped to a parent). Use for templated folder provisioning or governance audit logs.
Connect Google Drive and Slack in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Google Drive and Slack
Open Tiny Command, authorize Google Drive and Slack once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Google Drive trigger
Drop the Google Drive → New File trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-drive.trigger-file-created - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the Google Drive payload into the Slack inputs.
slack.api-request - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Google Drive + Slack.
How long does it take to connect Google Drive and Slack on Tiny Command?
Is the Google Drive ↔ Slack integration real-time?
Can I filter or transform data between Google Drive and Slack?
What Google Drive events can trigger a Slack workflow?
Do I need a paid plan to use Google Drive with Slack?
What if I want Slack → Google Drive instead?
Other apps that pair well with Google Drive.
Wire Google Drive to Slack in 2 minutes.
Free tier available. No credit card. No onboarding call.