Automate GitHub + Google Sheets
Where the code — and half the process — lives. The database every team already has open. 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 Sheets to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Google Sheets is a decision about the GitHub event rather than a transcription of it.
When a PR opens or merges in GitHub…
…an agent can append and update rows in Google Sheets — after reading the context and deciding it should.
When an issue is filed in GitHub…
…an agent can read ranges for reporting in Google Sheets — after reading the context and deciding it should.
When a release is cut in GitHub…
…an agent can maintain a rolling dashboard tab in Google Sheets — after reading the context and deciding it should.
When a row is added or edited in Google Sheets…
…an agent can comment on PRs and issues in GitHub — with the reasoning recorded in the run’s receipt.
When a sheet crosses a threshold in Google Sheets…
…an agent can open issues with structured detail in GitHub — with the reasoning recorded in the run’s receipt.
When a schedule fires in Google Sheets…
…an agent can draft release notes in GitHub — with the reasoning recorded in the run’s receipt.
The GitHub and Google Sheets hand-off, setup template
Start with the github-api node and the google-sheets-api node. Configure the GitHub source payload, the agent input, and the Google Sheets 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": "4c7a6ff3-018c-4b8e-a0d4-ad75c1a8870c",
"name": "GitHub → Google Sheets",
"nodes": [
{
"id": "759bc7b8-389e-4e17-aa96-6edb155d59f2",
"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": "1c595c9c-1d17-4249-ab1c-53df767453c6",
"text": "Read GitHub",
"x": 512,
"y": 336,
"isEditing": false,
"type": "github-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_AUTHENTICATED_USER",
"owner": "CONFIGURE_OWNER",
"repo": "CONFIGURE_REPO"
},
"description": "Setup template for GitHub API. Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "56b564fb-0519-456d-a798-e158eabc2eae",
"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 GitHub item. Decide whether it warrants action in Google Sheets, 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": "e62376f6-9c9d-4cfa-acf9-0eeec489f204",
"text": "Configure destination in Google Sheets",
"x": 512,
"y": 720,
"isEditing": false,
"type": "google-sheets-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "Read",
"spreadsheetId": "CONFIGURE_SPREADSHEETID",
"range": "CONFIGURE_RANGE"
},
"description": "Setup template for Google Sheets API. Interact with Google Sheets to read, write, append, or clear data in a spreadsheet. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "e08a4858-0126-4034-a0fa-fcec179cdee4",
"start": {
"id": "759bc7b8-389e-4e17-aa96-6edb155d59f2",
"type": "output"
},
"end": {
"id": "1c595c9c-1d17-4249-ab1c-53df767453c6",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "5b28c19c-74cc-45d9-a221-a8fbb92d8832",
"start": {
"id": "1c595c9c-1d17-4249-ab1c-53df767453c6",
"type": "output"
},
"end": {
"id": "56b564fb-0519-456d-a798-e158eabc2eae",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "cf847d71-47b0-4dac-a7ba-c30b1322df78",
"start": {
"id": "56b564fb-0519-456d-a798-e158eabc2eae",
"type": "output"
},
"end": {
"id": "e62376f6-9c9d-4cfa-acf9-0eeec489f204",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure GitHub API
Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search.
- action — The action to perform on GitHub Current example:
GET_AUTHENTICATED_USER. - owner — The owner of the repository (not needed for account-level or search actions) Current example:
CONFIGURE_OWNER. - repo — The name of the repository (for CREATE_REPO: the name of the new repository) Current example:
CONFIGURE_REPO.
Configure Google Sheets API
Interact with Google Sheets to read, write, append, or clear data in a spreadsheet.
- operation — The operation to perform on the Google Sheet Current example:
Read. - spreadsheetId — The ID of the Google Sheet to interact with Current example:
CONFIGURE_SPREADSHEETID. - range — The range of cells to interact with (e.g., 'Sheet1!A1:B5') Current example:
CONFIGURE_RANGE.
Install First-Pass Reviewer
First-Pass Reviewer is a working agent built around GitHub. Install it, point its last step at Google Sheets, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring GitHub to Google Sheets
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Google Sheets (one OAuth sign-in) and GitHub (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; github-api does the reading and google-sheets-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
GitHub and Google Sheets — common questions
Can I connect GitHub to Google Sheets without writing code?
You can build it entirely from the canvas. Authorise GitHub with one OAuth sign-in, Google Sheets with one OAuth sign-in, then tell the agent what first-pass review on every diff should look like once Google Sheets 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 GitHub to Google Sheets automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the GitHub item in full and decides — whether it matters, how to summarise it, and what belongs in Google Sheets. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my GitHub and Google Sheets data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your GitHub or Google Sheets 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 GitHub and Google Sheets run leave behind?
A receipt: what was read in GitHub, which tools ran with which arguments, what the agent concluded, and what it wrote to Google Sheets. Anything consequential can sit behind an approval gate so a person signs off before it happens.
