Automate Jira + Notion
The ticket system of record for engineering work. The team wiki agents can actually keep current. 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 Jira and Notion — 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 Jira into Notion.
When an issue is created or transitions in Jira…
…an agent can create and update pages in Notion — after reading the context and deciding it should.
When a sprint starts in Jira…
…an agent can write database rows in Notion — after reading the context and deciding it should.
When a priority changes in Jira…
…an agent can append meeting notes in Notion — after reading the context and deciding it should.
When a page is created or edited in Notion…
…an agent can create and update issues in Jira — with the reasoning recorded in the run’s receipt.
When a database row changes in Notion…
…an agent can transition tickets with comments in Jira — with the reasoning recorded in the run’s receipt.
When a status flips in Notion…
…an agent can summarise sprint state in Jira — with the reasoning recorded in the run’s receipt.
Copy this Jira → Notion workflow
Start with a custom-api call to {yoursite}.atlassian.net and the notion-api node. Configure the Jira source payload, the agent input, and the Notion 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": "ff46ffe3-2cbe-449b-ac99-cc7c3baf270a",
"name": "Jira → Notion",
"nodes": [
{
"id": "a907555f-e903-47b3-a0ce-56dc06ecf292",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "14a2769b-1bb2-4229-a1ad-f3b4fc95576e",
"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 Jira item. Decide whether it warrants action in Notion, 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": "da4d0493-a551-48f2-ae99-becd9d4fe084",
"text": "Configure destination in Notion",
"x": 512,
"y": 528,
"isEditing": false,
"type": "notion-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "search",
"pageSize": 1,
"query": "CONFIGURE_QUERY",
"filterType": "all"
},
"description": "Setup template for Notion API. Interact with Notion - search, query databases, get pages, and create pages. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "f51751ee-94ff-42ef-a090-b60931148526",
"start": {
"id": "a907555f-e903-47b3-a0ce-56dc06ecf292",
"type": "output"
},
"end": {
"id": "14a2769b-1bb2-4229-a1ad-f3b4fc95576e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "84778dbd-ccec-45ca-aaed-398d50bce730",
"start": {
"id": "14a2769b-1bb2-4229-a1ad-f3b4fc95576e",
"type": "output"
},
"end": {
"id": "da4d0493-a551-48f2-ae99-becd9d4fe084",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Notion API
Interact with Notion - search, query databases, get pages, and create pages.
- operation — Operation to perform Current example:
search. - query — Search query text Current example:
CONFIGURE_QUERY. - filterType — Filter results by type Current example:
all. - pageSize — Max results (default: 10-100) Current example:
1.
Install Meeting Follow-Through
Meeting Follow-Through already uses both Jira and Notion, 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
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Jira takes one OAuth sign-in, Notion takes one OAuth sign-in.
- Configure the nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Notion.
Jira and Notion — common questions
Can I connect Jira to Notion without writing code?
Yes. Jira connects with one OAuth sign-in and Notion with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when an issue is created or transitions, create and update pages” — and the agent handles the rest.
How is this different from a field-mapping Jira to Notion automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Jira item in full and decides — whether it matters, how to summarise it, and what belongs in Notion. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Jira and Notion 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: Jira, Notion, and your chosen model provider — which can be a local one.
What does a Jira and Notion run leave behind?
You get an auditable trail rather than a success flag. It shows the Jira context the agent worked from, the judgment it made about meeting notes filed where they belong, and the exact change applied in Notion, with approvals attached where you required them.
