Automate Jira + Trello
The ticket system of record for engineering work. Boards and cards — simple enough to automate deeply. 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 Jira; point its last step at Trello to finish this hand-off.
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 Trello.
When an issue is created or transitions in Jira…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When a sprint starts in Jira…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a priority changes in Jira…
…an agent can summarise a board in Trello — after reading the context and deciding it should.
When a card is created or moved in Trello…
…an agent can create and update issues in Jira — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can transition tickets with comments in Jira — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can summarise sprint state in Jira — with the reasoning recorded in the run’s receipt.
Jira to Trello, setup template
Start with a custom-api call to {yoursite}.atlassian.net and a custom-api call to api.trello.com. Configure the Jira source payload, the agent input, and the Trello 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": "ab20b380-a0bc-4cb6-a30e-9f066afef214",
"name": "Jira → Trello",
"nodes": [
{
"id": "cbed4d31-bf3f-4b5d-a84c-a4167032de7e",
"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": "53470cd2-fa68-436f-ac86-e359ffa7c246",
"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 Trello, 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": "a1d52590-acbf-4d87-a8b4-42b50570d02e",
"text": "Call Trello",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.trello.com/1/cards?key={key}&token={token}",
"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": "de82cb4f-31d2-48fe-a650-d51d4720fae8",
"start": {
"id": "cbed4d31-bf3f-4b5d-a84c-a4167032de7e",
"type": "output"
},
"end": {
"id": "53470cd2-fa68-436f-ac86-e359ffa7c246",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "4588c56f-c291-4105-a6e7-28268b1a544e",
"start": {
"id": "53470cd2-fa68-436f-ac86-e359ffa7c246",
"type": "output"
},
"end": {
"id": "a1d52590-acbf-4d87-a8b4-42b50570d02e",
"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://api.trello.com/1/cards?key={key}&token={token}. - 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 is a working agent built around Jira. Install it, point its last step at Trello, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring Jira to Trello
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Trello (an API key pasted into the vault) and Jira (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; custom-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.
Jira and Trello — common questions
Can I connect Jira to Trello without writing code?
You can build it entirely from the canvas. Authorise Jira with one OAuth sign-in, Trello with an API key pasted into the vault, then tell the agent what meeting actions become tickets automatically should look like once Trello 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 Jira to Trello 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 Trello. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Jira and Trello data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Jira or Trello 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 Jira and Trello run leave behind?
A receipt: what was read in Jira, which tools ran with which arguments, what the agent concluded, and what it wrote to Trello. Anything consequential can sit behind an approval gate so a person signs off before it happens.
