Skip to main content
Connect your Migma account to @MigmaAIBot, then message Migma to import a brand, design emails, set up a sending domain, import an audience, create a campaign, and send or schedule it from Telegram.
Illustration of Migma connected to Telegram above a List my brands prompt

Migma for Telegram illustration

Migma for Telegram is in beta. Use only @MigmaAIBot. The profile name should be MigmaAI.

Before you start

You need:
  • A Migma account
  • A Telegram account
  • Access to the Migma account you want Telegram to use

Connect Telegram in four steps

1

Open the Migma bot

Go to t.me/MigmaAIBot and select Start Bot. In the Telegram app, press Start and send a message.
Illustration of the official MigmaAI Telegram bot profile with the @MigmaAIBot handle and Start Bot button

The official profile shows MigmaAI and @MigmaAIBot

2

Open the connection page

If your account is not linked, the bot replies with Connect Migma. Select it.You can also open Settings → Integrations → Telegram in Migma, or go directly to migma.ai/telegram/connect.
Illustration of a Telegram chat with MigmaAI and a Connect Migma button

Select Connect Migma in the bot reply

3

Confirm your Telegram account

Sign in to Migma if asked, then select Log in with Telegram. Approve the Telegram account you want to link.
Illustration of the Migma Telegram connection page with the Log in with Telegram button

Connect page with the signed-in Migma account hidden for privacy

4

Return to Telegram and test the bot

After Migma confirms the link, return to Telegram and send a new message:
A reply confirms the bot can recognize your Telegram account and access the permitted Migma actions.
Illustration of MigmaAI returning three Stripe onboarding email drafts in Telegram

Migma replies with previews and an Open in Migma button

Linking does not replay the message that opened the connection flow. Send a new message after returning to Telegram.

What Migma can access

Telegram confirms your account id and username so Migma can recognize you. Migma processes messages, captions, and images you send directly to the bot, plus group messages that mention the bot. It does not access unrelated chats or your contacts. Migma keeps recent bot-thread context so follow-up requests such as Make it shorter can refer to the email already discussed. One Telegram account links to one Migma account.
Never paste a Migma API key into Telegram. Use only the Connect Migma flow.

Direct messages and groups

For direct messages, send your request to @MigmaAIBot. For groups:
  1. Add @MigmaAIBot to the group.
  2. Mention @MigmaAIBot in each request.
  3. Test the same request in a direct message first if the group gets no reply.
Messages without the bot mention are ignored in groups. When Migma needs a choice, such as which segment to target, it shows answer buttons. Tapping a button is the same as typing the answer. Only the person who asked can respond to those buttons.

Approve sends in chat

Before Migma sends or schedules a campaign, it posts a summary with the subject, audience, recipient count, sender, send time, and an inbox rendering score. Confirm with Send or Cancel, or reply in the chat. You approve every send. If you change the campaign after the summary appears, Migma shows a new summary before anything goes out. Migma posts in the same chat when a domain finishes connecting, an import finishes, or a send completes. Ask for opens and clicks when you want campaign results.

What you can ask

Results can include preview images, DNS setup links, and download links. After the workflow-tools release, new account links approve access to Migma email, audience, campaign, domain, webhook and billing tools. Sending or scheduling requires a send summary and your confirmation in chat. Contact deletion and external changes also require approval. Billing checkouts are completed by you. Existing links keep their original scopes; disconnect and reconnect to review broader access. Example chat:

Audience exports and connected tools

After the release with these workflow tools is available, ask: Export unsubscribed contacts for my brand as CSV. The bot uses the shared Migma MCP catalog, starts an export, and checks the job for a private download link. Large exports may still be processing when a reply arrives; ask it to check status in the same thread. For store or CRM workflows, the bot discovers tools enabled on that brand and reads their argument schemas before calling them. Existing server permissions and approval settings still apply. Tools requiring dashboard approval remain blocked in chat until you review the tool’s permissions in Migma. A CSV export does not synchronize Shopify. Shopify storefront tools do not include customer marketing-consent updates; synchronization needs a connected tool with that access. The bot must report unsupported operations and provider failures instead of claiming completion.

Troubleshooting

The bot does not reply

  1. Confirm the profile shows MigmaAI and @MigmaAIBot.
  2. Press Start in Telegram.
  3. Complete the connection using the intended Migma account.
  4. Return to Telegram and send a new direct message.
  5. In a group, mention @MigmaAIBot exactly.
  6. Reopen migma.ai/telegram/connect and connect again.
If a direct message still gets no reply, email support@migma.ai.

Telegram connected to the wrong Migma account

Disconnect the Telegram link, sign in to the intended Migma account, then repeat the connection steps.

Disconnect Telegram

Send disconnect to @MigmaAIBot. You can also open Settings → Developers → API Keys in Migma and revoke the key named for your Telegram account. After disconnecting, the bot asks you to connect again on your next message.

Build your own Telegram bot

Use Migma’s agent auth or API if you need a separately hosted bot or custom workflow.

Agent Auth

Give a custom bot scoped access for each Migma user.

OpenClaw

Run Migma in Telegram, Slack, WhatsApp, or Discord through OpenClaw.

SDK

Generate emails, fetch HTML, and read preview URLs from code.

API reference

Review the public endpoints available to your bot.
Last modified on October 3, 2026