User

Channel Telegram Oauth

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature

Select the intended record from Channel Telegram Oauth. Its detail/edit address follows /portal/channels/telegram/oauth/{type?}. Use the application’s record link; do not type a placeholder such as {id}.

Choose a task

Select the intended record from Channel Telegram Oauth. Its detail/edit address follows /portal/channels/telegram/oauth/{type?}. Use the application’s record link; do not type a placeholder such as {id}.
Find the form containing Access token. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Validate token and continue. Check the current record, recipients, amount or destination before confirming when those values apply.
If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Field	What to enter or choose
Access token	Enter the value privately from your account or the service configuration. Do not use sample credentials from a guide. The form’s example is 123456:ABC-your-telegram-bot-token. Replace it with your own value.

Field descriptions appear beside each task above so that separate forms are not mixed together.

Stay in the same account/workspace and reopen the intended record or result screen.
For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Problem	What to check
The screen or action is missing	Check the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejected	Read its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is empty	Check the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pending	Check its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Role-scoped source references

Pinned commit: 1d0944d30f606782c9abf5b878224cdd3cd09b99

Source-only route information

Method	Source-default route
GET	/portal/channels/telegram/oauth/{type?}
POST	/portal/channels/telegram/oauth/{type?}
GET	/portal/channels/telegram/oauth/{type?}/wait
POST	/portal/channels/telegram/oauth/{type?}/ajax-wait