Automate Linear + YouTube
Fast issue tracking that deserves fast automation. 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 Linear; point its last step at YouTube to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Linear side, works out what it means, and only then decides what — if anything — should happen in YouTube.
When an issue is created in Linear…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a status changes in Linear…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a cycle ends in Linear…
…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 issues with full context in Linear — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can update status and assignees in Linear — with the reasoning recorded in the run’s receipt.
Copy this Linear → YouTube workflow
Start with a custom-api call to api.linear.app and the youtube-api node. Configure the Linear source payload, the agent input, and the YouTube 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": "d892b3df-15ba-4bec-ae80-c9efab065b54",
"name": "Linear → YouTube",
"nodes": [
{
"id": "151d04d6-4121-400f-a6ee-9f8b78d845d6",
"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": "ab407919-4658-40f6-a5ee-3d7facb4f078",
"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 Linear item. Decide whether it warrants action in YouTube, 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": "e0ce5ae7-7576-4b1f-a15b-2dd0aca910e2",
"text": "Configure destination in YouTube",
"x": 512,
"y": 528,
"isEditing": false,
"type": "youtube-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "ADD_VIDEO_TO_PLAYLIST",
"playlistId": "CONFIGURE_PLAYLISTID"
},
"description": "Setup template for YouTube API. Interact with the YouTube API to manage videos, comments, playlists, and more. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "f3b9a8a0-3c27-43a8-a5fb-6c8090092188",
"start": {
"id": "151d04d6-4121-400f-a6ee-9f8b78d845d6",
"type": "output"
},
"end": {
"id": "ab407919-4658-40f6-a5ee-3d7facb4f078",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "579b9324-11ea-4a5f-ac66-a2f508971782",
"start": {
"id": "ab407919-4658-40f6-a5ee-3d7facb4f078",
"type": "output"
},
"end": {
"id": "e0ce5ae7-7576-4b1f-a15b-2dd0aca910e2",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure YouTube API
Interact with the YouTube API to manage videos, comments, playlists, and more.
- action — The action to perform on YouTube Current example:
ADD_VIDEO_TO_PLAYLIST. - playlistId — The ID of the playlist Current example:
CONFIGURE_PLAYLISTID.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Linear. 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
Build it in AGNT
- Download AGNT Community Core — free and local-first.
- Connect Linear with an API key pasted into the vault and YouTube with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and youtube-api onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Linear and what was written to YouTube.
Linear and YouTube — common questions
Can I connect Linear to YouTube without writing code?
Yes. Linear connects with an API key pasted into the vault and YouTube with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when an issue is created, pull transcripts and stats” — and the agent handles the rest.
How is this different from a field-mapping Linear to YouTube automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Linear item in full and decides — whether it matters, how to summarise it, and what belongs in YouTube. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Linear and YouTube data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Linear 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 Linear and YouTube run leave behind?
A receipt: what was read in Linear, which tools ran with which arguments, what the agent concluded, and what it wrote to YouTube. Anything consequential can sit behind an approval gate so a person signs off before it happens.
