English EN
Go to JetBot24

Release 26.10.2

October 12, 2026

New

  • New templates. Arithmetic, comparisons, logic, conditions, text functions and nested function calls now work inside {{ }}. In the builder blocks, expressions are highlighted, and when there is an error, a hint shows what to fix. More in Expressions, Function reference and Errors and limits.
  • A new help center. The platform help center has been written from scratch in four languages, with a light and a dark theme — screenshots included.

Changes

  • Trial Pro turns into full Pro. When the trial period ends and there is enough money on the balance, the Pro subscription is renewed automatically. More in Trial period.
  • A new limit on creating bots. The limit of 1000 bots per account has been removed. Instead, you can create no more than 50 new bots per day. More in The list of bots and creating a bot.
  • Deleting a bot with its lists. When you delete a bot, the platform asks whether to delete the lists linked to it as well. More in The bot's lists.
  • "Start time step". In the booking settings, the time step setting has been renamed to "Start time step" and has a clearer description: it is the interval between the start times offered, not the length of a service. More in Booking rules and free time.
  • sendMessageToQueue is deprecated. The API method will keep working until December 1, 2026. Use sendMessage in new integrations — see sendMessageToQueue.

Fixes

  • Inline buttons in VK after a timer or a delay. Such buttons used to stop working. The fix applies to messages sent after the release; in earlier messages the buttons still work only in the current block, as before.
  • The "Prodamus" block stopped silently. If Prodamus did not create a payment link — for example, because of a too generic name like "Service" in the "Purpose of payment" field — the customer got nothing. Now they get an error message, and the reason for the refusal is shown in the block's execution log. The "Purpose of payment" field now has a hint. More in Prodamus.
  • Renaming a scenario with a long name. The rename menu used to not appear.
  • Moving a mini app to another project. The app used to not be moved.
  • Invalid block connections. Some block types logically cannot be connected to each other, but the platform allowed it. Now such connections cannot be created.
  • Moving a bot with a list to another project. An empty, non-working copy of the list used to be moved. Now the list is moved in full if it is not used anywhere else in the old project; otherwise only its structure is moved. The platform warns you about this before moving. More in What happens to lists.