Telegram Group, Channel & Topic ID Guide for TwitGram

This guide covers how to find Telegram group, channel, and topic IDs, understand the formats TwitGram Bot accepts, and connect your destination correctly so alerts route where you intend. If you already have your ID and just need the TwitGram setup steps, jump to The TwitGram Routing Flow for Destinations.

Telegram Destination IDs in Plain English

Group Chat ID vs Channel ID vs Topic ID

Topic IDs are not standalone — they are always a suffix on the group's numeric ID, separated by /.

Why Many IDs Look Like -100...

Regular groups have negative IDs (e.g., -123456789). When a group is upgraded to a supergroup, or when a channel is created, Telegram assigns a new ID in the -100... range (e.g, -1001234567890). This is a Telegram internal distinction. For routing purposes, the key point is: if your group was recently upgraded to a supergroup, the ID changed. The old ID no longer works.

When @username Works, and When Numeric ID Is Mandatory

If your group or channel has no public username, or if you are routing to a topic thread, you must use the numeric ID.

Fast Methods to Get Telegram IDs Without Guesswork

Method 1 — Use @raw_data_bot to Extract Group/Channel IDs

This is the most reliable method for groups and channels.

1. Open Telegram and search for @raw_data_bot.
2. Start the bot and send /start.
3. Forward any message from your target group or channel into the @raw_data_bot chat.
4. The bot replies with the full message object. Find the chat field — the id value is your destination ID.

The ID will be negative for groups and supergroups. Copy, including the - sign.

Common failure: Forwarding a message from a channel where forwarding is restricted. In that case, add @raw_data_bot to the group or channel temporarily and send a test message — the bot will return the chat ID in its reply.

Method 2 — Use a Forum Topic Message to Capture Topic ID

@raw_data_bot returns the group chat ID but not the topic ID. To get the topic ID:

1. Open the target topic thread inside your forum-enabled supergroup.
2. Send any message inside that topic.
3. Forward that message to @raw_data_bot.
4. In the returned object, find message_thread_id — that is your topic ID.

The full destination string for TwitGram is ChatID/TopicID, for example: -1001234567890/42.

Group ID Setup: Formats That Work

Numeric Group Format: -1001234567890

The standard format for supergroups. Always negative, always starts with -100 for supergroups.

• Include the full string with the - sign
• Do not add spaces or line breaks
• If the group was recently upgraded from a basic group, get the new ID — it will have changed

Topic Format for Forum Groups: -1001234567890/42

Used when routing alerts to a specific topic thread inside a forum-enabled supergroup.

• The number before / is the group chat ID
• The number after / is the topic (message thread) ID
• @username/42 is not valid — the group portion must be the numeric ID

Username Format: @mygroup (and Its Limits)

Works only for groups with a public username. Simpler to type, but has two limitations:

1. If the group username changes, the routing breaks
2. Cannot be used for topic routing

For production setups where stability matters, numeric ID is more reliable.

Channel ID Setup: Formats That Work

Channel Username Format: @mychannel.

The simplest format for public channels. Works as long as the channel username does not change.

Numeric Channel Format: -100...

Required for private channels (no public username). Same -100... prefix as supergroups. Retrieve it using @raw_data_bot by forwarding a message from the channel.

Admin Permission Requirements Before Alerts Can Send

TwitGram Bot verifies access by sending a test message to the destination. For channels, this requires the bot to be an administrator with Send messages permission.

Steps to add the bot as an admin:
1. Open the channel in Telegram.
2. Go to Manage Channel → Administrators.
3. Add the TwitGram bot (or your custom bot, if configured).
4. Grant Post Messages permission at minimum.

If the bot is not an admin, TwitGram cannot validate the destination and will keep you in setup state.

The TwitGram Routing Flow for Destinations

After you collect your Telegram destination identifiers, the important part is entering them in TwitGram using the exact formats it expects.

In TwitGram, this is done from the alerts configuration flow, not from a separate external panel.

1) Open the Destination Setup Path in TwitGram

From the bot home screen, go to:

Configure Alerts → choose either Group Alerts or Channel Alerts → select the watchlist.

TwitGram then prompts you to submit a destination identifier for that watchlist.

2) Use the Correct Input Format for Each Destination Type

For Group Alerts, TwitGram accepts:
- Numeric group chat ID: -1001234567890
- Group username: @mygroup.
- Group + topic format (forum groups): -1001234567890/42

For Channel Alerts, TwitGram accepts:
- Channel username: @mychanne.l.
- Numeric channel ID: -1001234567890

Important: topic IDs are only supported with numeric group chat IDs.
@username/topic style is not valid.

3) Permission Prerequisites Before Validation

TwitGram verifies access by sending a test/welcome message to the destination you provide.

To pass this check:
- For channels, add the bot and grant Administrator with Send messages.
- For groups/topics, ensure the bot is present and can post in the target context.

If the bot cannot post, TwitGram keeps you in setup state and asks you to retry.

4) What Happens with Topic IDs

When you submit ChatID/TopicID, TwitGram parses both values and attempts delivery into that exact topic thread.

If the topic is invalid or inactive, you'll typically get a thread error (for example, thread not found / invalid message thread id).
At that point, re-check the topic ID source and confirm the group is a forum-enabled supergroup.

5) Save Confirmation and Post-Setup Checks

Once TwitGram can successfully send to the destination, it stores that route for the selected watchlist and confirms setup.

Before relying on it in live trading:
- Trigger one real alert path (or controlled test condition).
- Confirm the message lands in the intended group/channel/topic.
- Repeat for each watchlist that needs separate routing.

This gives you deterministic alert delivery, which is the baseline requirement for fast crypto execution.

Common Errors and How to Fix Them Fast

"Invalid format. Use @channel or -100..."

Cause: The submitted string does not match any accepted format — often a plain number without the - sign, or a URL instead of an ID.

Fix: Re-check the format table above. Strip any URL components. Ensure the numeric ID includes the leading -.

"Group ID must start with '-' or '@'"

Cause: A positive number was submitted for a group destination.

Fix: Group and supergroup IDs are always negative. Retrieve the ID again using @raw_data_bot and confirm the - sign is included.

"Topic IDs Cannot Be Used with @userna.me"

Cause: A topic destination was submitted in @username/42 format.

Fix: Replace the username portion with the numeric group chat ID. The correct format is -1001234567890/42.

"Thread Not Found / message_thread_id_inva.lid."

Cause: The topic ID is incorrect, the topic was deleted, or the group does not have forum mode enabled.

Fix: Confirm the group has Topics enabled in Group Settings. Re-extract the topic ID by forwarding a message from inside that specific topic to @raw_data_bot and reading message_thread_id from the output.

"Bot Cannot Access the Group/Channel.nnel"

Cause: The bot has not been added to the destination, or it lacks posting permission.

Fix: Add the bot to the group or channel. For channels, the Rant Administrator can send messages. For groups, ensure the bot is a member and group permissions allow bots to post.

TwitGram-Specific Best Practices for Crypto Operators

Keep Separate Destinations for Execution vs Research Streams

Mixing high-urgency signals (account deletions, listing announcements, CA drops) with lower-priority research signals (general KOL commentary, project updates) in the same destination creates noise at exactly the wrong moment.

The practical split: one destination for signals you act on immediately, one for signals you review periodically. Different watchlists, different IDs, different channels.

Use Topics for Strategy Segmentation Inside One Supergroup

If your team operates inside a single supergroup, forum topics let you route different watchlists to different threads without creating multiple separate groups. Each topic gets its own ID. Each watchlist in TwitGram gets its own topic destination.

This keeps the team in one place while keeping signal streams separated. Exchange listings to one topic, KOL activity to another, dev behavior signals to a third.

Run Destination Checks Whenever Team Structure Changes

When a group is upgraded, a channel is renamed, or a topic is deleted, the ID or routing may break silently. Build a habit: any time the team's Telegram structure changes, re-verify each TwitGram destination with a test alert before relying on it.

From Setup to Trade-Ready Alert Stack

Your IDs are verified. Now connect them to a working watchlist.

1. Enter your first destination ID in TwitGram via Configure Alerts.
2. Run a test alert to confirm delivery lands in the right place.
3. Create a watchlist with 5–10 high-signal accounts and route it to the verified destination.
4. Add whitelist keyword filters (0x, pump, launching, listed) to reduce noise.
5. Add blacklist filters (gm, giveaway, airdrop) to suppress low-signal content.
6. Repeat for each additional destination once the first is confirmed working.

A complete setup: one verified destination per signal category, each watchlist filtered and routed, each route tested before going live.

Final Takeaway

Correct destination IDs are the foundation of reliable alert routing. One wrong format means silent failure or delivery to the wrong place — neither of which you will notice until you miss something.

Get the ID, verify the format, confirm the bot has access, and test delivery. That is the full checklist.

No API key. No X account connection. Telegram-first execution.

Start here: TwitGram Bot · twitgram.xyz