Telegram IDs

How to find and use unique IDs for users, groups, and channels

What a Telegram ID is

An ID is a numeric identifier assigned to every Telegram user, basic group, supergroup, or channel. Workflows, bots, and automations use it to target the exact entity regardless of display names or public links.

Why IDs matter

Usernames and chat titles can change, but the ID stays the same for the lifetime of that account or chat. That stability makes IDs the safest handle inside automation.

When you need an ID

Sending messages

Message users or groups directly through your automation

Workflow automation

Bind chats and users to automated flows

Reliable targeting

Reference entities without usernames or invite links changing underneath you

How to get an ID

Here are the most reliable ways to obtain a Telegram ID inside Neurallux, ordered from the approach we recommend first.

1

Imported chats picker (in the editor)

Recommended
Best

After you verify a Telegram account and import your dialogs on the Bots page, workflow blocks can read the same chat list you see in Telegram. In Action and Condition nodes, use the compact # control in the top-right corner of the chat ID field to open a searchable list and insert the numeric ID in one click.

How the control looks in the field

1

On Bots, run Import chats for that account so Neurallux stores the dialogs you choose to sync.

2

Open a workflow, add or edit an Action or Condition block, and click the # button on the chat ID line.

3

Filter by title or @username, choose the chat — the field is filled with the correct numeric ID (including supergroups/channels as needed).

Why we put this first

  • Uses your verified MTProto session — IDs match what Telegram knows for chats you imported
  • No third-party lookup bots and no copy-paste from experimental Desktop settings
  • You pick the ID exactly where you type it in the automation

Good to know

Only chats that appear in your imported list for that verified account can be chosen. If something is missing, import again from Bots or use one of the fallback methods below.

2

Ready-made Neurallux workflow

Great alternative
Resolver template

Use the Chat ID resolver template from the Neurallux workflow hub. It automatically returns the correct ID for any chat, basic group, supergroup, channel, or user—no manual formatting.

Open the workflow hub

Why this works well

  • No fiddly steps—the flow handles everything
  • Works on phones and tablets without Telegram Desktop tweaks
  • Outputs the ID already normalized for API usage
3

Manual method (desktop only)

Enable peer IDs inside Telegram Desktop

Step-by-step:

1

Open Telegram Desktop

2

Go to Settings → Advanced → Experimental settings

3

Enable Show Peer IDs in Profile

After you enable the option:

Telegram shows a shortened ID in user profiles and when you open groups or channels.

Building the full ID:
Basic group

Prefix the ID with "-"

Prefix:-
Example:-123456789
Supergroup or channel

Prefix the ID with "-100"

Prefix:-100
Example:-100987654321
User

Do not add a prefix

Prefix:
Example:123456789

Telling basic groups and supergroups apart

You need the right prefix. To check the chat type:

1

Open the group and tap the ⋮ menu

2

Review the menu entries

Supergroup

If you see Vote in the menu, it is a supergroup. Prefix with -100

Basic group

If that entry is missing, it is a legacy group. Prefix with -

4

Third-party bots

Quick ID lookup using a dedicated bot

How to use it:

  1. 1

    Open @getidsbot

  2. 2

    To read your own ID, send the bot any message

  3. 3

    To read another user, supergroup, or channel ID, forward a message from that chat to the bot

  4. 4

    The bot replies with the resolved identifier

Why people like this route

  • Works on desktop, phone, and tablet alike
  • No experimental Telegram settings required
  • Returns IDs in the correct format automatically

Limitations

This approach may fail when:

  • The group or channel is private and the bot cannot see it
  • The user disabled message forwarding in privacy settings
  • Other privacy restrictions block forwarded metadata

When bots cannot help, fall back to the imported chat picker, the hub resolver template, or Telegram Desktop peer IDs

Using IDs inside Neurallux

Workflow blocks rely on Telegram IDs to target recipients and chats. Prefer the # picker after importing dialogs, use the Chat ID resolver hub template when you need a standalone flow, and keep Desktop or third-party methods as backups when a chat never appears in your import.