Automate Discord + YouTube
Community chat with an automation-friendly API. 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 Discord; point its last step at YouTube to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Discord side, works out what it means, and only then decides what — if anything — should happen in YouTube.
When a message posts in a channel in Discord…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a member joins in Discord…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a keyword appears in Discord…
…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 channel messages in Discord — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can DM members in Discord — with the reasoning recorded in the run’s receipt.
Copy this Discord → YouTube workflow
Start with the discord-api node and the youtube-api node. Configure the Discord 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": "e1b0788a-7789-499b-a801-43b7a47cfe26",
"name": "Discord → YouTube",
"nodes": [
{
"id": "37df58dc-23d3-48b8-a321-4666394f1ca4",
"text": "Watch Discord",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-discord-message",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"channelId": "CONFIGURE_CHANNELID"
},
"description": "Setup template for Receive Discord Message. Listen for incoming Discord 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": "ad4fc7c8-cfad-4004-a3b5-7dba5f799658",
"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 Discord 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": "1beee6a9-8fef-4cfc-a152-dcf17ddf6648",
"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": "a25b2e27-864d-45cd-ad38-eb0ecbe8140a",
"start": {
"id": "37df58dc-23d3-48b8-a321-4666394f1ca4",
"type": "output"
},
"end": {
"id": "ad4fc7c8-cfad-4004-a3b5-7dba5f799658",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "392f0ff6-ee33-4bb2-af93-dbcedc097928",
"start": {
"id": "ad4fc7c8-cfad-4004-a3b5-7dba5f799658",
"type": "output"
},
"end": {
"id": "1beee6a9-8fef-4cfc-a152-dcf17ddf6648",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}
Configure Receive Discord Message
Listen for incoming Discord messages in a specified channel and trigger the workflow when a new message is received.
- channelId — The ID of the Discord 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 Discord. 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
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise YouTube (one OAuth sign-in) and Discord (an API key pasted into the vault). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; discord-api does the reading and youtube-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Discord and YouTube — common questions
Can I connect Discord to YouTube without writing code?
Yes. Discord 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 a message posts in a channel, pull transcripts and stats” — and the agent handles the rest.
How is this different from a field-mapping Discord to YouTube automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles community questions answered from your docs the way a colleague would — reading the Discord context, judging it, then writing to YouTube with the reasoning recorded.
Does my Discord and YouTube data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Discord 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 Discord and YouTube run leave behind?
A receipt: what was read in Discord, 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.