Back to the changelog

• Feature

  Assistant chat in the participant portal

  When the organization has turned on the conversational agent, the portal form shows "Chat with" and the assistant's name: the external person can write naturally, the assistant collects the requested information and proposes the outcome of the task their link authorizes. A proposal is applied only after their explicit confirmation, protected data stays protected and replies are always plain text. In the case detail, "Opened N times" becomes "Link accesses: N".

• Feature

  WhatsApp and Telegram with n8n

  The same conversations can come from WhatsApp and Telegram (and, read-only, from SMS) through an n8n workflow that delivers messages to FlowSharp with a dedicated key: if the same number appears in several cases, the person picks the right one. The installation kit includes two ready-to-import workflows, one for Telegram and one for WhatsApp, with a step-by-step guide: they arrive switched off, you connect them to your channels, reconnect the credentials and turn them on when you are ready. They handle case selection, confirmations and retries; on Telegram the person is recognized by sharing their own contact. In notification policies you can now state who they are for (internal users or participants) and use WhatsApp and Telegram to invite participants with a signed invitation that guarantees where it comes from, provided the contact has a phone number with its international prefix; on WhatsApp the invitations use the message template approved by your organization. Documents are uploaded from the portal: on the channel the person gets an invitation to use their link.

• Feature

  Handover to a person

  In the conversational profile you decide when the assistant stops: when the person asks for an operator, uses a keyword, makes no progress for a few turns or exceeds the maximum number of turns (up to 40). The external task moves to "Awaiting a person", the link is revoked and the internal assignee (or the administrators) gets a notification. The handover applies to the whole participation: the assistant stops on portal, WhatsApp, Telegram and SMS together, closing a chat or creating a new link does not reactivate it and whoever follows the case gets a single notification; the person can still complete from the portal any other forms that remain open. Keywords also match double spaces and an explicit request to speak with a person also works when it comes with a document. New profiles suggest 3 turns without progress; already saved ones now use the threshold they had set. From the case detail, in the Conversations section, you read the exchange, see the proposals linked to the history and close the conversation.

• Feature

  Security alerts and data breach register

  FlowSharp now watches risk signals on its own: too many failed logins, oversized exports, support impersonations, mass deletions. Every alert reaches administrators as a notification and an email, with no personal data in the text, within minutes and only once per burst; thresholds are set at installation level and a wrong setting disables only the alerts, not the rest of the engine. Settings now include the data breach register required by the GDPR: detection, nature, data subjects, measures, authority notification and communication, with the 72-hour countdown and export. The platform provider can report a breach straight into the organization's register.

• Feature

  Read tracking

  Every document download is recorded in the audit log, once a day per user and document. For flows that need it you can also track who opens cases, with an option in the Designer.

• Feature

  MCP keys and case data

  Every MCP key and every OAuth consent decides whether the client may read case data. New keys start without that right: the client sees flows, phases, states and dates, but not the contents, and can still create cases and complete tasks. You enable it from Settings or your Profile, with a notice on where the data goes.

• Improvement

  More predictable assistant replies

  The assistant's replies never contain links to sites outside the installation, nor file names with extensions that coincide with a domain (for example ".zip" or ".md"); in that case the person receives a clear message and can try again. With the data shield on, the assistant only uses the data of the contact who is writing, and the new calls show up in the AI log as "Participant conversation".

• Improvement

  AI transparency

  Templates can include the "AI-generated content" notice in the organisation's language with a single placeholder, and publishing warns you when a template denies the AI mark while reading AI-written fields. The guide includes a notice template for those who use AI towards people.

• Improvement

  Data Shield

  Placeholders for restricted data are recognised even when a client alters them (case, spaces, different brackets): on protected fields they are ignored instead of overwriting the real value. Verbatim copies of AI-written content, even made by a script, carry the "AI generated" mark into events and webhooks.

• Improvement

  Designer and conditions

  The AI Form panel opens above the toolbar and the Flow Agent bar, asks for confirmation when you close it with unsaved changes and, on a freshly added phase, applies the form to the draft without errors. The code of an already published phase no longer changes when you rename it: there is a dedicated button, with confirmation. For Webhook tasks you can declare the expected automatic outcomes. The condition editor knows field types: numbers, True/False and lists are saved in the right format, and a number written as "5.000" is flagged as ambiguous with the two possible readings. Existing rules do not change.

• Improvement

  Analytics

  With no completed cases, average duration, median and cost show "—" instead of zero, and comparisons between versions appear only when both have data. A publish warning flags automatic tasks with a per-minute cost, which is not measured today.

• Improvement

  Cases

  A double click on "Save data" sends a single request.