All nodes/Integrations/Telegram

Telegram Config

Picks a saved Telegram bot from the workspace. The credentials live in the workspace settings, never in the graph — this node hands the resolved token to the action nodes through their 'telegram_config' port.

Try it

When to use it

Reach for this node in one situation: when a Telegram action node must talk through a bot other than the one this workflow is deployed to. By default all nine actions (Send Telegram Message, Telegram Reaction, Telegram Inline Keyboard, Telegram Get File, Telegram Forward Message, Telegram Moderate, Telegram Manage Chat, Telegram Chat Info, Telegram Tools) take the bot from the run context: their “Connection source” field says “From the run context”, and their telegram_config port is not even drawn.

Cases where the node earns its place: the workflow answers in a support bot but posts announcements to a channel as a different bot; or the workflow is not deployed to Telegram at all — it runs on a schedule, from the API or from web chat — so there is no ambient bot to inherit.

How it works

The node stores no token. It references an integration saved under “Settings → Integrations” (kind Telegram: bot username and bot token) and, at run time, hands the resolved token over the wire into the action node’s telegram_config port. Only the integration id stays in the graph, and the run log shows nothing but the connection name for this node — credentials reach neither the logs nor the event stream.

Common mistakes

• Nowhere to draw the wire. The telegram_config port appears on an action node only once its “Connection source” is set to “External connection (wire a config node)”. Flip the field first, then draw the edge.
• Expecting this node to pick the trigger bot. The bot the workflow answers in is chosen in the deploy panel (“Channels → Telegram → Select Telegram bot”), not here.
• A connection with no token. If the integration is wired but carries no bot token, the action node stops with an error — it does not quietly fall back to the deploy bot.
• A leftover wire from an earlier version of the graph. A token arriving on the port always wins over the deploy bot, so if an action talks through the wrong bot, check the incoming edge.
• One node, one bot. Two actions on two different bots need two config nodes; a single one can feed any number of actions that share a bot.

Inputs

—

Outputs

Configuration