How does the Telegram integration work?
AI Flowi Workflow receives Telegram bot updates through a public HTTPS Webhook endpoint. The path uses 2 documented extensions: Telegram Webhook Setup registers the endpoint, and Telegram Update Parser extracts incoming JSON fields. Registration runs separately from update processing. See the commercial integrations overview.
By Ai Flowi · Technical review: Janice Lee, Technical Support, Ai Flowi.
Published · Updated
Components and roles
| Component | Role |
|---|---|
| Webhook | Receives the Telegram update as JSON. |
| Telegram Webhook Setup | Documented extension that registers the webhook endpoint. |
| Telegram Update Parser | Documented extension that extracts common fields from an update. |
The setup path takes a bot token and Webhook URL, with an optional API key when the deployment requires one. The runtime path starts when Telegram sends an update to Webhook. Connect Webhook.JSON to Telegram Update Parser.Telegram Update, then pass documented parser fields to the next workflow step.
The parser documents chat_id, user_id, username, text, and command. Its exact public output type metadata is not supplied. Check the ports and types in your environment before connecting downstream components.
Where should I start with Telegram?
Start with webhook setup to register your public HTTPS endpoint, then use the update parser guide to understand incoming fields. Follow the AI bot tutorial for workflow logic and a separate reply request. Use troubleshooting when registration, parsing, downstream connections, or replies fail.
- Set up the Telegram webhook to register the endpoint.
- Parse Telegram updates to understand the inbound data.
- Build a Telegram AI bot to follow the full workflow path.
- Troubleshoot Telegram when registration, parsing, or replies fail.
Keep the bot token in its secret input and check registration output before sharing it, since a webhook URL may contain authentication information.