Nilyo
Sign inGet started →
Telegram + Make

Connect Telegram to Make

Make’s Telegram modules drive a bot: its own identity, unable to message anyone who has not written to it first. Nilyo connects your own account, so a scenario acts inside the conversations you already have.

How to connect

Add an MCP Client module to the scenario — or an MCP tool from an AI Agent’s configuration — create a connection and set the server URL to https://nilyo.com/mcp with OAuth authentication. A browser window opens to authorize, the same Nilyo sign-in ChatGPT and Claude use, with no Make-specific account to create.

Bot or account

Keep the bot for opt-in broadcasts — people who started a chat with it and expect notifications. Use your own account when the scenario has to reach a colleague, a client or a group where you are already a member, and when the message should come from you rather than from a product name.

Groups are read-only until you say otherwise

Listings mark chats, groups and channels, so a scenario can summarize a busy group into a ticket without posting in it. Chat and message identifiers travel together, since a message id means nothing outside its conversation.

Resolve the recipient by name

A resolution module turns a name into the exact conversation and returns the candidates when several match. Passing a display name straight into a send module is how an alert lands in the wrong group.

A realistic scenario

A deployment finishes; the scenario posts the result in the existing team group and sends a one-to-one message to whoever is on call — both as you, with no bot for anyone to find and start first. Telegram carries no local daily cap here; calls are still serialized per account.

Watch conversations without polling them

A scheduled scenario that lists Telegram chats every few minutes spends its runs on nothing. A realtime destination delivers a new message when it happens, with the chat and message identifiers needed to fetch the conversation, so the scenario starts on a real event instead of a timer.

“When a deployment finishes, post in the team group and message the on-call.”
“Summarize a busy group into a ticket each morning.”

Common questions

Why not the built-in Telegram bot modules?

A bot cannot initiate a conversation, shows its own name, and sees only part of a group depending on its privacy mode.

How is the account connected?

With a QR code or a phone code, once; an expired session reconnects the same account.

Is there a daily limit?

No local budget for Telegram here. Calls are serialized per account and Telegram’s own limits apply.

Can a scenario post in a group I belong to?

Yes, and it posts as you rather than as a bot nobody added to the group. Listings mark chats, groups and channels separately, so a scenario can read a group for context and answer only in the direct conversation if that is what you want.

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.