Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Telegram, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands.
All connector references · Connect an account · AI setup and shared results
Read the identity of the connected Telegram bot.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Telegram connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
Result
Returns ok and the bot user under result, including id and available username.
Example
Choose your Telegram Account and add Get bot details. This command needs no other settings beyond the inputs described above. These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Check the bot token and chat access. Users normally need to start the bot before private messaging; groups/channels need suitable bot permissions. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Read chat details accessible to the Telegram bot.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Telegram connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| Chat | text | Required. Numeric chat ID as text, including a leading minus sign for groups, or an allowed @channelusername. The bot needs access. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
Result
Returns ok and the chat object under result, including id, type and available title/username.
Example
Choose your Telegram Account and add Get chat. Set Chat = "-1001234567890". These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Check the bot token and chat access. Users normally need to start the bot before private messaging; groups/channels need suitable bot permissions. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Send a plain text Telegram message without link previews.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Telegram connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| Chat | text | Required. Numeric chat ID as text, including a leading minus sign for groups, or an allowed @channelusername. The bot needs access. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Message | text | Required. Plain text message, normally at most 4,096 characters under Telegram’s limits. Link previews are disabled; no formatting mode or attachment is added. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
Result
Returns ok and the sent message under result, including message_id and chat. No formatting mode or attachments are added.
Example
Choose your Telegram Account and add Send message. Set Chat = "-1001234567890"; Message = "Hello from the demo workflow.". These are illustrative values: replace example IDs and addresses with your own permitted test values. An intended live run creates/changes data or sends a message; inspect its receipt before repeating it.
Errors and limits
Check the bot token and chat access. Users normally need to start the bot before private messaging; groups/channels need suitable bot permissions. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Isolated tests and live debugging do not call connected providers. Enable Use live data only when you intend to contact the account. Writes, messages and AI requests can change real data or incur provider charges. A successful connection check does not prove access to every action. These examples explain the command contract; they are not evidence of a completed live provider request.
Zendesk commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Zendesk, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All ...
Connector command reference
Find detailed inputs, results, examples and common errors for every command in the 56-app connector library. Open an action below or use its help button in the editor. [Business connector setup](/docs/commands/business-connectors) · [AI connector setup](/docs/commands/ai-connectors) - [Google Drive]...
Notion commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Notion, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
Cloudflare commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Cloudflare, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [A...
Twilio commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Twilio, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
