Automate GitHub + Google Calendar
Where the code — and half the process — lives. The shared clock your workflows can read and write. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
First-Pass Reviewer is a ready-made agent built around GitHub; point its last step at Google Calendar to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Google Calendar is a decision about the GitHub event rather than a transcription of it.
When a PR opens or merges in GitHub…
…an agent can create or move events in Google Calendar — after reading the context and deciding it should.
When an issue is filed in GitHub…
…an agent can add agendas to invites in Google Calendar — after reading the context and deciding it should.
When a release is cut in GitHub…
…an agent can block focus time in Google Calendar — after reading the context and deciding it should.
When an event starts or ends in Google Calendar…
…an agent can comment on PRs and issues in GitHub — with the reasoning recorded in the run’s receipt.
When a meeting is created in Google Calendar…
…an agent can open issues with structured detail in GitHub — with the reasoning recorded in the run’s receipt.
When a day begins in Google Calendar…
…an agent can draft release notes in GitHub — with the reasoning recorded in the run’s receipt.
The GitHub and Google Calendar hand-off, in full
GitHub is reached through the github-api node and Google Calendar through the google-calendar-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": "0867cf94-dda2-492c-a803-ed1e75eecd20",
"name": "GitHub → Google Calendar",
"nodes": [
{
"id": "958b069d-97a6-4457-a24a-0d569a0bf53e",
"text": "Watch GitHub",
"x": 512,
"y": 144,
"isEditing": false,
"type": "github-api",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "292923d6-2511-422a-a55d-7d2edf23c4dc",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the GitHub item. Decide whether it warrants action in Google Calendar, and explain why."
},
"description": "Decides whether this GitHub item warrants anything in Google Calendar.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b0fcadce-434f-4872-a420-191e7fd35464",
"text": "Act in Google Calendar",
"x": 512,
"y": 528,
"isEditing": false,
"type": "google-calendar-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_EVENTS"
},
"description": "Interact with Google Calendar to manage events, check availability, and create Google Meet meetings.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "b2dd44df-5cf6-4055-ab34-25d4f11d91da",
"start": {
"id": "958b069d-97a6-4457-a24a-0d569a0bf53e",
"type": "output"
},
"end": {
"id": "292923d6-2511-422a-a55d-7d2edf23c4dc",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2d75b75a-7bab-437b-a276-f0b332e61eba",
"start": {
"id": "292923d6-2511-422a-a55d-7d2edf23c4dc",
"type": "output"
},
"end": {
"id": "b0fcadce-434f-4872-a420-191e7fd35464",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install First-Pass Reviewer
First-Pass Reviewer is a working agent built around GitHub. Install it, point its last step at Google Calendar, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — GitHub takes one OAuth sign-in, Google Calendar 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 Google Calendar.
GitHub and Google Calendar — common questions
Can I connect GitHub to Google Calendar without writing code?
No code is required. Add both connections in the vault (GitHub uses one OAuth sign-in, Google Calendar uses one OAuth sign-in), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping GitHub to Google Calendar automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Google Calendar, the agent can weigh what arrived from GitHub, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my GitHub and Google Calendar data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: GitHub, Google Calendar, and your chosen model provider — which can be a local one.
What does a GitHub and Google Calendar run leave behind?
Every run is recorded end to end — the GitHub items examined, the decision and its reasoning, the resulting Google Calendar write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
