v0.99.36
November 14, 2026
Install FlowSharp as an app, close repeating stages early, decide on tasks knowing you are looking at the right data, and work with settings protected from concurrent edits.
-
Feature
FlowSharp as an app
You can install FlowSharp from the browser on phones, tablets and computers and open it from its own icon, in a dedicated window. In your Profile, under FlowSharp app, you'll find the Install the app button or step-by-step instructions, including for iPhone and iPad. The icon menu opens My tasks, Cases and Flows right away, and on computers the icon shows unread notifications. The app keeps only interface files on the device, never case or people data: without a connection a page explains this. Permissions and session duration stay those of your account, and the portal for external participants keeps working as before, always fresh from the network.
-
Feature
Closing a repeating final stage early
A final stage that repeats over a list can now close the case as soon as a condition is met, for example at the first approved document, without waiting for the other items. You set the condition in the Designer's Loop tab, with the guided editor or with code. The case outcome is the one from the last recorded check, work not yet done is closed in an orderly way and a parent process receives the outcome as with any other closure.
-
Improvement
Cycle conditions step in at the right moment
The conditions for leaving a repeating stage are now checked after each completed item and before starting the next one, even when the work is done by automatic scripts. The case leaves as soon as the condition is true, without calling external services or assigning activities for items that would be discarded right away. In parallel mode the check happens after each group of items completed together. A rule written in code that fails no longer stalls the cycle. Cases with a stalled cycle have a label in Table and Kanban, «Change status» warns you when you leave a cycle that is still open, and the cycle page shows skipped activities next to completed items.
-
Improvement
Repetitions recognizable everywhere
Every activity of a repeating stage can be recognized outside the case detail too. Notifications show the activity title and «item N of M» in the recipient's language, the browser extension shows the position and the outcome of the closed case, the conversational assistant tells individual activities apart and your external assistants can read iterations and visits. Integrations receive an identifier of the exact activity, so an automation completes precisely the right item. Confidential titles stay hidden from anyone not authorized.
-
Feature
Repeating stages with AI and in Solutions
Creating a flow with AI can propose repeating stages when you point to a list in the data, together with outcome texts and conditions to leave the cycle early. Solutions and new versions keep the full configuration of these stages.
-
Improvement
Process outcomes in lists and Analytics
In Cases and in the flow Monitor you'll find the Outcome column and two filters: one to search for an exact outcome, one to see cases with or without an outcome. The CSV export applies the same filters. In the flow's Analytics detail, the Process outcomes section shows how many closed cases have an outcome and which are the most frequent, counting confidential ones separately.
-
Improvement
More reliable task decisions
An activity marked as Failed no longer carries a decision outcome: you just write the reason in the note, and a rule such as «the outcome is approve» does not fire for an activity that did not succeed. Skip appears only when the activity allows it, and an open activity that cannot be skipped cannot be skipped through integrations either; an administrator or a designer can still close a failed activity as skipped, writing down the reason. If a colleague changes the activity or the case data while you are deciding, the dialog tells you and asks you to reload before confirming, so you don't approve on data you haven't seen and don't erase someone else's note. In the timeline, every data update shows which fields changed. «Edit flow» also no longer loses what you typed when someone else saved before you.
-
Improvement
Publishing warnings that prevent routing mistakes
When you publish, FlowSharp warns you when a rule reads an activity's outcome without checking that it was completed, when a failing automatic activity would still bring the case to a positive conclusion, and when a cycle condition would also be true with an empty list. The warnings don't block publishing. In the rule builder, picking a human activity's outcome automatically adds the «activity completed» condition, which you can remove.
-
Security
Sensitive settings protected from concurrent edits
When two people edit the same setting, FlowSharp no longer silently overwrites the other person's work. This applies to events and subscribers, schedules, incoming webhooks, users and roles, keys for external assistants, category and folder permissions, AI and email providers, allowed AI addresses and connectors. When someone else has saved before you, «Changed by another user» appears: with Reload you get your changes back on top of the updated values and you decide whether to save. Turning off a protection, such as a webhook signature or an event validation, asks for explicit confirmation. Saving a schedule without changing its timing no longer moves the next run.
-
Security
More robust data validation
Format rules written in event schemas, in incoming data validation and in request forms are now checked with an engine whose timing is always predictable. On save, FlowSharp points to the exact spot of an unsupported rule, for example those that look ahead or behind in the text, and accepts common forms that used to be rejected out of caution. A schema can contain up to 64 different format rules and received data can be nested up to 64 levels deep: beyond that, FlowSharp answers with a clear message showing the spot and the limit. Schemas saved earlier with forms no longer supported are not applied until you fix them: the guide explains how.
-
Security
Webhook addresses protected
The addresses of connectors and of event webhook subscribers are shown with their confidential parts hidden, administrators included: credentials, confidential parameters and the secret codes that services such as Slack, Make, Teams and Telegram put in the path. Recognition of confidential parts is more accurate and stays fast even on very long texts; when a text contains several addresses with credentials, FlowSharp hides it entirely. If you leave the address as it is, FlowSharp keeps the saved one; if it finds a credential in the parameters, it suggests moving it to an encrypted header. Addresses can be up to 2000 characters long and error messages no longer show the address. Automation initiatives and the other system flows no longer generate the AI Summary: no data sent to the provider and no credits used.
-
Security
Incoming webhook signatures with a timestamp
Incoming webhooks accept only the signature that includes the sending date and time, valid for five minutes: a request signed in the old format, without date and time, is refused even if the webhook doesn't require a signature. The webhook's latest receipts flag these requests explicitly, so you know which systems to update. The guide shows how to sign, including from n8n.
-
Security
Updated libraries
The libraries used by FlowSharp are updated to their current versions, with the latest security fixes.
-
Improvement
More reliable numbers and data
An integer too long to be stored without rounding is rejected with a message that names the field: write long identifiers as text. A field declared as integer does not accept decimals when validation is strict. Deadlines are calculated to the second and the Designer keeps the seconds. «Max iterations» with an invalid value no longer goes unnoticed: the Designer flags it, the history records it and publishing warns when a cycle is limited only by an expression. If a flow's data structure is not valid, starting it from outside is rejected with a clear message instead of accepting unchecked data.
-
Improvement
Clearer events
When an event does not start a case because one already exists for the same object, the event detail says so with the real reason. The object reference and the correlation value are compared regardless of extra spaces or full-width characters, also for waits already registered, while capitalization still matters. A data update rejected by validation names the fields involved. Choosing the flows to start with an event writes to the draft when the family has no published version and never changes archived versions. Non-representable characters and excessively nested data receive an explicit message, and incoming webhooks with a large body are checked faster.
-
Improvement
Refinements
Future deadlines in Table and Kanban read «in X». The script execution log is a list with time and message. «Force entry» appears only when the case is actually queued. The data JSON editor asks whether to clear or keep the properties you removed from the text. «+ New case» explains why creation failed. «Change status» no longer runs twice on a double click. In repeating stages, blocking activities of individual items no longer prevent changing stage, the condition builder no longer turns «All» into «At least one» without saying so, and the guide explains how to unblock a stalled cycle. In the Designer, the stage Behavior section has aligned switches and help next to each entry, and the data structure flags an invalid path right next to the field.