Automate Telegram + X (Twitter)
The fastest channel between your agents and your phone. The feed where your market thinks out loud. 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 X (Twitter) to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches X (Twitter) is a decision about the Telegram event rather than a transcription of it.
When a message arrives in Telegram…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a command is sent in Telegram…
…an agent can collect engagement metrics in X (Twitter) — after reading the context and deciding it should.
When a schedule fires in Telegram…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a mention or keyword appears in X (Twitter)…
…an agent can send messages and alerts in Telegram — with the reasoning recorded in the run’s receipt.
When a schedule fires in X (Twitter)…
…an agent can reply to commands in Telegram — with the reasoning recorded in the run’s receipt.
The Telegram and X (Twitter) hand-off, setup template
Start with the telegram-api node and the twitter-api node. Configure the Telegram source payload, the agent input, and the X (Twitter) 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": "4e5b26c4-0f67-4fd1-adb8-4d61a2ac4a96",
"name": "Telegram → X (Twitter)",
"nodes": [
{
"id": "8e72bc00-b648-48de-a436-78c0dec6aa50",
"text": "Watch Telegram",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-telegram-update",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"botToken": "CONFIGURE_BOTTOKEN",
"apiBaseUrl": "CONFIGURE_APIBASEURL",
"updateTypes": "messages_and_buttons",
"chatFilter": "CONFIGURE_CHATFILTER",
"commandFilter": "CONFIGURE_COMMANDFILTER",
"ignoreBotMessages": false,
"dropPendingUpdatesOnStart": false,
"deleteWebhookOnStart": false,
"pollTimeoutSeconds": 1,
"pollIntervalMs": 1,
"limit": 1,
"includeRaw": false
},
"description": "Setup template for Receive Telegram Update. Listen for incoming Telegram bot messages, commands, channel posts, and inline keyboard callback button clicks using long polling. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "f7850cb3-45fb-4b25-a0fa-bf8e70c2e412",
"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 Telegram item. Decide whether it warrants action in X (Twitter), 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": "b7d52c0d-336e-4a8c-a713-e8c9d96ce8ec",
"text": "Configure destination in X (Twitter)",
"x": 512,
"y": 528,
"isEditing": false,
"type": "twitter-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "POST",
"text": "CONFIGURE_TEXT"
},
"description": "Setup template for X (Twitter) API. Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "ddcda96c-0d68-4a57-a8d0-787b30ff09a6",
"start": {
"id": "8e72bc00-b648-48de-a436-78c0dec6aa50",
"type": "output"
},
"end": {
"id": "f7850cb3-45fb-4b25-a0fa-bf8e70c2e412",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "671e2730-387b-4d70-a736-cb7c161de5bc",
"start": {
"id": "f7850cb3-45fb-4b25-a0fa-bf8e70c2e412",
"type": "output"
},
"end": {
"id": "b7d52c0d-336e-4a8c-a713-e8c9d96ce8ec",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Receive Telegram Update
Listen for incoming Telegram bot messages, commands, channel posts, and inline keyboard callback button clicks using long polling.
- botToken — Optional fallback Telegram bot token from @BotFather. If omitted, AGNT uses the connected Telegram provider token from Settings → Connections. Current example:
CONFIGURE_BOTTOKEN. - apiBaseUrl — Optional Bot API base URL. Use https://api.telegram.org by default, or a local Bot API server URL. Current example:
CONFIGURE_APIBASEURL. - updateTypes — Which Telegram updates should trigger the workflow. messages_and_buttons listens for messages, edited messages, and callback button clicks. Current example:
messages_and_buttons. - chatFilter — Optional chat ID or @username to listen to. Leave empty for all chats. Multiple values can be comma-separated or newline-separated. Current example:
CONFIGURE_CHATFILTER. - commandFilter — Optional command name such as start or summarize, without the slash. Multiple values can be comma-separated or newline-separated. Current example:
CONFIGURE_COMMANDFILTER. - ignoreBotMessages — Ignore updates sent by bots when Telegram includes sender metadata. Current example:
false. - dropPendingUpdatesOnStart — Start from fresh updates instead of replaying old queued Telegram updates when the workflow starts. Current example:
false. - deleteWebhookOnStart — Delete any existing Telegram webhook before long polling. Enable this if Telegram reports a webhook conflict. Current example:
false. - pollTimeoutSeconds — Telegram long-poll timeout in seconds. Higher values reduce API churn. Range: 1-50. Current example:
1. - pollIntervalMs — Delay between long-poll requests in milliseconds. Range: 0-60000. Current example:
1. - limit — Maximum updates to fetch per poll. Telegram allows 1-100. Current example:
1. - includeRaw — Include the full raw Telegram update object in raw/response outputs. Current example:
false.
Configure X (Twitter) API
Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations.
- action — The action to perform on Twitter Current example:
POST. - text — The content of the tweet, reply, or quote tweet Current example:
CONFIGURE_TEXT.
Install Social Scheduler
Social Scheduler is a working agent built around Telegram. Install it, point its last step at X (Twitter), and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring Telegram to X (Twitter)
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise X (Twitter) (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 twitter-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 X (Twitter) — common questions
Can I connect Telegram to X (Twitter) without writing code?
You can build it entirely from the canvas. Authorise Telegram with an API key pasted into the vault, X (Twitter) with one OAuth sign-in, then tell the agent what approve agent actions from anywhere should look like once X (Twitter) 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 X (Twitter) automation?
Mapping tools move data; this reasons about it. Rather than copying a field into X (Twitter), the agent can weigh what arrived from Telegram, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Telegram and X (Twitter) 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 Telegram, X (Twitter) and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Telegram and X (Twitter) run leave behind?
You get an auditable trail rather than a success flag. It shows the Telegram context the agent worked from, the judgment it made about published work becomes native threads, and the exact change applied in X (Twitter), with approvals attached where you required them.
