Telegram Content Access

Check Telegram channel membership in one clean flow and unlock a protected link after the user joins.

The user wants a Telegram bot that checks channel or community membership before sending a link, file, or protected resource.

• What public Telegram channel link should users join?
• What link should members receive after access is confirmed?

• Start in one content access flow
• Show a compact intro with join-channel and check-access buttons
• Run the Telegram check-member module action
• Branch to delivery when membership is active
• Branch to join/retry guidance when membership cannot be confirmed
• Send Try again back to the first membership check

Good to know

• Use moduleActionRef for [email protected] templateKey check-member when the Telegram module is installed.
• Ask for the public Telegram channel link in the assistant briefing and pass that same value through the target_chat input field.
• Keep backend compatibility: the check-member module still accepts @channel usernames and numeric -100 chat IDs for legacy or advanced flows.
• Do not ask for user_id in this template; the Telegram module prepopulates it from {{sysvar|platformId}}.
• Do not save success/status outputs into variables; reference the check-member action output fields directly in the condition and messages.
• Keep this example as one flow; the recovery button should return to the first membership check rather than duplicating retry blocks.

Keep in mind

• Do not represent membership checks with a placeholder boolean when the Telegram module action is available.
• Do not ask the user to provide a Telegram user ID; use the Telegram module default {{sysvar|platformId}}.
• Do not split this simplified content-access template into multiple flows.
• Do not duplicate membership check, decision, or delivery blocks just for retry.
• Do not ask non-technical users for a numeric Telegram chat ID in the primary setup path.
• Do not leave the membership channel link placeholder unchanged when a completed briefing answer is available.
• Do not connect both condition outcomes to the same message.