Use case · Bots
Bots that answer with a graph
A bot is an event pipeline: an update arrives, something decides what it means, a few nodes transform it, and a send node answers. The Bots project is the smallest honest version of that pipeline, and it is public.
What you build
Every graph is a set of small Python nodes wired by ports. These are the pieces this track puts together.
Receive updates
Start from a chat update, a webhook payload or a scheduled trigger. Telegram Get Updates and HTTP Route both turn an incoming event into a value your graph can act on.
Route commands
Compare text with String nodes, branch on the result and send each command down its own chain. A group keeps one command handler together on the canvas.
Reply and notify
Telegram Send Message takes a chat id and text; Email Send and HTTP Post cover other channels. Deliveries and failures appear in the same run log as the rest of the graph.
Build it step by step
The same five moves work for every graph: add nodes, wire ports, set parameters, run, then save or share.
Open the Bots project
Bob’s Bots project has two public graphs, Echo and Price Feed. Start with Echo and notice how little a working graph needs.
startprintAdd a reply channel
Drop Telegram Send Message from the Notify category and wire the text output into its text input. Set the chat id as a parameter or feed it from the incoming event.
telegram_send_messageRead the update
Add Telegram Get Updates or an HTTP server in front so the graph receives real events. The update payload arrives as a dictionary you can inspect with Print.
telegram_get_updateshttp_serverRoute by command
Use Starts With or Contains to detect a command, then Branch to split the chain. Each branch ends in its own reply so a typo gets a useful answer.
starts_withbranchKeep the token out of the graph
A token placed in a node parameter becomes part of the graph structure. Prefer the run container environment, especially before a graph becomes public.
Run, save and publish
Run the graph and follow the events in the console. Save it into the project, then snapshot it into the store if you want to sell an open or closed copy.
Example you can open now
This example is seeded on the public site. Open the graph in the editor to inspect it, or take a copy through the store when a fork is not enough.
Telegram Echo Bot
A small open graph that connects an incoming message to a reply node. Import it into a project, connect your token through the environment and extend the command routing.
How it runs
The API creates the graph’s container and the orchestrator runs the nodes inside it. A long-polling bot stays in its node while messages arrive; each emitted event still travels through the ports like any other value. The console receives stdout and per-node events until the run ends or you stop it.
- Each graph runs in its own Docker container, started by the API.
- Nodes are fetched at the exact version the graph pins.
- stdout and node events stream to the editor console while it runs.
Build a bot for your own chat
Copy the Echo graph, replace Print with your delivery node, and add one route per command. The graph stays readable as the bot grows.