Automate Google Sheets + Slack
The database every team already has open. 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.
Report Assembler already works across Google Sheets and Slack — free, and it runs on your machine.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Slack is a decision about the Google Sheets event rather than a transcription of it.
When a row is added or edited in Google Sheets…
…an agent can post a rich channel message in Slack — after reading the context and deciding it should.
When a sheet crosses a threshold in Google Sheets…
…an agent can DM a teammate in Slack — after reading the context and deciding it should.
When a schedule fires in Google Sheets…
…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 append and update rows in Google Sheets — with the reasoning recorded in the run’s receipt.
When a keyword or mention fires in Slack…
…an agent can read ranges for reporting in Google Sheets — with the reasoning recorded in the run’s receipt.
When a reaction is added in Slack…
…an agent can maintain a rolling dashboard tab in Google Sheets — with the reasoning recorded in the run’s receipt.
Copy this Google Sheets → Slack workflow
Google Sheets is reached through the google-sheets-api node and Slack through the slack-api node. Between them sits the agent, which is the part a field-mapping tool cannot do: it reads the item and decides whether the hand-off is warranted at all.
{
"id": "9765cc6b-ac6f-438f-a682-8f4ccd66384a",
"name": "Google Sheets → Slack",
"nodes": [
{
"id": "c9e4ff73-8386-478a-abe0-ddf9eb2c0340",
"text": "Watch Google Sheets",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-sheets-new-row",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for new rows added to a specified Google Sheet and trigger the workflow when a new row is detected.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "362c2f67-59b0-46cd-adbd-9eb24eefef7e",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Google Sheets item. Decide whether it warrants action in Slack, and explain why."
},
"description": "Decides whether this Google Sheets item warrants anything in Slack.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "f9146252-af19-427a-ab74-ce108133e67c",
"text": "Act in Slack",
"x": 512,
"y": 528,
"isEditing": false,
"type": "slack-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "SEND_MESSAGE"
},
"description": "Interact with Slack to perform various operations such as sending messages, uploading files, managing reactions, and more.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "9a727565-061d-407d-a767-a87a970a3782",
"start": {
"id": "c9e4ff73-8386-478a-abe0-ddf9eb2c0340",
"type": "output"
},
"end": {
"id": "362c2f67-59b0-46cd-adbd-9eb24eefef7e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "24c44747-49b4-4476-a4c0-4d4fc3d05c14",
"start": {
"id": "362c2f67-59b0-46cd-adbd-9eb24eefef7e",
"type": "output"
},
"end": {
"id": "f9146252-af19-427a-ab74-ce108133e67c",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Report Assembler
Report Assembler already uses both Google Sheets 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
What building this looks like
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Slack (one OAuth sign-in) and Google Sheets (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; google-sheets-api does the reading and slack-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Google Sheets and Slack — common questions
Can I connect Google Sheets to Slack without writing code?
You can build it entirely from the canvas. Authorise Google Sheets with one OAuth sign-in, Slack with one OAuth sign-in, then tell the agent what land extracted data as clean rows should look like once Slack is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Google Sheets to Slack automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Slack, the agent can weigh what arrived from Google Sheets, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Sheets and Slack data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Google Sheets, Slack and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Sheets and Slack run leave behind?
Every run is recorded end to end — the Google Sheets items examined, the decision and its reasoning, the resulting Slack write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
