Automate Google Calendar + Linear
The shared clock your workflows can read and write. Fast issue tracking that deserves fast automation. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Meeting Follow-Through already works across Google Calendar and Linear — free, and it runs on your machine.
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 Linear.
When an event starts or ends in Google Calendar…
…an agent can create issues with full context in Linear — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can update status and assignees in Linear — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can write cycle summaries in Linear — after reading the context and deciding it should.
When an issue is created in Linear…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a status changes in Linear…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a cycle ends in Linear…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
Copy this Google Calendar → Linear workflow
Start with the google-calendar-api node and a custom-api call to api.linear.app. Configure the Google Calendar source payload, the agent input, and the Linear 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": "47bbd59f-0f31-47ea-af7d-37b3e7b7b160",
"name": "Google Calendar → Linear",
"nodes": [
{
"id": "656f35d7-ae9c-4b95-a8c2-d23e2f39421e",
"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": "f64fd315-f2ab-45f0-ac7b-a7cb62796d24",
"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 Linear, 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": "47b9b5d3-258c-4e67-a0d8-70104461276a",
"text": "Call Linear",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.linear.app/graphql",
"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": "406a877e-8940-4f9a-a4dc-f5ac57beadcc",
"start": {
"id": "656f35d7-ae9c-4b95-a8c2-d23e2f39421e",
"type": "output"
},
"end": {
"id": "f64fd315-f2ab-45f0-ac7b-a7cb62796d24",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "bd02395a-b9de-4e64-ad98-838807421838",
"start": {
"id": "f64fd315-f2ab-45f0-ac7b-a7cb62796d24",
"type": "output"
},
"end": {
"id": "47b9b5d3-258c-4e67-a0d8-70104461276a",
"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.linear.app/graphql. - 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 already uses both Google Calendar and Linear, so installing it gives you this exact hand-off wired up — connected, editable, and running on your own machine.
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 Linear (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 Linear — common questions
Can I connect Google Calendar to Linear without writing code?
You can build it entirely from the canvas. Authorise Google Calendar with one OAuth sign-in, Linear with an API key pasted into the vault, then tell the agent what prep briefings before every meeting should look like once Linear 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 Linear automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Google Calendar item in full and decides — whether it matters, how to summarise it, and what belongs in Linear. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Google Calendar and Linear data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Calendar or Linear 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 Linear 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 Linear. Anything consequential can sit behind an approval gate so a person signs off before it happens.
