Automate Google Calendar + Slack
The shared clock your workflows can read and write. 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.
Meeting Follow-Through is a ready-made agent built around Google Calendar; point its last step at Slack to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Google Calendar side, works out what it means, and only then decides what — if anything — should happen in Slack.
When an event starts or ends in Google Calendar…
…an agent can post a rich channel message in Slack — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can DM a teammate in Slack — after reading the context and deciding it should.
When a day begins in Google Calendar…
…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 create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a keyword or mention fires in Slack…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a reaction is added in Slack…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and Slack hand-off, in full
The two ends are the google-calendar-api node and the slack-api node. What makes this different from a zap is the middle node — it forms a view about the Google Calendar item before anything reaches Slack.
{
"id": "f2d1b0d8-2d61-444b-ad90-fbb1e266dd6e",
"name": "Google Calendar → Slack",
"nodes": [
{
"id": "11f62f63-8944-4614-a7fc-cdaf29c82c58",
"text": "Watch Google Calendar",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for events created or updated on a Google Calendar and trigger the workflow.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "8a3d894c-1c04-4207-a5a2-5c55e11b3bfe",
"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 Calendar item. Decide whether it warrants action in Slack, and explain why."
},
"description": "Decides whether this Google Calendar item warrants anything in Slack.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "fe5702d2-b531-4082-aa99-4a587bbfe0a0",
"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": "248cdd3f-9a61-4941-abf3-8ae485d4fe32",
"start": {
"id": "11f62f63-8944-4614-a7fc-cdaf29c82c58",
"type": "output"
},
"end": {
"id": "8a3d894c-1c04-4207-a5a2-5c55e11b3bfe",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "ccd6b7d9-3d3e-41a6-a0d2-9fb1f3b2c5e4",
"start": {
"id": "8a3d894c-1c04-4207-a5a2-5c55e11b3bfe",
"type": "output"
},
"end": {
"id": "fe5702d2-b531-4082-aa99-4a587bbfe0a0",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at Slack, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Build it in AGNT
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Calendar takes one OAuth sign-in, Slack takes one OAuth sign-in.
- Build the three nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Slack.
Google Calendar and Slack — common questions
Can I connect Google Calendar to Slack without writing code?
You can build it entirely from the canvas. Authorise Google Calendar with one OAuth sign-in, Slack with one OAuth sign-in, then tell the agent what prep briefings before every meeting 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 Calendar to Slack automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles prep briefings before every meeting the way a colleague would — reading the Google Calendar context, judging it, then writing to Slack with the reasoning recorded.
Does my Google Calendar and Slack data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Calendar 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 Calendar and Slack run leave behind?
You get an auditable trail rather than a success flag. It shows the Google Calendar context the agent worked from, the judgment it made about pipe agent findings into the room where decisions happen, and the exact change applied in Slack, with approvals attached where you required them.
