Automate Google Calendar + Trello
The shared clock your workflows can read and write. Boards and cards — simple enough to automate deeply. 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 Trello to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Trello is a decision about the Google Calendar event rather than a transcription of it.
When an event starts or ends in Google Calendar…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can summarise a board in Trello — after reading the context and deciding it should.
When a card is created or moved in Trello…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
Google Calendar to Trello, setup template
Start with the google-calendar-api node and a custom-api call to api.trello.com. Configure the Google Calendar source payload, the agent input, and the Trello 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": "e777eddc-d509-40a9-a8ce-70810294ef16",
"name": "Google Calendar → Trello",
"nodes": [
{
"id": "a3adc1c2-4b49-4af6-ab9f-1b129919fcac",
"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": "1f141a0c-2bce-4289-a2df-5fef84077dce",
"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 Trello, 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": "d206fabe-250b-4c32-a210-e0e675bdd088",
"text": "Call Trello",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.trello.com/1/cards?key={key}&token={token}",
"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": "78589cf4-2586-4b31-a7d5-91fb42cd3eda",
"start": {
"id": "a3adc1c2-4b49-4af6-ab9f-1b129919fcac",
"type": "output"
},
"end": {
"id": "1f141a0c-2bce-4289-a2df-5fef84077dce",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "0d97b13b-4b77-4499-a0b8-de5288ba53d2",
"start": {
"id": "1f141a0c-2bce-4289-a2df-5fef84077dce",
"type": "output"
},
"end": {
"id": "d206fabe-250b-4c32-a210-e0e675bdd088",
"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:
https://api.trello.com/1/cards?key={key}&token={token}. - 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 Trello, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring Google Calendar to Trello
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Trello (an API key pasted into the vault) and Google Calendar (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; google-calendar-api does the reading and custom-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Google Calendar and Trello — common questions
Can I connect Google Calendar to Trello without writing code?
You can build it entirely from the canvas. Authorise Google Calendar with one OAuth sign-in, Trello with an API key pasted into the vault, then tell the agent what prep briefings before every meeting should look like once Trello 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 Trello 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 Trello with the reasoning recorded.
Does my Google Calendar and Trello data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Calendar or Trello 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 Trello 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 email requests become cards instantly, and the exact change applied in Trello, with approvals attached where you required them.
