Automate Jira + YouTube
The ticket system of record for engineering work. Long-form content worth repurposing everywhere else. 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 YouTube to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches YouTube is a decision about the Jira event rather than a transcription of it.
When an issue is created or transitions in Jira…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a sprint starts in Jira…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a priority changes in Jira…
…an agent can summarise comments in YouTube — after reading the context and deciding it should.
When a video is published in YouTube…
…an agent can create and update issues in Jira — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can transition tickets with comments in Jira — with the reasoning recorded in the run’s receipt.
Copy this Jira → YouTube workflow
Jira is reached through a custom-api call to {yoursite}.atlassian.net and YouTube through the youtube-api node. Between them sits the agent, which is the part a field-mapping tool cannot do: it reads the item and decides whether the hand-off is warranted at all.
{
"id": "d241a1c7-7696-4bfc-ac39-917b6e6aadcc",
"name": "Jira → YouTube",
"nodes": [
{
"id": "7db742ca-d173-4008-ad93-4c44f7f13c64",
"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": "e6848237-93aa-4eb7-ad17-fbae4af9e3aa",
"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 YouTube, and explain why."
},
"description": "Decides whether this Jira item warrants anything in YouTube.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "54048e43-6ecc-4430-aec8-64836666d47c",
"text": "Act in YouTube",
"x": 512,
"y": 528,
"isEditing": false,
"type": "youtube-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "ADD_VIDEO_TO_PLAYLIST"
},
"description": "Interact with the YouTube API to manage videos, comments, playlists, and more.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "80db0ffa-d3dc-4f8d-ab2e-74230a6be83a",
"start": {
"id": "7db742ca-d173-4008-ad93-4c44f7f13c64",
"type": "output"
},
"end": {
"id": "e6848237-93aa-4eb7-ad17-fbae4af9e3aa",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "213fac8a-8190-4b06-a319-006843bcfde8",
"start": {
"id": "e6848237-93aa-4eb7-ad17-fbae4af9e3aa",
"type": "output"
},
"end": {
"id": "54048e43-6ecc-4430-aec8-64836666d47c",
"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 YouTube, and you have this hand-off without building it from an empty canvas.
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, YouTube takes one OAuth sign-in.
- Build the three 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 YouTube.
Jira and YouTube — common questions
Can I connect Jira to YouTube without writing code?
You can build it entirely from the canvas. Authorise Jira with one OAuth sign-in, YouTube with one OAuth sign-in, then tell the agent what meeting actions become tickets automatically should look like once YouTube 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 YouTube automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles meeting actions become tickets automatically the way a colleague would — reading the Jira context, judging it, then writing to YouTube with the reasoning recorded.
Does my Jira and YouTube data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Jira or YouTube 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 YouTube 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 videos become posts, threads and newsletters, and the exact change applied in YouTube, with approvals attached where you required them.
