Your Telegram conversations can be part of more than a chat with an AI assistant. Telepath’s REST API lets you connect that context to automation tools and your own applications.

Use our n8n community node for a configured starting point, or build an HTTP integration for tools such as Make. The API uses OAuth: each person connects their own Telepath account and grants access to it.

What you can build

  • A conversation digest: read available messages from selected chats, summarize them with your chosen AI and save the summary.
  • A customer follow-up workflow: find a conversation, extract a request and create a note or task.
  • A reply assistant: prepare a draft, review it and send it through an authorized Telegram connection.
  • A channel workflow: prepare content and publish to a channel you have connected with the required permissions.

The API also exposes available transcripts, supported media, Notes and reminders. Access depends on what is connected, stored and allowed for your account.

Connect Telepath to n8n

The n8n-nodes-telepath package includes operations for chats, messages, media, channels, Notes and reminders, plus a Telepath OAuth2 API credential.

  1. On self-hosted n8n, open Settings → Community Nodes and install n8n-nodes-telepath.
  2. Add a Telepath node and create a Telepath OAuth2 API credential. Use a current n8n version that supports OAuth dynamic client registration.
  3. Select Connect my account and complete Telegram sign-in. The credential handles client registration and PKCE, and uses n8n’s token refresh support.
  4. Make sure Telegram collection is connected: follow the device setup guide to share private chats through Chat Automation. Signing in and making chat history available are separate steps.
  5. Run Chat → List Telegram chats, then Read chat messages to check the data before adding automation.

Using n8n Cloud? Cloud installation depends on verification and availability in n8n’s node directory. An npm release alone does not make a package available in Cloud. See n8n’s community-node installation rules; the self-hosted route above is the starting point for this guide.

The repository includes example workflows for listing chats and collecting a bounded window of messages into an n8n Data Table. Select your own credential and review the selected chat before enabling a schedule.

What about Make?

Make’s HTTP app can call APIs without a dedicated app module. This is the route to explore for Telepath; this guide does not describe a native Telepath app in Make.

Authentication needs to be configured first. Telepath requires Authorization Code with S256 PKCE, a registered callback URL and token refresh. Make documents an OAuth 2.0 connection, but a generic OAuth option alone does not establish compatibility with these requirements. We have not verified an end-to-end Make sign-in and refresh flow for this guide.

If your chosen Make connection cannot generate and exchange PKCE values, it needs a compatible OAuth intermediary or custom integration. Contact us before building around it. With a valid OAuth connection, your HTTP requests use the API base URL below, JSON bodies where required and a Bearer access token. Store credentials in the platform’s connection settings, outside prompts and message text.

API authentication and examples

For every endpoint, parameter, response and error, see the complete Telepath REST API Reference. You can also download the OpenAPI 3.1 specification.

Base URL: https://telepath.lemma.company/api/v1

Custom clients can discover the authorization, token and registration endpoints from Telepath’s OAuth metadata. Register your integration’s exact redirect URI, use S256 PKCE and request telegram.read for reads, adding telegram.write for actions. The OAuth resource identifier is https://telepath.lemma.company/mcp, including when you call REST endpoints.

After completing OAuth, send Authorization: Bearer <access_token>. A Telegram bot token is not a Telepath access token. Handle expiry through OAuth refresh rather than copying a temporary token into a permanent workflow.

List available chats

This read-only request uses the same endpoint as the n8n credential check. The shell variable below represents your own valid access token.

curl 'https://telepath.lemma.company/api/v1/chats/list' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"limit":10}'

Read one chat

Replace CHAT_ID with an ID returned for your own archive.

curl 'https://telepath.lemma.company/api/v1/chats/CHAT_ID/messages?limit=20' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN"

Send an authorized reply

This request sends a real message when supplied with a valid token, chat ID and permissions. Review the destination and text first.

curl 'https://telepath.lemma.company/api/v1/chats/CHAT_ID/messages' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"text":"Thanks for your message. I will get back to you shortly."}'

For private Telegram Business chats, replies require the appropriate reply permission and an incoming message in that chat within the previous 24 hours. Channel posting uses dedicated channel operations and separate permissions.

Start with a small, scheduled workflow

  1. Run a schedule, initially every five minutes.
  2. Read a bounded window from a selected chat.
  3. Filter incoming messages and deduplicate by chat ID + message ID, using persistent storage.
  4. Generate a summary or draft with your chosen AI provider.
  5. Review replies before sending, and record the result to avoid duplicate actions.

This is polling, not an incoming-message webhook. Telepath does not currently offer an outgoing event for every new message through this API. Bounded reads can miss messages during busy periods or downtime. Do not use a periodic snapshot as a guarantee of complete message capture.

The REST gateway currently allows 120 requests per minute per account, shared across credentials and workflows. Telegram and plan limits also apply. Respect 429 responses and Retry-After. If a send times out or returns an uncertain error, check the conversation before retrying: the message may already have been delivered.

Make history available before automating it

OAuth gives your workflow access to your Telepath account; it does not automatically import every Telegram conversation. Chat Automation collects new messages from the private chats you allow. To add older history to your archive, send /import to the Telepath bot and follow the export instructions. Group and channel access require their own setup and permissions.

Start with one chat and a read-only workflow. Once you can see the expected messages, add the next step. If you need help choosing between n8n and a custom Make integration, tell us what you want to automate.