Communication × Social
TelegramX (Twitter)AGNT

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.

Install Social Scheduler → Get AGNT free

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, in full

Telegram is reached through the telegram-api node and X (Twitter) through the twitter-api node. Between them sits the agent, which is the part a field-mapping tool cannot do: it reads the item and decides whether the hand-off is warranted at all.

Telegram to X (Twitter): watch telegram → read it and decide → act in x (twitter) TRIGGER receive-telegram-update Watch Telegram Fires the moment it happens. ACTION agnt-agent Read it and decide Judged against your own rules. ACTION twitter-api Act in X (Twitter) Runs POST.
Neither Telegram nor X (Twitter) credentials leave your machine — both live in a local vault.
Telegram → X (Twitter)paste into a new workflow
{
  "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": {},
      "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": "f7850cb3-45fb-4b25-a0fa-bf8e70c2e412",
      "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 X (Twitter), and explain why."
      },
      "description": "Decides whether this Telegram item warrants anything in X (Twitter).",
      "error": null,
      "isActive": false,
      "output": null,
      "outputs": {}
    },
    {
      "id": "b7d52c0d-336e-4a8c-a713-e8c9d96ce8ec",
      "text": "Act in X (Twitter)",
      "x": 512,
      "y": 528,
      "isEditing": false,
      "type": "twitter-api",
      "icon": "connect",
      "category": "action",
      "isSelected": false,
      "parameters": {
        "action": "POST"
      },
      "description": "Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations.",
      "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
}

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)

  1. Install AGNT — it runs on your own machine and needs no account to start.
  2. Authorise X (Twitter) (one OAuth sign-in) and Telegram (an API key pasted into the vault). Nothing is stored anywhere but your disk.
  3. Describe the job in plain language, or paste the definition above; telegram-api does the reading and twitter-api the writing.
  4. 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.

Give AI a job. Get the proof.