Nilyo
Sign inGet started →
Telegram + n8n

Telegram in n8n from your own account

The built-in Telegram node drives a bot: a separate identity users must message first. The Nilyo node connects your own account, so a workflow reads the conversations you already have and answers as you.

Install and authenticate

On n8n Cloud, search Nilyo in the nodes panel and drop it on the canvas: the package is a verified community node, so there is nothing to install. On self-hosted n8n, add n8n-nodes-nilyo from Settings then Community nodes. Create a personal token in Nilyo under Agent access and store it in a credential named Nilyo API.

Account, not bot

A bot cannot message someone who has not written to it first, appears under its own name, and in a group sees only what its privacy mode allows. That fits broadcast notifications to people who opted in. It does not fit a workflow that has to reach a client, a supplier or a colleague, which is what most Telegram automations are really for.

Connect once, by QR or phone code

Telegram is connected in Nilyo with a QR code or a code sent to your number. If the session later expires, you reconnect the same account rather than creating a second one, so chat identifiers held in a workflow keep working.

Chats, groups and channels are marked

Listings say which is which, so a workflow can summarize a busy group into a ticket without posting in it, or filter to direct conversations only. Chat and message identifiers travel together, because a message id means nothing outside its chat.

“Summarize what I missed in my Telegram groups since yesterday.”
“Send a Telegram to the on-call colleague when the deployment finishes.”

Inbound messages start the workflow

The Nilyo Trigger subscribes to new Telegram messages for the connected account, so the workflow starts on delivery with the identifiers needed to fetch the conversation — no schedule polling an account that was quiet all night.

No invented rate limit

Unlike LinkedIn or Instagram, Telegram carries no local daily budget here: calls are serialized per account so nothing runs in parallel, and Telegram’s own limits apply. Saying so is more useful than publishing a number that enforces nothing.

Common questions

Can I keep the bot node too?

Yes. A bot remains the right tool for broadcast notifications to users who opted in. Use Nilyo when the workflow must act as you, inside existing conversations.

Does Telegram ask for a phone each time?

No, the account is connected once. An expired session is reconnected on the same account rather than duplicated.

Can an AI Agent node use it?

Yes, attached as a tool, using the tool variant of the node type.

Can it post in a group?

Yes, as you rather than as a bot nobody added to the group.

How Telegram works with Nilyo

Connection. QR code shown in the conversation (Telegram › Settings › Devices) or a code sent to your phone.

What your agent can do. Chats, groups and channels, message history, sending text and media, reactions.

Pacing and safety. No local budget; calls are serialized per account.

  • Groups and channels appear in the chat list with their type, so the agent can summarize a channel or answer in a group on request.

All Telegram guides

Related guides

Give Nilyo to your agent.

Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.

© 2026 Nilyo.