Overview
A Join Request workflow can message the requester privately, post to the configured group destination, or do both. Content and approval timing are separate controls so you can verify delivery before granting access.
- Write a personalized Telegram-compatible message.
- Attach Gallery media and a supported call-to-action button.
- Choose manual, immediate, or delayed approval.
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 connected channel and choose DM, group delivery, or both.
- Write the message using supported HTML and placeholders such as `{first_name}`, `{username}`, and `{channel}`.
- Optionally attach one prepared Gallery asset and choose whether it is free or paid in Stars.
- Add a supported URL or Mini App button and preview its label and destination.
- Choose manual, immediate, or delayed approval, save, and test with a new join request.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Delivery mode | The saved workflow can target the requester DM, the configured group destination, or both. |
| Content source | You can author a template, attach Gallery media, or use an eligible Telegram source message where the interface provides import. |
| Paid attachment | A paid media attachment requires a positive Stars price and a Telegram-ready asset. |
| Approval timing | Approval can remain manual, run immediately, or wait for the configured delay. |
Verify the result
- Placeholders resolve to the requesting fan and selected channel.
- The button opens the exact saved destination.
- The request is approved only according to the selected timing mode.
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.