Use the generic Trigger, API Request, Transform, and Webhook nodes for Telegram Bot API workflows while the native connector remains unavailable.
Where: Flowgen → Add → Automation
Before you start
- A Telegram bot credential must already exist in a server-side connection that Flowgen can select. The current visible Flowgen UI does not provide a complete self-service Telegram connection-provisioning flow.
Key ideas
- Current integration path: This build has no dedicated Telegram node. Telegram is reached as an external API from an authenticated server-side connection.
- Outbound bot actions: Shape chat/message/media values with Extract / Merge, then call the Bot API through API Request; use Send Webhook for a generic callback destination.
- Incoming updates: The trigger contract supports inbound webhooks, but the endpoint id and secret must be minted during publication; the canvas deliberately cannot invent them.
Steps
- Create or select the server-side connection that owns the bot credential.
- Build the flow with Trigger, Extract / Merge, and API Request.
- Test with a non-production chat and verify the shaped response.
- Publish the automation only when its trigger/address surface is available, then monitor it in Automations.
Outbound pattern
- Trigger the flow manually or on a schedule.
- Use Extract/Merge to shape chat_id, text, media, and reply markup.
- Call the appropriate Telegram Bot API method through API Request using the saved connection.
- Inspect the response and route errors before continuing.
Inbound pattern
Incoming Telegram updates require a published webhook address and secret. The platform must mint that address during automation publication; the canvas must not invent or hard-code one.
Limitations and important notes
- There is no native Telegram node in the current source.
- Do not paste bot tokens or Authorization headers into authored node fields; credential headers are rejected and secrets belong in the server connection broker.
- Until connection provisioning and incoming webhook publication are exposed end-to-end, this is an infrastructure-assisted beta workflow rather than a fully self-service connector.
Troubleshooting
I cannot create/select a Telegram connection
The visible product does not currently expose the complete provisioning path. Ask the workspace/platform administrator to provision the server-side connection; do not place the bot token in the canvas.
FAQ
Is there a native Telegram node?
Not in the current source. Use the generic automation/API path; the catalog must not imply a native connector exists.
Can I paste an Authorization header into the node?
No. Credential headers are rejected by design; authentication comes from the server-side connection broker.