In October '26, FlowSharp shipped 23 features, 88 improvements, 20 security updates, 5 design updates, 6 integrations.
October 18, 2026
External participants, complete: designed in the flow, followed from the case, replying from a dedicated public page.
October 18, 2026
External participants can fill in requested information from the portal; the Flow Agent shows when it is working; guide cross-references fixed.
October 18, 2026
External participants receive their links and reply from the public portal; sturdier transitions and task completions on every channel; pre-1.0 cleanup; installation profiles for the SaaS.
October 17, 2026
Skip and Confirm for information requests, AI under control (consent to platform providers, registry on by default, human-only fallback), terms of use, retention, faster Process Maps.
October 16, 2026
Unambiguous numbers in rules, an organization currency and the foundations for external participants to work on cases.
October 15, 2026
Cases unique across all versions, schedules resuming with the right checks, work queues honored and imports without surprises.
October 14, 2026
Confidential data protected everywhere, instant analytics even at large volumes, sample cases ready to work on.
October 13, 2026
Visual previews on cards, fast case history even on the longest cases, tracked support access.
October 11, 2026
Required license, roles and plan at a glance, easier-to-find Process Maps.
October 10, 2026
Your plan, always at hand.
October 10, 2026
Faster events under load and reliable exports even at large volumes.
October 9, 2026
Plan features and limits, consistently applied.
October 9, 2026
Traceable sensitive actions and clearly marked partial results.
October 8, 2026
Consistent cases, protected confidential data and aligned procedures.
October 8, 2026
Your installation license, in one panel.
October 7, 2026
Reliable human fallback and identifiable assistants in history.
October 7, 2026
The flows you really use, at the top.
October 7, 2026
Security updates to third-party libraries.
October 7, 2026
Assistants can import maps and Solutions.
October 6, 2026
Clearer design and everyday work.
October 6, 2026
More consistent flow design from agents too.
October 6, 2026
Security updates to third-party libraries.
October 6, 2026
A second assessment for uncertain cases, with a person as fallback.
October 6, 2026
More reliable forced transitions, verifiable event deliveries and failures traceable in history.
October 5, 2026
Create with AI builds the flow before your eyes: the structure first, then the details of each phase.
October 5, 2026
System One and System Two now have consistent names throughout the interface and guides.
October 5, 2026
Copilot and Create with AI are now more reliable: the proposal is checked and fixed before saving. If something is off, the Copilot sees it and fixes it with one click; Create with AI no longer loses the work done so far and lets you try again.
October 4, 2026
Cases awaiting start confirmation are now easy to find, have a deadline, and can be rejected with a reason. A case created by an external assistant on a flow that requires confirmation no longer stays out of sight: a dedicated filter finds it, a badge on the flow shows how many are waiting, a configurable deadline warns or rejects it automatically if nobody decides in time, and whoever can start the flow can explicitly reject it with a reason — without deleting it.
October 4, 2026
Who did what is now visible in case history, even when automation is the one acting: an action taken through a connected assistant (MCP) now shows who asked for it and which assistant, not just "System"; starting a case through an external automation key shows the key's name, not the case's assignee; entering a phase because a queue slot freed up shows "WIP release" instead of attributing the action to whoever closed the previous case; a vendor administrator temporarily operating inside the organization for support shows "FlowSharp Support", not a technical code. Existing history rows stay as they are: the new labels apply from this release onward.
October 3, 2026
Transitions protected while a phase is still being entered, safe retries for integrations, a warning on overly generic AI prompts, scheduled items re-checked against a new version — plus more robust inbound webhooks, more reliable email sending, and more resilient map import on repeated attempts: an item that is still completing entry into a phase can no longer be moved by a second attempt that lands at the same instant (REST, extension and MCP all get a retryable error, with how long to wait); REST and MCP assistants can now declare which phase they think they're starting from, so a retry after an uncertain network outcome never risks moving the same item twice; an AI task with an empty prompt or no placeholder at all now gets a warning — in the task panel and at flow publish — that calls attention to what gets sent to the model; a scheduled item that rebinds to a newly published version is now re-checked against the creation gates (work-in-progress limit, uniqueness, data, title): if the new version doesn't pass them, the item stays on its original version instead of starting under a configuration that wouldn't have passed those checks. The inbound webhook bandwidth budget now follows the bytes actually received, not the sender's declared header, and an early rejection closes the connection right away; SMTP sending now retries the other addresses of a dual-stack server when the first one refuses the connection; importing a Process Map with a requestId now holds up better when an attempt gets stuck for too long or hits an error right at the end.
October 3, 2026
Security hygiene, Process Maps and human fallbacks: protection against requests to internal networks now also covers cloud metadata addresses that had slipped through and domain names that resolve to them under the on-premise exemption; a dedicated cap on previews requested by MCP-connected assistants; the notice about scheduled cases waiting for an operational flow is now visible on the Kanban board and in the flow view too; Jev Assistant diagnostics also show up during an actual case run; a human fallback open because of a technical error can go straight back to automation; wiring or unwiring a flow in a Process Map requires management permission on that flow; map import has a «Preview» button that shows the report without writing anything, and can now declare a request key to be safely retried without creating a duplicate map.
October 3, 2026
More webhook security fixes, and interface improvements: webhook signatures now carry a timestamp that prevents reusing them later, an organization can no longer saturate inbound webhook bandwidth with a few very large deliveries, an installation without a configured external address works correctly again, the Users page flags Super Admins, and the Designer blocks saving on an invalid number.
October 2, 2026
Security pass: an independent audit reviewed the whole codebase and this release incorporates its fixes — SuperAdmin accounts, cross-organization links, n8n configuration, and webhooks.
October 1, 2026
Inbound and outbound webhooks: an external system can trigger a FlowSharp event by calling a dedicated address, without API keys, and FlowSharp notifies connected systems when an event happens, with signed calls.