Skip to main content

Automation · Multiple personal Telegram accounts

Architecture reviewed 31 August 2026

Connect multiple personal Telegram accounts to Make.com

A native Make.com Telegram integration. Tag chats, update contact details and mark chats read from Make. It covers every personal Telegram account you connect, not a single bot.

Connect Telegram Install the Make.com app See the setup
Your Telegram accounts Entergram Native integration Make.com

The difference

Most tools connect one bot. Entergram connects every account your team runs.

  • One inbox across 100+ connected Telegram accounts, with no account switching. Filter down to the accounts you want to watch.
  • Real personal accounts, not bots. Each one runs through its own dedicated proxy, and replies go out from the account that owns the conversation.
  • The MCP covers every personal account on your seat with one connection.
See multi-account Telegram CRM

Direct answer

How the Make.com Telegram integration works

Build visual Telegram automations around authorized personal accounts using the published Entergram app for Make. Its actions update tags, update contact details and mark a chat as read on the real accounts your team uses, not on a generic bot. Triggers come from workspace events; check the app inside Make for the current list before you design around one. The app does not copy message content, so it is not an archive route.

Data model

What should move between Telegram and Make.com

The mapping is intentionally selective. Every row carries an identity, privacy or duplicate-handling rule. Object labels follow the destination API terminology.

Telegram contextMake.com destinationRequired rule
Entergram eventInstant or scheduled scenarioFilter by workspace and event type.
Account IDScenario variablePreserve before routers split the flow.
Fields and labelsMapped app fieldsValidate required values before write.
Read stateMark-as-read actionOnly after a person or a rule has handled the chat.
External record IDEntergram comment or data storeUse for duplicate prevention.
Tags and contact detailsEntergram update actionsMatch the chat on a stored Telegram ID, never a display name.
scenariosmoduleswebhooksconnectionsexecution history

Vendor-specific workflows

Three practical Make.com and Telegram workflows

01

Payment to a tagged chat

Trigger
Stripe reports a completed payment.
Result
Make tags the customer's chat as paid and updates their contact details, so the rep sees it in the inbox.
Guardrail
Use a verified customer-to-chat mapping and one-time idempotency key.
02

Form lead to a qualified chat

Trigger
A form submission creates a qualified lead.
Result
Tag the matching chat as qualified and update its contact details, so the rep follows up from their own account.
Guardrail
Do not message people who have not consented to the channel.
03

Ticket status back to the chat

Trigger
A ticket in your support tool changes status.
Result
Update the chat's tags so the inbox shows the current state, and mark it read once handled.
Guardrail
Search for existing records before you write.

Implementation

How to connect Make.com to multiple personal Telegram accounts

  1. 01

    Connect the Telegram accounts

    Authorize the personal Telegram accounts in Entergram first. The Make app acts on the chats in that workspace.

  2. 02

    Create a workspace API key

    Create a key in Entergram's workspace settings and give it only the scopes your scenarios need.

  3. 03

    Install the Entergram app in Make

    Open the invitation link on this page and add the app to your Make organization.

  4. 04

    Create the connection

    Add an Entergram module to a scenario and paste the workspace API key when Make asks for a connection.

  5. 05

    Build the scenario

    Use the Entergram actions to update tags, update contact details or mark a chat as read. Check the app in Make for the current list of triggers.

  6. 06

    Run it once on a test chat

    Confirm the tag or contact change shows up on the right chat in Entergram before you turn scheduling on.

Operational boundaries

What this integration should not do

  • Module coverage grows over time, so check the app inside Make before designing around an operation.
  • Make plan limits apply to operation volume and scenario scheduling.
  • Make connections and data stores hold workspace API keys and must be protected as production credentials.
  • Visual scenarios still need error handlers and duplicate protection.
  • Do not send unsolicited or unsafe bulk messages. Telegram permissions, consent and workspace policy still apply.

Related pages

More on Make.com and Telegram

Use it with AI

Make.com Telegram MCP

How an AI client works with Make.com and your Telegram accounts through the Entergram MCP.

Guide

Read integration guide

A longer article on Make.com and Telegram from our blog.

Evidence and review

Verify the destination platform before you build

Third-party APIs, scopes and limits change. This page was reviewed against official destination documentation on 31 August 2026. Confirm current requirements before production deployment.

Install the Make.com app

Read the official Entergram app for Make and the HTTP module documentation

Frequently asked questions

Make.com Telegram integration FAQ

Can I connect a personal Telegram account to Make.com?

Yes. Install the Entergram app in Make from the invitation link and connect it with a workspace API key. Its actions then work on the personal accounts in that workspace.

Does Entergram have a native Make.com integration?

Live. The Entergram app is published on Make and can be installed from the invitation link below, then connected with a workspace API key.

How is this different from Make.com Telegram MCP?

This page covers connecting Make.com to your Telegram accounts. The Make.com Telegram MCP page, where there is one, covers letting an AI client use Make.com and your Telegram accounts as tools.

How should Telegram contacts be matched to Make.com?

By the Telegram chat ID that Entergram passes into the scenario. Never match on a display name.

Should complete Telegram conversations be copied into Make.com?

No. The Make app updates tags and contact details and marks chats as read. It does not copy message content.

Continue exploring

Related Telegram integrations

Automation

n8n + Telegram

n8n's own Telegram node runs a bot. To work from the personal accounts your team actually uses, call Entergram from n8n instead: the HTTP Request node for REST API calls, or the MCP node when an AI step needs Telegram tools. Every call carries the account, chat and message IDs, so the workflow always knows which account it is acting for.

Automation

Zapier + Telegram

Zapier's Telegram apps run a bot. To act from the personal accounts your team uses, a Zap calls Entergram's REST API with a Webhooks by Zapier custom request, for example to tag a chat or update contact details after something happens in another app.

Support and ticketing

Zendesk + Telegram

Your customers write to a personal Telegram account and will not move to email or a portal. Your agents live in Zendesk. The native integration connects the two. Private chats on the Telegram accounts you select become Zendesk tickets. A new message continues the active ticket, and a message that arrives after the ticket is solved or closed opens a new one. When an agent replies in Zendesk, the reply is sent from the real Telegram account that owns the chat, so the customer keeps talking to the account they already know. The same tickets show up read-only on Entergram's ticket board, with a link back to Zendesk.

CRM

HubSpot + Telegram

Your reps qualify leads in Telegram DMs, and HubSpot only knows about the ones somebody remembered to type in. The native integration automates the copying, not the selling. Every Telegram chat on the synced accounts maps to one HubSpot contact, whether it is a DM, a group or a channel. Entergram custom columns sync both ways with contact properties, so a stage changed in Entergram reaches HubSpot, and a lifecycle stage changed in HubSpot comes back to the chat. Read-only HubSpot properties flow into Entergram only. Messages are not copied: HubSpot gets the structured fields, not the transcript. That is the scope of the HubSpot Telegram automation: contacts and their properties, kept in step without anyone re-keying a lead.

Build the connection carefully

Start with the Telegram accounts your team already uses

Connect them to Entergram, define the first governed workflow, then add Make.com with the minimum required authorization.

Start free trial Discuss the integration