Automate Google Calendar + PostgreSQL
The shared clock your workflows can read and write. The production database your reports should come from. 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 PostgreSQL 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 PostgreSQL.
When an event starts or ends in Google Calendar…
…an agent can run parameterised queries in PostgreSQL — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can write validated rows in PostgreSQL — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can produce report extracts in PostgreSQL — after reading the context and deciding it should.
When a scheduled query runs in PostgreSQL…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a threshold is crossed in PostgreSQL…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and PostgreSQL hand-off, setup template
Start with the google-calendar-api node and a custom-api call to {host}:5432. Configure the Google Calendar source payload, the agent input, and the PostgreSQL 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": "6c9b536c-0e1d-4af9-abac-229571aecd22",
"name": "Google Calendar → PostgreSQL",
"nodes": [
{
"id": "9c485724-dc80-428a-a670-6b9ca0dade14",
"text": "Watch Google Calendar",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"calendarId": "CONFIGURE_CALENDARID"
},
"description": "Setup template for Google Calendar New Event. Listen for events created or updated on a Google Calendar and trigger the workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "0a578f34-4cdc-4120-aaab-f3a058223d18",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Calendar item. Decide whether it warrants action in PostgreSQL, 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": "bc1799a6-ac68-450c-a289-c31cd47a5910",
"text": "Call PostgreSQL",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "postgresql://{user}:{password}@{host}:5432/{database}",
"method": "GET",
"authType": "None",
"query": "",
"headers": "{}"
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "79b0a3f7-d26f-45f5-a6fd-2e14df825e32",
"start": {
"id": "9c485724-dc80-428a-a670-6b9ca0dade14",
"type": "output"
},
"end": {
"id": "0a578f34-4cdc-4120-aaab-f3a058223d18",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "0cccfd87-45c7-4d9c-a8be-2f51bfd91520",
"start": {
"id": "0a578f34-4cdc-4120-aaab-f3a058223d18",
"type": "output"
},
"end": {
"id": "bc1799a6-ac68-450c-a289-c31cd47a5910",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Calendar New Event
Listen for events created or updated on a Google Calendar and trigger the workflow.
- calendarId — Calendar ID to monitor (defaults to 'primary') Current example:
CONFIGURE_CALENDARID.
Configure Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
postgresql://{user}:{password}@{host}:5432/{database}. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at PostgreSQL, 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
- Download AGNT Community Core — free and local-first.
- Connect Google Calendar with one OAuth sign-in and PostgreSQL with a local endpoint on your own machine; both land in the local vault.
- Start from a marketplace workflow, or drop google-calendar-api and a custom-api node 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 Calendar and what was written to PostgreSQL.
Google Calendar and PostgreSQL — common questions
Can I connect Google Calendar to PostgreSQL without writing code?
No code is required. Add both connections in the vault (Google Calendar uses one OAuth sign-in, PostgreSQL uses a local endpoint on your own machine), 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 Google Calendar to PostgreSQL automation?
Mapping tools move data; this reasons about it. Rather than copying a field into PostgreSQL, the agent can weigh what arrived from Google Calendar, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Calendar and PostgreSQL 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 Calendar, PostgreSQL and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Calendar and PostgreSQL run leave behind?
A receipt: what was read in Google Calendar, which tools ran with which arguments, what the agent concluded, and what it wrote to PostgreSQL. Anything consequential can sit behind an approval gate so a person signs off before it happens.
