Telegram bot — inbound messages
SETUP: create a bot with @BotFather and paste its token (or a ${credential.telegram.token} reference) — then every message to your bot runs this flow. Test simulates one inbound message.
What’s inside
2 nodes — every type links to its full reference page.
| Step | Node | Type |
|---|---|---|
| Telegram inbound | Telegram Trigger | input.telegram |
| Route to support | Console | utility.console |
Import it
- Studio → Import — paste the JSON below (or the URL
/docs/templates/telegram-bot-inbound-messages.json). - Or ask the AI Copilot with the JSON pasted after the phrase:
import this workflow json into a new workflow named "Telegram bot — inbound messages" - Any credentials the nodes need are
${credential.…}references — add them once in Admin → Credentials and the template picks them up. Nothing secret ships in a template.
The workflow document (flowdrome.workflow.v1, 2 node types)
{
"schemaVersion": "flowdrome.workflow.v1",
"id": "",
"name": "Telegram bot — inbound messages",
"version": "0",
"status": "draft",
"nodes": [
{
"id": "tg",
"type": "input.telegram",
"label": "Telegram inbound",
"category": "trigger",
"config": {
"token": "${credential.telegram.token}",
"baseUrl": ""
},
"position": {
"x": 0,
"y": 0
}
},
{
"id": "out",
"type": "utility.console",
"label": "Route to support",
"category": "utility",
"config": {
"message": "TG {{ $json.from }}: {{ $json.message }}"
},
"position": {
"x": 530,
"y": 0
}
}
],
"edges": [
{
"id": "e0",
"sourceNodeId": "tg",
"sourcePort": "output",
"targetNodeId": "out",
"targetPort": "input"
}
],
"triggers": [
{
"id": "t0",
"nodeId": "tg"
}
],
"meta": {
"snippets": [],
"source": "template-gallery",
"description": "SETUP: create a bot with @BotFather and paste its token (or a ${credential.telegram.token} reference) — then every message to your bot runs this flow. Test simulates one inbound message."
}
} Generated from the verified demo corpus — this exact document seeds and runs on a fresh Flowdrome. Raw JSON: telegram-bot-inbound-messages.json.