Overview
Each Telestars automation owns a different Telegram moment. Start from the real trigger and destination, then choose the builder designed for that path instead of forcing one flow to serve every use case.
- Identify the correct workflow for a private-channel request.
- Separate first Secretary conversations from bot `/start` journeys.
- Use Channel Flow only for ordered channel publishing.
Before you start
- Choose the Telegram trigger and destination before building message steps.
- Prepare every Gallery asset for the bot that will deliver it.
- Use a test account to validate the complete Telegram path before enabling live traffic.
Step by step
- Open the Automation hub and identify the Telegram event that should start the workflow.
- Choose Join Request DM for a request to join a private channel.
- Choose Welcome DM for the first conversation on a connected Secretary Mode profile.
- Choose Bot Flow for a fan who starts a standalone bot with `/start`.
- Choose Channel Flow for posts delivered into a Telegram channel on a schedule.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Join Request DM | Triggered by a fan requesting access to a configured private Telegram channel. |
| Welcome DM | Triggered when a new Secretary Mode conversation begins for the selected profile. |
| Bot Flow | Triggered inside a bot conversation by the `/start` journey. |
| Channel Flow | Publishes an ordered sequence into a channel through an authorized publisher bot. |
Verify the result
- Trigger the workflow from Telegram and confirm each configured step arrives once and in order.
- Confirm media, buttons, delays, and paid state match the builder preview.
- Verify that saving, starting, pausing, or disabling the workflow leaves a clear dashboard status.
Troubleshooting
| If you see this | What to check |
|---|---|
| A workflow does not start | Check its trigger, enabled or running state, bot scope, Telegram permissions, and whether the test account already completed the one-time path. |
| A media step fails | Prepare the asset for the delivering bot and verify its type is supported by that step. |
| Formatting looks different | Use the Telegram import flow for native entities or keep dashboard-authored text within Telegram HTML limits. |
Best practice
Test one trigger, one destination, and one complete sequence at a time before adding paid media or longer delays.