Automate Google Drive + Slack
Where the documents live — and pile up. Team chat where operations actually surface. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Research Analyst already works across Google Drive and Slack — free, and it runs on your machine.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Google Drive into Slack.
When a file lands in a folder in Google Drive…
…an agent can post a rich channel message in Slack — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can DM a teammate in Slack — after reading the context and deciding it should.
When a file is shared in Google Drive…
…an agent can open a thread with findings in Slack — after reading the context and deciding it should.
When a message hits a channel in Slack…
…an agent can read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a keyword or mention fires in Slack…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a reaction is added in Slack…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
The Google Drive and Slack hand-off, setup template
Start with the google-drive-api node and the slack-api node. Configure the Google Drive source payload, the agent input, and the Slack operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "81773ec2-a825-40f1-ac8e-e711bdda03ee",
"name": "Google Drive → Slack",
"nodes": [
{
"id": "719cb822-e61f-4d9c-a120-aa5438234540",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "e773603b-0187-4051-a49c-2df40ce01376",
"text": "Read Google Drive",
"x": 512,
"y": 336,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_FILES",
"folderId": "CONFIGURE_FOLDERID"
},
"description": "Setup template for Google Drive API. Interact with Google Drive to perform various operations on files and folders. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "410f8eb1-64a3-4219-a0a2-e91c8168db92",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Drive item. Decide whether it warrants action in Slack, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b92626c1-d8b3-4fd5-a601-cd6e5d76ee56",
"text": "Configure destination in Slack",
"x": 512,
"y": 720,
"isEditing": false,
"type": "slack-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "SEND_MESSAGE",
"channelId": "CONFIGURE_CHANNELID",
"message": "CONFIGURE_MESSAGE"
},
"description": "Setup template for Slack API. Interact with Slack to perform various operations such as sending messages, uploading files, managing reactions, and more. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "9cb5a6ab-a93f-404c-ae0f-3edfb7631ad0",
"start": {
"id": "719cb822-e61f-4d9c-a120-aa5438234540",
"type": "output"
},
"end": {
"id": "e773603b-0187-4051-a49c-2df40ce01376",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2f00c023-c178-4a50-ab7c-5c9f5bc248e8",
"start": {
"id": "e773603b-0187-4051-a49c-2df40ce01376",
"type": "output"
},
"end": {
"id": "410f8eb1-64a3-4219-a0a2-e91c8168db92",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "71326d62-43a9-43dd-a473-62cd882432be",
"start": {
"id": "410f8eb1-64a3-4219-a0a2-e91c8168db92",
"type": "output"
},
"end": {
"id": "b92626c1-d8b3-4fd5-a601-cd6e5d76ee56",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Drive API
Interact with Google Drive to perform various operations on files and folders.
- action — The action to perform on Google Drive Current example:
LIST_FILES. - folderId — The ID of the folder (for LIST_FILES, UPLOAD_FILE, CREATE_FOLDER) Current example:
CONFIGURE_FOLDERID.
Configure Slack API
Interact with Slack to perform various operations such as sending messages, uploading files, managing reactions, and more.
- action — The action to perform on Slack Current example:
SEND_MESSAGE. - channelId — The ID of the Slack channel Current example:
CONFIGURE_CHANNELID. - message — The message to send Current example:
CONFIGURE_MESSAGE.
Install Research Analyst
Research Analyst already uses both Google Drive and Slack, so installing it gives you this exact hand-off wired up — connected, editable, and running on your own machine.
Runs on your own machine · See what it does
Wiring Google Drive to Slack
- Download AGNT Community Core — free and local-first.
- Connect Google Drive with one OAuth sign-in and Slack with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop google-drive-api and slack-api onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Google Drive and what was written to Slack.
Google Drive and Slack — common questions
Can I connect Google Drive to Slack without writing code?
Yes. Google Drive connects with one OAuth sign-in and Slack with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when a file lands in a folder, post a rich channel message” — and the agent handles the rest.
How is this different from a field-mapping Google Drive to Slack automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles auto-summarise incoming docs the way a colleague would — reading the Google Drive context, judging it, then writing to Slack with the reasoning recorded.
Does my Google Drive and Slack data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Drive or Slack tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Google Drive and Slack run leave behind?
A receipt: what was read in Google Drive, which tools ran with which arguments, what the agent concluded, and what it wrote to Slack. Anything consequential can sit behind an approval gate so a person signs off before it happens.
