Automate Jira + Telegram
The ticket system of record for engineering work. The fastest channel between your agents and your phone. 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 Telegram 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 Telegram.
When an issue is created or transitions in Jira…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a sprint starts in Jira…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a priority changes in Jira…
…an agent can deliver files and reports in Telegram — after reading the context and deciding it should.
When a message arrives in Telegram…
…an agent can create and update issues in Jira — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can transition tickets with comments in Jira — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can summarise sprint state in Jira — with the reasoning recorded in the run’s receipt.
Copy this Jira → Telegram workflow
Concretely: a custom-api call to {yoursite}.atlassian.net on one side, the telegram-api node on the other, and an agent in between that can decline. Deciding not to write into Telegram is a recorded outcome, not a silent one.
{
"id": "88322162-7224-4a3f-a981-90396f3395ca",
"name": "Jira → Telegram",
"nodes": [
{
"id": "dd65213d-c78a-45ff-a406-4e36e405849a",
"text": "Poll Jira",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"interval": "15",
"unit": "minutes"
},
"description": "Checks Jira on a schedule.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "48337ad3-1670-4faf-a712-33b65d5bc426",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Jira item. Decide whether it warrants action in Telegram, and explain why."
},
"description": "Decides whether this Jira item warrants anything in Telegram.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b2eb6166-bd97-4b52-ac99-5bfc6127f320",
"text": "Act in Telegram",
"x": 512,
"y": 528,
"isEditing": false,
"type": "telegram-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_ME"
},
"description": "Use Telegram Bot API from a single AGNT node. Choose an action to validate a bot, send messages/media, edit/delete messages, download files, or call any raw Bot API method.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "c93d5e63-e289-4257-a6ba-b94c6d8c2332",
"start": {
"id": "dd65213d-c78a-45ff-a406-4e36e405849a",
"type": "output"
},
"end": {
"id": "48337ad3-1670-4faf-a712-33b65d5bc426",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "5980e1a2-0553-41a2-a110-5138552d25f4",
"start": {
"id": "48337ad3-1670-4faf-a712-33b65d5bc426",
"type": "output"
},
"end": {
"id": "b2eb6166-bd97-4b52-ac99-5bfc6127f320",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Jira. Install it, point its last step at Telegram, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Build it in AGNT
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Telegram (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 telegram-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 Telegram — common questions
Can I connect Jira to Telegram without writing code?
No code is required. Add both connections in the vault (Jira uses one OAuth sign-in, Telegram uses an API key pasted into the vault), 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 Jira to Telegram 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 Telegram. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Jira and Telegram 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, Telegram, and your chosen model provider — which can be a local one.
What does a Jira and Telegram 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 Telegram. Anything consequential can sit behind an approval gate so a person signs off before it happens.
