AI agents for Jira
The ticket system of record for engineering work. AGNT connects to Jira so agents can read what happens there, reason about it, and act — with a receipt for every run.
Meeting Follow-Through is a ready-made agent that works in Jira — free, and it runs on your machine.
Jira and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in Jira. |
|---|---|
| Connects with | Basic — held in the local vault |
| AGNT node | custom-api, or the zapier-action bridge |
| Runs when | An issue is created or transitions |
| Typical build time | Ten minutes |
| Where data goes | Nowhere by default — AGNT runs on your machine and credentials never leave it. |
What you can automate
Reacts when…
- an issue is created or transitions
- a sprint starts
- a priority changes
Agents can…
- create and update issues
- transition tickets with comments
- summarise sprint state
Teams use it for
- meeting actions become tickets automatically
- sprint summaries written from real board state
- incoming bugs enriched before triage
Build it: the Jira workflow
Design goal for Jira: meeting actions become tickets automatically; sprint summaries written from real board state; incoming bugs enriched before triage. The template below supplies configurable nodes, not the complete logic for those goals.
Use this Jira setup template to arrange the schedule, input review and API operation. Configure the account-specific fields and add your own decision and approval controls before activation.
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": "9238b104-23c0-4b5a-a470-77e8c14a8bf0",
"name": "Jira — read, decide, act",
"nodes": [
{
"id": "d504c3ba-03e6-4333-acab-ecf9e6855876",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "clock",
"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": "613afb84-3410-49ec-a54a-8d544aa8cbb4",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Decide what needs to happen in Jira. Explain your reasoning.\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": "b8a52a81-7793-446f-a188-6b0cb09e7562",
"text": "Call the Jira API",
"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",
"headers": "{}",
"query": ""
},
"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": "6fd92bb6-954d-4d6e-a341-f9600dfd6350",
"start": {
"id": "d504c3ba-03e6-4333-acab-ecf9e6855876",
"type": "output"
},
"end": {
"id": "613afb84-3410-49ec-a54a-8d544aa8cbb4",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "d2253d05-ee1e-4002-a4f5-cf57360e7a30",
"start": {
"id": "613afb84-3410-49ec-a54a-8d544aa8cbb4",
"type": "output"
},
"end": {
"id": "b8a52a81-7793-446f-a188-6b0cb09e7562",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}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 — it runs on Jira
Meeting Follow-Through is a working agent that uses Jira. Installing it drops the whole workflow onto your canvas — connected, editable, and yours to change.
Runs on your own machine · See what it does
Tickets are where decisions go to be forgotten
The gap in most Jira usage is not the board but everything around it: actions agreed in a meeting that never became tickets, bugs arriving without reproduction steps, sprint summaries written from memory. Those are all reading-and-writing jobs an agent handles well.
Enrichment before triage
A ticket that arrives with the relevant history, likely component and related past issues attached is far cheaper to triage. Doing that enrichment on creation means the human triage step starts from a briefed ticket rather than a title.
Jira without a first-party node
There is no first-party Jira node yet, and a page implying otherwise would cost you an afternoon. What works today is the generic custom-api node pointed at Jira’s own API, authenticating with basic.
| What you need | Value |
|---|---|
| Endpoint | https://{yoursite}.atlassian.net/rest/api/3/issue |
| Method | POST |
| Authentication | Basic |
| Header | Authorization: Basic base64({email}:{apiToken}) |
| Reference | Jira API documentation |
Worth knowing: Basic auth pairs your account email with an API token, never with your password.
One thing to know before you build
Basic auth pairs your account email with an API token, never with your password.
That single detail accounts for most of the time people lose on a first Jira build. With it out of the way the endpoint above is all you need, and the workflow below wires it up.
Connect Jira in two minutes
- Download AGNT Community Core — free, local-first, no account needed to run.
- Connect with one OAuth sign-in from AGNT’s vault — tokens are stored encrypted on your machine and never leave it.
- Drop the Jira node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
Jira + AGNT — common questions
Can agents create and transition issues?
Yes — creating with full context, updating fields and transitioning with an explanatory comment.
Can meeting actions become Jira tickets?
Yes, extracted from a transcript with owner and due date, linked back to where they were agreed.
Can it write sprint summaries?
Yes, from real board state rather than recollection.
