Automate Telegram + YouTube
The fastest channel between your agents and your phone. 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.
Social Scheduler is a ready-made agent built around Telegram; 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 Telegram event rather than a transcription of it.
When a message arrives in Telegram…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a command is sent in Telegram…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a schedule fires in Telegram…
…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 send messages and alerts in Telegram — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can reply to commands in Telegram — with the reasoning recorded in the run’s receipt.
Telegram to YouTube, in three nodes
The two ends are the telegram-api node and the youtube-api node. What makes this different from a zap is the middle node — it forms a view about the Telegram item before anything reaches YouTube.
{
"id": "a4d30da9-2ef5-43dc-ac23-f93d94a3bd88",
"name": "Telegram → YouTube",
"nodes": [
{
"id": "39872e37-782a-4473-a4f4-bbc00d39c3ae",
"text": "Watch Telegram",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-telegram-update",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for incoming Telegram bot messages, commands, channel posts, and inline keyboard callback button clicks using long polling.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "c440ca83-5937-4024-a26c-eaeb3bd71aa8",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Telegram item. Decide whether it warrants action in YouTube, and explain why."
},
"description": "Decides whether this Telegram item warrants anything in YouTube.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "58afc486-dec5-429b-a518-1f95cb3a796e",
"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": "5f42d9ca-992d-4c7c-ada6-d72e574b60b0",
"start": {
"id": "39872e37-782a-4473-a4f4-bbc00d39c3ae",
"type": "output"
},
"end": {
"id": "c440ca83-5937-4024-a26c-eaeb3bd71aa8",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "cd6ae1ed-9824-4c4f-ae55-5e520b31af1a",
"start": {
"id": "c440ca83-5937-4024-a26c-eaeb3bd71aa8",
"type": "output"
},
"end": {
"id": "58afc486-dec5-429b-a518-1f95cb3a796e",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Social Scheduler
Social Scheduler is a working agent built around Telegram. 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 Telegram (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; telegram-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.
Telegram and YouTube — common questions
Can I connect Telegram to YouTube without writing code?
You can build it entirely from the canvas. Authorise Telegram with an API key pasted into the vault, YouTube with one OAuth sign-in, then tell the agent what approve agent actions from anywhere 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 Telegram to YouTube automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Telegram 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 Telegram and YouTube data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Telegram 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 Telegram and YouTube run leave behind?
A receipt: what was read in Telegram, 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.
