Automate Slack + YouTube
Team chat where operations actually surface. 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.
Support First Responder is a ready-made agent built around Slack; point its last step at YouTube 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 Slack into YouTube.
When a message hits a channel in Slack…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a keyword or mention fires in Slack…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a reaction is added in Slack…
…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 post a rich channel message in Slack — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can DM a teammate in Slack — with the reasoning recorded in the run’s receipt.
Copy this Slack → YouTube workflow
Start with the slack-api node and the youtube-api node. Configure the Slack 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": "636ca6e0-631f-4781-ac71-3fd732c6429a",
"name": "Slack → YouTube",
"nodes": [
{
"id": "bf69f23b-2ba5-45fc-a5f1-422db931832c",
"text": "Watch Slack",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-slack-message",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"channelId": "CONFIGURE_CHANNELID"
},
"description": "Setup template for Receive Slack Message. Listen for incoming Slack messages in a specified channel and trigger the workflow when a new message is received. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "24cb3f5e-da3b-4561-a7ea-38d97310ece2",
"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 Slack 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": "933745c5-dae2-4a58-ad09-7151c89056cc",
"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": "24501dba-e435-4aa9-ad35-b6fb4d166bca",
"start": {
"id": "bf69f23b-2ba5-45fc-a5f1-422db931832c",
"type": "output"
},
"end": {
"id": "24cb3f5e-da3b-4561-a7ea-38d97310ece2",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "b07268fc-5ce6-4d01-a99d-01df9b4f18a6",
"start": {
"id": "24cb3f5e-da3b-4561-a7ea-38d97310ece2",
"type": "output"
},
"end": {
"id": "933745c5-dae2-4a58-ad09-7151c89056cc",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Receive Slack Message
Listen for incoming Slack messages in a specified channel and trigger the workflow when a new message is received.
- channelId — The ID of the Slack channel to monitor Current example:
CONFIGURE_CHANNELID.
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 Support First Responder
Support First Responder is a working agent built around Slack. 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
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Slack takes one OAuth sign-in, YouTube takes one OAuth sign-in.
- Configure the 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.
Slack and YouTube — common questions
Can I connect Slack to YouTube without writing code?
You can build it entirely from the canvas. Authorise Slack with one OAuth sign-in, YouTube with one OAuth sign-in, then tell the agent what pipe agent findings into the room where decisions happen 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 Slack to YouTube automation?
Mapping tools move data; this reasons about it. Rather than copying a field into YouTube, the agent can weigh what arrived from Slack, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Slack and YouTube data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Slack, YouTube and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Slack and YouTube run leave behind?
You get an auditable trail rather than a success flag. It shows the Slack 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.
