Changelog

Most of 1.7 is in the builder. Steps all look the same now, it’s easier to use data from earlier steps, and the panels stay where you put them. We also reworked the pages you use to set up a bot, so going from a token to a live flow takes fewer clicks.

• One card for every step. Each step in the builder shows its icon, its name (click to rename), a short summary of what it does, and one labelled row for each way out, so labels no longer overlap. Problems show as one line on the card along with the fix, and errors leave from their own port at the bottom.
• Data from earlier steps, by name. Data from earlier steps shows as pills named after the step, like Welcome › Sent text. Type {{, click Insert data or drag a pill in to pick from a list grouped by step, with each value’s type and its value from the last run. Unrenamed steps are numbered, like Send message 1 and Send message 2. You get a warning if you give two steps the same name.
• A builder that fits your screen. You can resize or collapse the nodes and settings panels, and the builder remembers how you left them. On phones they open as bottom sheets. Click a node in the palette to add it, use Add next on any free port, and press Tidy up (Shift+Alt+T) to lay the flow out left to right in one undo step. Nodes covers each step.
• Configuration on one page. Your test and production bots, your secrets and where each secret is used now share one page. A missing secret has a fix right there, and links from Flows, Bots and the builder’s Checks take you straight to the setting you need.
• Templates. Cards show what starts each flow, just like the Flows list. The preview reads top to bottom with branches nested inside, and adding a template only asks for API keys your bot doesn’t have yet. With no bots, Create a bot starts one with the template already picked.
• New bot and first run. The new bot dialog tells you the token becomes your test bot, shows token errors under the field, and lets you start from a template or a blank bot. The first-run wizard has a step rail, a clearer card once your token is verified, and makes clear that going live turns the token into your production bot.

Fixed: disconnecting your production bot now takes the bot offline, so no page can show it as Live when it can’t answer. In the first-run wizard, retrying a failed deploy no longer deploys twice, and picking another template replaces the flow instead of adding to it. Errors on the sign-in and sign-up forms are clearer, and a failed request now shows a readable message instead of “API error 400”.

When a bot didn’t answer the way you expected, you used to dig through a table of runs. From 1.6, Executions in your bot’s menu lists every message from the last 7 days, one row per message, and explains each one. Reading the execution log walks through it.

• One row per message. See who sent what, which flows ran for it and how long it took. New messages appear on their own.
• Failures explain themselves. A failed message shows which step failed, what OpenAI, Telegram or the website you called said, and whether the person got a reply, with a link straight to that step in the builder.
• Why not the others? For any message, see why each other flow didn’t answer: it only answers /order, it ignores commands, or a flow above it answered first.
• Search and filters by text, sender, flow, status, bot and time, all kept in the page’s link so you can share a view.
• From Test all to the log. Click a row in Test messages to open it in Executions, and replay a logged message through your drafts with Replay in Test all.
• The Bots page (it was the Dashboard) now shows whether each bot is live and on which release, changes you haven’t deployed, messages and failures in the last 24 hours, and flows that need fixing. Your plan’s usage is one line at the top.

Fixed: a step whose Error output isn’t wired to anything now counts as failed, since the person got no reply. It used to show as a success. The builder also no longer shows “Unsaved changes” when you’ve only opened or clicked around a flow.

Until now, every flow whose trigger matched a message ran at once, so a “reply to any text” flow and a /order flow could both answer the same message. From 1.5, your flows form an ordered list on the bot’s Flows page. Each message is checked from the top, and the first flow that matches answers it. How flows work has the details.

• Ordered flows. Drag flows to set which one answers first. A Continue switch lets a flow run and still pass the message on to the flows below it, for example to log every message.
• Commands stay with command flows. Message flows now skip /commands by default (the new Ignore commands switch), so a catch-all flow never swallows your commands.
• Checks as you edit. Errors and warnings show on the Flows page and in the builder’s new Checks list, each with a one-click fix, such as Move above it for a flow that would never be reached. A flow with errors can’t be run or deployed.
• Test all. Test every flow together on your test bot, for as many messages as you like, and see which flow handled each one.
• Deploy bot, History and roll back. Deploy the whole bot at once and see exactly what changes first. Every deploy is saved as a release you can roll back to in one step, and you can take the bot offline from History.
• Executions now has its own page in the bot’s menu.

Your existing bots keep working: whatever you had deployed became release v1, in the order the flows were created.

The first release of Gramflow. Build a Telegram bot by dragging nodes onto a canvas, wiring them together, and deploying — no server to run.

What’s in 1.0:

• A visual builder with 16 nodes — triggers, actions, logic, data, and AI. See the full node reference.
• Templates — clone a proven flow (welcome bot, FAQ, AI chat, feedback collector, group welcome) into your account in one click.
• Streaming AI replies from the Generate Text node, using your own OpenAI, Anthropic, or Google key, with conversation memory across turns.
• Interactive buttons that branch the flow, and a wait-for-input step for back-and-forth conversations.
• TEST and LIVE environments — build against a sandbox, then deploy to your live bot in one click. Bot tokens are encrypted at rest.