24 September 2026

Insert field, on every chat-flow message

New. Every Message card in Chat Flows (and the escalate/handoff message) has an Insert field button under the text. It opens the CRM field list — Deal or Lead, Contact, Company — with search, and a click drops {{CODE}} at the cursor. At send time the code is replaced by the record's value.

Placeholders were already substituted at send time ({{NAME}}, {{RESPONSIBLE_NAME}}, any field of the lead or deal); what was missing was a way to discover them. New in the same release: {{CONTACT_*}} and {{COMPANY_*}} resolve in flows too, including inside a WhatsApp Business template's parameters, and a question step's answer can be inserted as {{LABEL}}. A flow that is not attached to a lead or deal offers its own collected answers instead of CRM fields.

Attach the file stored on the deal or lead

New. The attachment picker of a chat-flow message step (and of an Automation) has a third source next to upload and link: From CRM field. It lists the file-type fields of the flow's lead or deal; picking one attaches the field, not a file. At send time WASync reads the file stored on that record and sends it, so each customer receives their own contract, invoice or CV. A multiple field sends all its files, five per message at most, in the step's order.

If the field is empty on a record, or the file cannot be fetched, the message text still goes out without the file and a short note is written to the record's timeline. Nothing fails silently and nothing is sent half-resolved.

Values written the way a person would

Improvement. Wherever a person reads a CRM value — flow messages, robot messages, Automations text, AI prompts, timeline comments, notifications — it is now formatted: list fields show the item's label instead of its id (a customer had received "282, 284, 286"), dates read dd.mm.yyyy (with hh:mm for date-time fields), money fields read "100 EUR", yes/no fields read Yes/No in the message's language, file fields read "1 file" or "3 files". Values written back into Bitrix24 by a flow (set-field steps, router conditions) stay raw on purpose.

Robot panel: custom fields show their name

Fix. In the robot panel's field picker, custom fields (UF_*) showed their technical code instead of their name. Bitrix24 reports the code as the field's title and keeps the name in a separate label; the picker now reads the label. The inserted placeholder is unchanged, so saved automations keep working.