Automate Google Calendar + Jira
The shared clock your workflows can read and write. The ticket system of record for engineering work. 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 Jira — free, and it runs on your machine.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Google Calendar into Jira.
When an event starts or ends in Google Calendar…
…an agent can create and update issues in Jira — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can transition tickets with comments in Jira — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can summarise sprint state in Jira — after reading the context and deciding it should.
When an issue is created or transitions in Jira…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a sprint starts in Jira…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a priority changes in Jira…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
Google Calendar to Jira, setup template
Start with the google-calendar-api node and a custom-api call to {yoursite}.atlassian.net. Configure the Google Calendar source payload, the agent input, and the Jira 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": "4a6b9d76-134d-43e5-a156-ca0746b42c36",
"name": "Google Calendar → Jira",
"nodes": [
{
"id": "3056e175-152b-41a2-a408-950fc5f5efd8",
"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": "96ecb0be-9ed1-4c85-a7eb-9d17bbfc79ce",
"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 Jira, 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": "04a65b91-f413-431b-ab83-3ebabd3e5092",
"text": "Call Jira",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://{yoursite}.atlassian.net/rest/api/3/issue",
"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": "53191597-1bb3-47b2-af2b-e7ad896377ec",
"start": {
"id": "3056e175-152b-41a2-a408-950fc5f5efd8",
"type": "output"
},
"end": {
"id": "96ecb0be-9ed1-4c85-a7eb-9d17bbfc79ce",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "e2adc4dd-85f7-472e-ac71-becd1d8b675c",
"start": {
"id": "96ecb0be-9ed1-4c85-a7eb-9d17bbfc79ce",
"type": "output"
},
"end": {
"id": "04a65b91-f413-431b-ab83-3ebabd3e5092",
"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://{yoursite}.atlassian.net/rest/api/3/issue. - 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 Jira, 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 Jira (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 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 Jira — common questions
Can I connect Google Calendar to Jira without writing code?
No code is required. Add both connections in the vault (Google Calendar uses one OAuth sign-in, Jira 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 Jira 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 Jira. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Google Calendar and Jira data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Google Calendar, Jira, and your chosen model provider — which can be a local one.
What does a Google Calendar and Jira run leave behind?
Every run is recorded end to end — the Google Calendar items examined, the decision and its reasoning, the resulting Jira write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
