Automate Google Calendar + X (Twitter)
The shared clock your workflows can read and write. The feed where your market thinks out loud. 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 X (Twitter) to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches X (Twitter) 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 post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can collect engagement metrics in X (Twitter) — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a mention or keyword appears in X (Twitter)…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a schedule fires in X (Twitter)…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
Google Calendar to X (Twitter), in three nodes
Concretely: the google-calendar-api node on one side, the twitter-api node on the other, and an agent in between that can decline. Deciding not to write into X (Twitter) is a recorded outcome, not a silent one.
{
"id": "1827829d-7ed0-475b-ab62-815afb9d38fe",
"name": "Google Calendar → X (Twitter)",
"nodes": [
{
"id": "3313ebff-52f5-4206-a571-0b19dcfd7264",
"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": "a2f48240-52af-45e7-a96f-99bf291ae4da",
"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 X (Twitter), and explain why."
},
"description": "Decides whether this Google Calendar item warrants anything in X (Twitter).",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "1f7b4d43-f63c-4d7e-a139-618b9ef8655c",
"text": "Act in X (Twitter)",
"x": 512,
"y": 528,
"isEditing": false,
"type": "twitter-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "POST"
},
"description": "Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "439f27bc-a7bf-438f-a280-fc2fdea8a436",
"start": {
"id": "3313ebff-52f5-4206-a571-0b19dcfd7264",
"type": "output"
},
"end": {
"id": "a2f48240-52af-45e7-a96f-99bf291ae4da",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "e530e032-5c5d-493a-adbc-4634f25f1930",
"start": {
"id": "a2f48240-52af-45e7-a96f-99bf291ae4da",
"type": "output"
},
"end": {
"id": "1f7b4d43-f63c-4d7e-a139-618b9ef8655c",
"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 X (Twitter), 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
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise X (Twitter) (one OAuth sign-in) 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 twitter-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 X (Twitter) — common questions
Can I connect Google Calendar to X (Twitter) without writing code?
No code is required. Add both connections in the vault (Google Calendar uses one OAuth sign-in, X (Twitter) 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 Google Calendar to X (Twitter) automation?
Mapping tools move data; this reasons about it. Rather than copying a field into X (Twitter), 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 X (Twitter) 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, X (Twitter) and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Calendar and X (Twitter) run leave behind?
Every run is recorded end to end — the Google Calendar items examined, the decision and its reasoning, the resulting X (Twitter) write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
