Every FlowSharp release, feature, improvement, and security fix.
October 31, 2026
MCP tools and the Flow Agent now describe fields with the catalogue's own words: the "help next to every field" programme is complete. The Flow Agent answers usage questions with the guide chapters again, and "Create with AI" shows when it ignores event subscriptions proposed by the model.
October 30, 2026
Help next to every field in the administration pages and on the Legal hold reason too; AI flow building and the Flow Agent now know the field catalogue. Three fix batches from the testers' third round: secret variables no longer end up in assignees, event updates and scripts follow the same document rules as the API, and redaction placeholders never become real data.
October 29, 2026
Help next to every field in Process Maps, Saving, SOPs, the Library, the user, profile and license pages, the participant portal and the less obvious filters of Cases and Tasks. Plans change too: FlowSharp AI credits in every plan, AI tasks and flow generation everywhere, your own providers from Optimize, included tutor sessions and FlowBrain coming soon.
October 27, 2026
Help next to every field in the Designer and on the flow and case pages too: phase inspector, flow settings, every task type, catalogue, monitor, new process, import and PDF. Parameters that can only be set via the API are now documented and shown in the task panel.
October 27, 2026
Help next to every field in Settings too: AI providers, integrations, keys, email, notifications, solutions, organisation, governance and documents. In dialogs the first Esc closes the window again, not the tooltip.
October 26, 2026
Help next to every field, from Events to task details and KPIs: clear texts in Italian and English with a link to the right section of the guide; the Events page gains a Home button and the external-events wizard explains how to configure inbound webhooks.
October 26, 2026
More precise privacy, more confidential logs and streams: erasure touches only what you specify, rectification no longer writes placeholders over data, script logs no longer reach external agents in clear, and revoked sessions lose their live updates immediately.
October 25, 2026
Variables really work in tasks, and Webhook secret credentials are sent only when needed, stay hidden in logs and do not come back in responses.
October 25, 2026
More privacy for case data: n8n execution details protected, participant contacts no longer needlessly hidden from the AI, plainer MCP errors and a read log that holds up under heavy load.
October 24, 2026
The Webhook call log no longer shows credentials and confidential data, not even on those already saved, and the Designer warns you when you put a password in an address or confidential data in the title.
October 23, 2026
Safer events in the Designer: no publishing toward missing events, invalid payloads without useless retries, warnings when a copy listens to the same events; no AI-generated description unless you ask for it.
October 23, 2026
A more reliable engine (evaluations after waits, deadlines, data changes, loops between flows), event subscribers with Connector and readable emails, "New event" in four steps and a tidier Management area.
October 22, 2026
The conversational agent reaches external channels, security alerts and data breach register, data access right for MCP keys, fixes to the Designer and analytics.
October 21, 2026
Conversational profiles for participants, data subject rights and an explanation of every decision taken by AI.
October 19, 2026
Sensitive fields per list element and antivirus check on documents.
October 19, 2026
External participants polish after the first demo: clearer portal, more consistent case detail and Designer.
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
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 6, 2026
Clearer design and everyday work.
October 6, 2026
More consistent flow design from agents too.
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.
September 30, 2026
They're called cases now: the thing that moves through a flow is no longer called an "item" but a "case", across the interface and the guide; and global search gets more precise.
September 30, 2026
Global search refined: "Search" moves to the last row of the menu next to the arrow that collapses it, also finds the Guide and What's New, shows each flow once and explains why a result showed up; in "All Items" the filters are searchable by typing.
September 28, 2026
Stronger in the details: a more consistent engine and human fallback, more precise AI diagnostics, a more accessible Designer with events one click away, clearer items and permissions, and tidier What’s New and Solutions.
September 28, 2026
More accessible human fallback: reasons available on hover and clearer keyboard controls.
September 27, 2026
Dependency batch: third-party libraries and the build/CI pipeline updated to the versions that were safe to take right away; no visible change in everyday FlowSharp use.
September 27, 2026
Fourth tester round — validation, contracts and interface: the generated code for a phase with a very long name no longer breaks the save, the Data Schema now rejects rules it cannot keep instead of silently dropping them, the data-conflict message points to the fix that actually works, a change that alters nothing no longer leaves a false trace in the history, a script with the wrong setData() argument fails right away instead of pretending it worked, and automatic tasks finally say what they decided and who carried them out; a case always tells you where it comes from — manual, API, an MCP assistant, the Flow Agent, an event, a sub-process, a scheduled start or sample data — including the Origin card and the history, the "Archive" dialog says what stays, deleting a folder that only holds disabled or archived flows explains what to do, and task-type names are consistent everywhere, with the right verb for a skipped or failed task.
September 27, 2026
Fourth tester round — AI, MCP and documents: converting a manual decision to Jev now carries over the phase's form and warns when the source phase does not evaluate rules on its own; uploads with missing or extra bytes are rejected right away with a clear message, «Item documents → Active» lists real documents only, and inactive uploads can be deleted, by hand or automatically after 7 days, without leaving leftovers behind; starts from external assistants ask a person to confirm, assistant and integration errors distinguish a missing case from a completed one, AI spend is attributed to whoever started the case; AI diagnostics become consistent — the same AI provider in execution, detail, diagnostics, publishing and import, warnings shown the moment you configure, the real cause of an AI failure in the history, and the connection test recorded in the log.
September 26, 2026
Fourth tester round — engine and Designer: rules wait for the phase's tasks, tasks see freshly written data, typed values passed to sub-flows, numeric fields consistent with your language, Esc closes one window at a time, Jev scores become levels from 1 to N, stricter protection for internal addresses, scheduled cases on a suspended flow start on the published version.
September 25, 2026
Third tester round: Saving Challenge numbers without hidden projections, integrations and scripts that no longer fail silently, stricter protection for internal addresses and confidential fields.
September 25, 2026
Tasks speak the language of work: eight types with icons, in the order you think about a process, and a panel explaining what each one does.
September 24, 2026
Ready to ship: image promotion with stronger guarantees, consistent What’s New in every installation and a Jev conversion that never rewrites halfway.
September 24, 2026
From human to assisted decisions: prepare a Jev decision from a manual task, retain human review for uncertainty and inspect document context before automating.
September 24, 2026
More control over data and decisions: concurrent drafts protect your edits, documents stay consistent with their case, and history makes interventions, waits and events easier to follow.
September 23, 2026
Sturdier under the hood: consistent, accessible dialogs across the app, more reliable map import and export, Italian numbers never misread, and a What's New that tells you whether a version is already out or still being tried.
September 23, 2026
Restricted folders stay restricted, always. Removing the last access rule no longer reopens a folder to everyone, the side doors flagged by the security audit are closed, and an activity log that fails to write now stops the operation instead of pretending it succeeded.
September 21, 2026
The building block of the marketplace: a process map now travels whole, with the real flows inside and, if you want, sample data to see it come alive right away; and the security doors left open on restricted folders are now all closed.
September 21, 2026
A correctness release: numeric form fields no longer change what you type, chains of automatic steps no longer stop half-way in silence, and a sub-process that ends always unblocks whoever is waiting for it.
September 20, 2026
A polishing release: the Flow Agent can be switched off per organization, the history says when a transition came from an event held back by the WIP gate, and seven small visual defects reported in September are closed.
September 17, 2026
A platform release, so FlowSharp only starts when it can really work: at boot it checks that the database is up to date and says so clearly if it isn't, document reading runs in an isolated process that cannot block the service, and the PDF reading engine has been updated.
September 16, 2026
More control before publishing and more traces after: publishing warns about sensitive data and placeholders left by an import, the activity log now covers a flow's draft life too, and events received while an item waits in a queue are all applied, in the right order.
September 15, 2026
Per-folder flow permissions: decide folder by folder who can see, work on and administer flows and their items, with three levels and rules inherited down the tree, enforced everywhere: interface, integrations, assistant. Plus, in the Library, extracted text can be corrected by hand and a document can be shared with an expiring link.
September 15, 2026
A consolidation release: assistants and integrations see of flows only what their role allows, WIP limits are no longer silently rounded, and configuration errors speak plainly: Webhook task credentials never appear in answers to agents, a badly written WIP limit is flagged while editing and publishing, a script trying to read the Library where it is not supported stops with a message instead of writing empty values; literal Library search, assistant chat usable from the keyboard.
September 14, 2026
What's New reads one month at a time, the Library browses as cards, and Settings are searchable: the What's New page has a month menu with a summary by type of update; Library documents can be shown as cards with a preview; a box at the top of Settings finds the right section by name or description. Under the hood FlowSharp moves to Node 24 and refreshes its core libraries.
September 13, 2026
The Flow Agent assistant becomes an always-at-hand bar, on-premise updates run with one command that really verifies, and cost baselines follow the map across all its versions: a bar at the bottom of every page opens your chats with the assistant; self-hosted installations update with update.sh or update.ps1 and know at once if something is wrong; baselines stay valid when the map changes version, open from the map list and land in the PDF with the challenge.
September 13, 2026
Confirmations inside the app, organisation language in the administrator's hands, sharper warnings in the designer and maps: "are you sure?" questions are no longer browser windows but app dialogs, in your language and with the risk level visible; the organisation language is chosen in Settings → Branding and drives AI summaries, e-mails and notifications; the designer warns immediately when two phases share the same event code and maps flag disabled processes.
September 13, 2026
Activity log, protection of historical data, legal hold, account defence and sessions under control: administrators see and export who did what, case history and the log can no longer be altered through ordinary means, a case or a process can be put on legal hold with a reason, repeated sign-in attempts lock the account and every web session can be listed and revoked. The same version brings thirty fixes from September testing, a reorganised sidebar and a profile photo.
September 11, 2026
Document Library with folders and per-folder permissions, redesigned expression picker, estimated costs in the AI call log: shared documents are organised in folders, each with its own read or manage permissions for users and roles; in the designer, properties are explored level by level and the Library is browsed by folder; every recorded AI call shows what it cost.
September 10, 2026
Work queues that lose nothing, confidential data handled with warnings instead of blocks, and an AI call log: an event reaching a queued case is applied when the case leaves the queue, flow designers see right away where confidential data goes out to automations and models, and every AI call can be recorded and reviewed by administrators.
September 10, 2026
Full close-out of September's verification round: sessions with a ceiling that truly applies everywhere, shareable exports with no secrets and addresses preserved, document search that reveals nothing about protected files, scheduled items that no longer skip their initial checks, Event configuration errors that are finally clear, and text extraction diagnostics.
September 10, 2026
Security polish after 0.87.0: webhook JSON bodies no longer have template forms that escape protection and every configuration error shows up right away, the browser extension can no longer mix up two connections, and automatic alerts never go out without their configured credentials.
September 10, 2026
Stronger sign-in security, a browser extension that renews itself, a safer and more comfortable Designer: sessions now have a maximum duration and logging out closes every web session, the browser extension link no longer expires silently, Webhook tasks are validated before you can even save them, and the app loads faster.
September 8, 2026
Stronger security, simpler everyday work: a hidden risk in automated scripts is closed, confidential data stays protected across events and flow fields, and documents, the Library, the Designer, Kanban and the extension all gain concrete refinements.
September 7, 2026
Diagnostics and usability: document uploads that reveal nothing to those who shouldn't know, a keyboard-navigable Library, and a "Preview" that appears only where a preview truly exists.
September 7, 2026
Operations without surprises: interruption-proof extension linking, Event tasks that always tell the truth, an event log that respects visibility, and a task detail identical from every door.
September 6, 2026
Integrity and protections: confidentiality no longer gets lost on save, credentials survive edits, events never copy restricted data, and every invalid configuration gets a clear no instead of a silent fallback.
September 5, 2026
Full portability and data that never gets lost: exports and duplications carry everything, nested data never vanishes silently, numeric inputs are no longer silently "fixed", and legacy AI configuration meets a clear gate with the migration path written in the error.
September 5, 2026
Monitoring sees the whole family: unambiguous multi-version views, confidentiality that follows each item in its own version, diagnostics that never lie, and scope-proof agent tools.
September 5, 2026
Clear contracts, nothing lost: free drafts with strict publishing, a Document trash with guided restore, errors that speak plainly, and a complete audit of automatic rules.
September 4, 2026
Provable trust: deletions with verifiable proof, crash-proof extraction delivery, a hardened AI boundary and credential-free exports — a release entirely dedicated to security and reliability.
September 1, 2026
Certified erasure: deleting a tenant now truly deletes its files from storage too, with a grace window and proof of erasure.
September 1, 2026
Fixes from field testing: the Monitor now spans every version of a flow, and Document fields survive new versions intact.
August 31, 2026
Friction-free storage activation: extended compatibility with legacy S3-compatible providers, provisioning available straight from Diagnostics, and configuration verified at startup.
August 31, 2026
Document storage hardened: an independent security review of the new document subsystem, with every relevant issue closed before production activation.
August 31, 2026
Documents join your processes: contracts, reports and attachments are uploaded straight from forms, with versions, preview, quotas and a grace period — on S3-compatible cloud storage governed by FlowSharp.
August 28, 2026
Your installed base gets itself in order: the new Diagnostics finds work stuck on never-configured automations and unblocks it, privacy protections survive copies and versions, and item creation speaks the language of your process instead of JSON.
August 28, 2026
Items get a real title and AI plays by your rules: the title is visible everywhere, searchable and composable from a template — even AI-generated once data is complete; empty automations no longer claim success; and what reaches AI models is decided per flow, protected by default.
August 27, 2026
Reorganized settings, guides one click away, and summaries that admit their age. The Management section becomes Settings with a readable order, every page gains a question mark that opens the right guide chapter in its own window, and the AI Summary stops presenting itself as current when something important has happened in the meantime.
August 26, 2026
Process times tell the truth and stuck phases become visible. "Time per status" no longer mixes completed stays with ongoing ones, and phases where cases are stuck — instead of disappearing from the panel — now show how many they are holding. Plus: actions that name the process they act on, a localized canvas, and the place where agents will live.
August 26, 2026
Sensitive data stays sensitive and the numbers tell the truth. An indicator that would reveal one person's data now stays hidden for everyone, impossible durations no longer distort time and cost — and you can see how many were excluded — and processes that wait for several tasks to finish now publish without workarounds.
August 25, 2026
Rules now see the whole flow: "wait until every task is done" patterns finally work, placeholders resolve in every task type, event-driven processes publish without false alarms — and the guide, accessibility and error messages take a leap forward.
August 24, 2026
The flow list scales and diagnostics tell the truth. /flows loads families in pages with server-side search; Data diagnostics flag unresolvable references, default rules carrying conditions and Sub-flows without a destination (with no more false alarms); a rejected save shows a clear banner with phase and rule; procedures and guides get real Markdown typography.
August 24, 2026
A wave of tester-driven fixes. Flow import applies the same rules as the designer, time metrics become credible again, the flowchart PDF really shows the arrows without wasting pages, clicking an activity opens its card, and an accessibility pass makes Profile, OAuth revocations and the MCP tool catalog readable with a screen reader too.
August 23, 2026
Documentation becomes the source of truth again. A brand-new guide chapter on the Flowchart, every chapter realigned with the real product, technical references regenerated from the code and first-administrator setup fixed: what you read now matches what the product does.
August 23, 2026
The Flowchart becomes a document. Download the flowchart as PDF — cover, paginated diagram with cross-page connectors, legend and the "Who does what" cards of every phase — and the people who run the process open it read-only instead of the old map.
August 23, 2026
Quick fix for the Flowchart. The "Expected output" field of tasks now saves as expected: in 0.85.0 saving the flow rejected it as an unknown field.
August 23, 2026
The Flowchart. Next to the designer comes the documentation view of the process: phases laid out automatically, large boxes with their activities inside, who does what and the expected result of each activity, in three layouts of your choice. The first step of the "process documentation" track.
August 23, 2026
The interface polish wave. Twelve refinements in a single pass: dark mode becomes readable everywhere, unread notifications truly stand out, the compact sidebar breathes, and a series of details — favicon, autofill, reveal eyes — stops misbehaving.
August 22, 2026
Errors that tell you what to fix. The Designer fork rejects reusing a request with different content, import errors list duplicate keys and the phases involved, export refuses documents with broken references, and OAuth errors speak the OAuth contract.
August 22, 2026
The cycle's final hardening. OAuth errors with the right code, administration of dynamically registered clients with deactivation, traced client metadata diagnostics, automations that reject never-interpolated templates, and an MCP section that calls things by their name — with a state readable by screen readers too.
August 22, 2026
Metrics that declare what they measure and an audit trail that says who acted. Every dashboard number explains its basis, unit and population; alongside structural automation comes the period's observed automation; the trend shows since when data exists. The audit trail records who acted and through which channel, and alert telemetry reflects real deliveries — with one less personal data item in payloads.
August 22, 2026
Process maps that don't lose pieces and health that tells the truth. Deleting a process wired into a published map is now blocked with the list of affected maps; a node whose process is gone gets flagged; archived maps are truly deleted when nothing uses them; a never-checked map no longer looks healthy; and the map list gains real search and pagination.
August 22, 2026
Lists that don't lie and AI assistants with two more tools. Changing page really skips a whole page, totals stay stable while you scroll, search reaches the task calendar, and counts respect your visibility. MCP assistants gain task listing and data updates with the same rules as the APIs, and read-only users are no longer offered impossible actions.
August 22, 2026
Truly immutable versions and data protection that follows the family. Reactivating a version used by items creates a new draft instead of reopening it; an archived process can't be republished or shared by mistake; duplicate copies exactly the chosen version; and a new sensitive classification on the parent process also protects child elements already generated in other processes.
August 21, 2026
What you save is what runs. Designer rules, events and forms are verified at the source: a default rule can no longer hide a condition that would be ignored, an "on event received" rule must point to an actually subscribed event, an import no longer creates nameless event definitions, and form schemas are checked against what the runtime can interpret. Plus, Human phases gain the Rules tab for event-driven waiting.
August 21, 2026
Events delivered all the way through and clear answers even in edge cases. The event engine always executes every action of an event, in the right order and without duplicate effects; an overly wide calendar range is rejected with an explicit message, deleting an initiative from the Plan never leaves orphaned elements, and integrations see more while revealing less.
August 21, 2026
No more pieces lost along the way. An imported or saved process arrives whole or is rejected with the exact list of what to fix, and retries on element creation can no longer return the wrong result.
August 21, 2026
The Designer warns you before, not after. Non-editable versions open read-only, events are always chosen explicitly, and real-time diagnostics flag impossible links, unreachable outcomes, and unsupported forms before they become a problem.
August 21, 2026
Sensitive data protected across all versions, transparent AI Summary. Sensitive-field classification applies to a process's entire version family, history shows what was actually protected, the AI Summary communicates clear states, and integrations get new tools with explicit risk labels.
August 20, 2026
MCP profiles with tailored permissions, duplicate-free events. Each integration can have its own profile with a dedicated address and explicit permissions, OAuth authorization respects the profile's boundaries, and event delivery is protected from duplicates even when things go wrong.
August 19, 2026
OAuth-ready MCP connectors, more transparent events. Remote connectors can authorize without keys in URLs, versioning preserves event actions, and telemetry now distinguishes receiving an event from actually applying an effect.
August 17, 2026
More reliable events, clearer rules. The "deadline first, then the event" rule now covers every delivery scenario, event-linked actions are thoroughly checked before going live, and SLA durations respect a uniform maximum limit.
August 17, 2026
A security-focused update. Two-step verification for administrators, secure one-time alert confirmations, stronger and rotatable at-rest encryption, sign-in links and keys kept out of logged URLs, and less sensitive data retained in history.
August 15, 2026
Clearer rules, alerts that actually arrive. One draft per version family, events and timeouts applied in the order they really happened, SLA warnings delivered to owners through alert policies, and an export that flags plain-text credentials.
August 14, 2026
The 0.83 release is now more robust in real-world cases. Retries, versions, timeouts, and SLAs produce reliable outcomes; export and duplication preserve the design; Events gains recovery tools; compare and Analytics costs reflect the same runtime reality.
August 13, 2026
Flows without hidden dead ends, operational recovery under control. The designer blocks processes that cannot reach a final state, automation stalls become visible alerts, cross-install invitations survive retries and crashes, Admins can recover an item through MCP, and the extension downloads preconfigured from Settings.
August 12, 2026
Edit a published flow without losing anything, and an engine that always tells the truth. "Save" on a published flow now creates a new version with all your changes, in one step. Sensitive data follows the data wherever it is copied, engine failures become visible and recoverable, the Events page is complete, and the operational views show what is really happening.
August 9, 2026
Your flows travel, your work stays safe. Duplicate a flow with one click, import it from file, paste or URL, share it across installations with an expiring link. And every change made from tabs, guides or services is now visible to the designer save: no more silent overwrites.
August 9, 2026
A smaller, verifiable distribution. No feature changes: the backend now contains production dependencies only, migrations have a dedicated image, and every release publishes image inventory and provenance.
August 8, 2026
Every channel, the same rules. UI, API, import, AI generation, agents and child flows now write into the engine through the same funnel: one grammar for durations, identical validations everywhere, event schemas enforceable on demand, explicit data inheritance in child flows. And the browser extension gets a makeover, in your brand colors.
August 8, 2026
Reliable versions, honest baselines. Creating flow and Process Map versions is now concurrency-proof — no more duplicate numbers, even under bursts — and past duplicates are cleaned up for good. Savings proposals declare when the design changed underneath them, with guided regeneration.
August 7, 2026
Time tells the truth. A scheduled item no longer looks "already started": the start date appears only when the process actually begins, and metrics, SLAs and sorting follow suit. This release also brings real per-visit analytics, a rule validator with no code execution in the browser, and more predictable API contracts.
August 7, 2026
Real governance on published flows. A published flow is now immutable — you change it by creating a new Draft version — and each item's history records the exact design version behind every event. Misconfigured rules are stopped at publish time, AI agents follow the same policies as the UI, and Process Maps gain full link management.
August 7, 2026
Four targeted closures. Activity sequences now resume reliably from every channel — including AI agents via MCP —, completed items no longer accept changes even under concurrency, the scheduler no longer produces false conflicts, and the activities' technical configuration stays on the server. No migrations: a simple upgrade.
August 7, 2026
Honest responses, sequences that never stall. Second stabilization wave: concurrent saves have a single winner, activity sequences always resume — even after a crash —, scheduled items start when you actually move them, event rules now work on human phases too, and the n8n contract says the same thing everywhere: UI, snippets and guides. No migrations: a simple upgrade.
August 6, 2026
The crash-safety guarantees become complete. An independent audit combed the previous release for remaining gaps — and this release closes them all: deliveries that can no longer be lost, durable resumes, no superseded executor able to overwrite fresh work, and dangerous configurations blocked before they reach production. No migrations: a simple upgrade.
August 5, 2026
The engine becomes crash-proof. Seventeen coordinated changes close critical races and crash windows: events that can no longer be lost, outcomes with a single winner, always-recoverable creations, atomic escalations. With one declared breaking change for n8n integrations.
August 4, 2026
Foundations refreshed. A focused update of the database access layer, shipped on its own: cleaner transaction behaviour under load and ecosystem security patches. No change to everyday use.
August 4, 2026
Nine decisions closed, no grey areas. The ambiguous behaviours accumulated over the past weeks — who receives an event, what a script knows about the child flow it created, when an item is genuinely concluded, how views are ordered at equal priority — were decided one by one and implemented together.
August 3, 2026
The work-item lifecycle, with no blind spots. Events raised by activities and scripts now genuinely fire and start the listening flows, an unreachable child flow is stopped at publish instead of remaining a promise, every outcome — succeeded, failed, skipped — appears in the item's history, and a failed activity can be retried, skipped or resolved with a tracked note. Plus three security hardenings from an independent external audit.
August 2, 2026
What the flow declares now genuinely holds. Waiting for data, work-in-progress limits, response times, required fields on completion, priority: all of these could be configured, and then nobody — wholly or partly — enforced them. Waiting now genuinely suspends the phase's work and clears the moment the data arrives, a queued item no longer moves as if it were active, escalation creates the work in the destination phase, and required fields apply identically on every channel.
August 1, 2026
Automatic rules now do what the designer promises. A rule written exactly the way the help, the hints and the assisted generator show it saw no data at all and stayed silent forever, with no error and no trace. Rules now genuinely read the item's data, numeric comparisons understand numbers that arrive as text, a field never filled in no longer sends anything forward, and when a rule does not fire the history says why.
August 1, 2026
Confidential data stays confidential everywhere, and everyone sees only what is theirs. A safeguard is worth as much as its least guarded exit: a field could be hidden on the item's page and appear in the clear in the indicator computed from that very field, and a read-only role could see no flow in its own list yet still learn names and volumes from another screen. Confidentiality now follows the data wherever it is recomputed, visibility is the same from whichever direction you arrive, and connections with external assistants work the way the standard expects.
July 31, 2026
The rules you write are the rules that hold. Some conditions the designer offered — "greater than or equal", JavaScript rules written the way the assistant suggested, fields in the very form the AI recommended — were accepted on save and then silently ignored by the engine. Now the places where you write and the places where your process runs speak the same language: deadlines have a single grammar, a badly written value is rejected right away instead of vanishing, and if a rule errors at runtime you find it written in the item's history.
July 30, 2026
An item that enters a phase gets its work, and your colour reaches all the way down the sidebar. An item that changed phase through a deadline arrived at its destination without receiving that phase's tasks: the flaw showed up on no screen, and at worst it left the item open forever, waiting for work nobody would ever create. Your brand colours, which started showing in the previous version, now reach the surface you look at most. And the designer stops wasting your time over codes, warnings and phases you want to remove.
July 30, 2026
What you configure shows up, and what the product promises holds. Your brand colours now actually colour the interface, instead of saving with no effect. Deadlines no longer spin silently. The designer tells you the truth about what happens when you mark a phase as final, instead of hiding the controls and letting the diagram tell a different story. And the key for connecting an AI assistant no longer travels inside the address.
July 29, 2026
Uploaded logos are visible again, and the rules hold outside the interface too. Uploading a logo really did work — the file was saved — but nobody could see it back: that is why the defect stayed invisible for so long. Alongside come six security fixes, work that no longer sits stuck in a queue, and a long list of rules the product promised without enforcing them outside its own screens.
July 29, 2026
Outbound communications work again, and your data stays inside your organisation. Since 25 July every call to an external system was failing before it even started: notifications, alerts, links between installations and email sent through web services. This version repairs them. Alongside come an important privacy fix on the AI assistant connection, protection for the configurable AI engine, and a long list of refinements from tester feedback.
July 28, 2026
The interface only promises what you can actually do. Commands the server would reject no longer appear: those who don't design processes see them read-only, and the two near-identical "force" buttons for changing status — with very different effects — have become a single, clear command about what it respects and what it overrides. On top of that, email forms fill in without surprises and several server responses now tell the truth.
July 28, 2026
An item closes when the work is done, and reconciled names stay reconciled. The last phase of a process can have work to do, and until it's done the item is not complete: before, it was considered closed the moment it got there, and the counts said "done" with the checks still open. On top of that, a hand-written name linked to a real person no longer comes back on its own.
July 27, 2026
Hand-written names now link up and move from wherever you are looking at them. The previous version brought assignee reconciliation; this one closes the two gaps that opened right after it. The clickable counts in that panel led to an error or an empty list, because the assignee filter rejected exactly the hand-written names. And an item could only be reassigned by rewriting that name everywhere it appeared: now you move one item at a time, from its own detail page.
July 27, 2026
Names typed by hand as assignees now link to real people, in a single move. Writing "Tiziana" before Tiziana exists in the directory is a legitimate way to sketch a process, but as long as that name stays a label the work produces no notifications or reminders. There is now one place to see the placeholders left, understand where they appear, and link them to a user.
July 26, 2026
Updating FlowSharp no longer signs you out, and no update starts without a verified backup. Anyone with the page open during a release was often disconnected and saw a row of red errors appear. Underneath there was a real defect: a momentarily unreachable database was reported as "session expired". Now the page waits and recovers on its own.
July 25, 2026
Email now goes out from your own channels, and whoever forgets a password no longer has to call the administrator. Until yesterday all mail left through a single channel, configured once for the whole installation: every organisation received notifications from a sender that wasn't theirs. Now each one configures its own sending channels, with a fallback order if the first doesn't answer.
July 25, 2026
Work assigned to a name that doesn't exist yet no longer disappears in silence. You can still type a person's name as the assignee before you've even created their user — that's normal while you sketch a process — but now the system tells you, instead of leaving that work with no alerts and no reminders.
July 24, 2026
When two people work on the same thing, nobody silently loses their work any more. Items, flows and process maps now notice if someone else saved in the meantime: instead of overwriting, they warn you and reload.
July 23, 2026
Screens refresh on their own and drafts stay where you left them. No risk of saving a draft on the wrong record, views that immediately reflect what changes in real time, and searches and filters that do what they promise.
July 23, 2026
Data that's harder to corrupt, configurations that don't fail silently. Entity references no longer duplicate over a stray space or a capital letter, a non-existent assignee no longer leaves work hanging on nobody, and views that promised an option now actually give it to you.
July 23, 2026
Every flow measures what matters. KPIs computed on your data with formulas, thresholds and alerts; daily history, goals with automatic evaluation and trends with forecasting — all computed in-house, your numbers never leave the platform.
July 22, 2026
The flow table is yours. Columns from your flow's fields, reliable server-side sorting and saved views: one shared with the team, one personal to you.
July 22, 2026
Your flow now has a registry of its fields. Declared contract and fields observed from real use live together in the new Data Schema tab; reorganized settings and a Form AI that starts from your data structure.
July 22, 2026
"Load more" no longer skips anything. Lists that load in blocks stay correct even while others are working on the same data.
July 22, 2026
Everyday refinements: dark theme, sidebar, documentation anchors and the overview image. The details you meet every day.
July 22, 2026
Truly unique flow names, dashboard numbers that add up, actions that state what they will do. You can no longer create two flows that look identical, the total at the top of the dashboard matches the per-flow breakdown, and "Delete" and "Design" state their effect before running.
July 22, 2026
What you see in the list is what you filter, search and export. The status filter no longer hides items from other flow versions, search behaves predictably with special characters, and the CSV file contains exactly the rows in front of you.
July 22, 2026
Process maps no longer lose work and protect published versions. Edits made during a save are no longer overwritten, back-to-back saves no longer trigger false conflicts, and a published map is now truly immutable.
July 22, 2026
Safer external links and more reliable incoming data. The entity link can no longer run code on click, and a flow's start data is now checked by type too.
July 22, 2026
Governance of external domains is now truly enforced, everywhere. When you deny a provider the block is respected — even YouTube or Google Drive — and the check covers every content type, not just embedded frames.
July 21, 2026
Assigning a manual task is now one clear gesture, with no surprises. A single assignment field in the designer, the notification reaches the right person, and dynamic assignees really work.
July 21, 2026
Notifications respect your organization's time zone, and the Archive gets a safe permanent delete. Allowed hours in the right zone (with daylight saving) and protected permanent deletion.
July 21, 2026
More consistent localization and lots of usability and accessibility polish. Notifications speak the recipient's language, your chosen language is remembered, and several screens become clearer and sturdier.
July 21, 2026
A more reliable, context-aware AI assistant, a calendar that actually shows your items, and editable event names. The Copilot answers questions, understands what you're editing, and no longer breaks drafts.
July 21, 2026
No more "fake success": invalid input is stopped, not swallowed. Malformed JSON, invalid data schemas, subscribers with no destination and wrong WIP limits are now blocked with a clear message. And events get a readable name separate from the technical key.
July 21, 2026
Search and filters that scale, with no rows silently disappearing: on items, tasks and events, search now works across the whole archive — no more hidden caps hiding older records. And embed-domain governance now recognizes content that already exists.
July 20, 2026
More security control, more reliable data, no lost work: decide which external domains are allowed in embeds, maps no longer overwrite each other across tabs, flow names and codes become unique, and the Automation Plan stops counting phantom savings.
July 19, 2026
FlowSharp works better on your phone, and videos are back: the main pages now truly adapt to small screens — no more clipped buttons or cut-off tables — and videos embedded in task guides play again.
July 19, 2026
Updated technical foundations: modernized, more reliable PDF reading, a test platform unified on the latest generation, and a documented roadmap for upcoming upgrades. Same app, stronger underpinnings.
July 19, 2026
A faster interface and two new control levers: the app loads less code at startup, Admins can unblock a stuck item with "Force transition", SuperAdmins can permanently delete a deactivated tenant, and Analytics now shows saturated phases.
July 19, 2026
An engine that holds together even under failure: if external automation is unreachable, tasks fail cleanly — with alerts and fallback paths — instead of staying "running" forever; lists and dashboards are lighter; and every operation can be traced in the logs from click to webhook.
July 18, 2026
Deep cleanup under the hood, simpler deployments: less code to maintain means a more solid product — gone is a never-active authentication layer (and its configuration requirement that complicated installs), along with orphaned components and 230+ dead translations. And the last hardcoded strings now speak your language, dates and amounts included.
July 18, 2026
A lighter app with errors always visible: startup is much faster (initial bundle -64%), the flow detail page is smoother on long lists, and when a load fails you see it right away — with a "Retry" — instead of a list that just looks empty.
July 18, 2026
A faster engine, same behavior: every state transition makes far fewer database round-trips and pre-transition checks run in parallel; the alert engine drops repeated queries and always prioritizes the longest-waiting work.
July 18, 2026
Safer and faster: a last loophole toward the internal network closed in integrations, cache cleared on user switch, responsive login even under load and quicker transitions. Plus, the n8n snippets generated by the app now work on the first try.
July 18, 2026
Data security and a more reliable engine: items are readable only when their flow is visible to your role, sensitive fields are masked in exports and AI channels too, non-blocking AI tasks no longer lose their verdict, and published Process Maps become immutable. Plus a round of polish on the Automation Plan and AI Assistants.
July 17, 2026
New "Management" area and Automation Plan: settings now open in a unified full-width area with a side menu and an overview home; automation becomes a real "Plan" linked to Analytics, with a bar showing how far you are from your goal; and your organization's logo and colors can be personalized on your own.
July 17, 2026
Stricter permissions and a more accessible app: integration credentials and the automation backlog are now restricted to the right roles, the Copilot truly applies final-state outcomes, What-if no longer creates duplicate initiatives, and the sidebar, filters and dialogs are fully usable with keyboard and screen readers.
July 17, 2026
Reliability and isolation: external systems connected to your flows no longer receive duplicate deliveries when an internal job is retried, and data isolation between organizations is now guaranteed "by construction" at the database access layer.
July 17, 2026
AI item summary: every item now has a short AI-generated verdict (a rating plus two or three sentences) that accounts for history, data, human notes and score, refreshes on state change and can be turned off per organization, flow or single state; plus human notes recorded in the audit trail and one-click copy of the data JSON.
July 15, 2026
From What-If to the automation backlog: the ROI & What-If report now shows saved time alongside costs and lets you push tasks straight into the Automation Backlog with residual presets and duplicate detection; plus colors on demo statuses, restore for archived procedures, and timing and layout fixes.
July 15, 2026
Quality and polish: the Copilot can set flow-level SLA and expected path and its edits are always applicable; Saving Challenges gain a clearer export, readable amendments and localized notifications; plus accessibility and security fixes.
July 14, 2026
Formatted procedure preview in tasks too: the procedure section cited by a task is now rendered — headings, bold and lists — instead of raw text.
July 14, 2026
Procedure viewer with markdown: a procedure version's content, opened from the timeline, is now rendered — formatted headings, bold and lists instead of raw text.
July 14, 2026
A clearer What's New page: the "What's New" page now speaks the product's language — only features, improvements and fixes useful to whoever uses FlowSharp — and the whole history has been revisited with the same criteria, for uniform, professional communication.
July 13, 2026
Federated identity — refinements: small robustness and security improvements after completing the three phases.
July 12, 2026
Federated identity (Phase 2) — cross-install: an external consultant or collaborator can now operate across different FlowSharp installations (companies with separate systems, not just tenants of the same installation) with a single sign-in. The hosting company invites by email; the invitee accepts from a dedicated page and can then switch between their own workspace and the hosting one with one click. Revocation always stays with the hosting company: the moment it is revoked, the external session drops immediately, even if already open.
July 12, 2026
A wave of fixes from tester reports: more reliable designer saves, status duplication without "ghost routing", tighter control over admin overrides of automatic tasks (with protection against late n8n responses), and documents/PDFs finally rendered properly in task guides — including PDFs on Google Drive.
July 12, 2026
Real time reaches everywhere: after item detail and notifications (v0.43.0), now Monitor, lists, dashboard, ticker and analytics move on their own — and a freshly created item shows up instantly in the lists of whoever is watching, whatever channel it is born from (form, API, event, sub-flow). With the live connection active, polling thins out and lightens the server.
July 12, 2026
Human work that’s left waiting stops silently disappearing: multi-channel alerting with escalation is born. An assigned task or an unanswered "human" status generates reminders via email, webhook or event, following a configurable policy (a ready-to-use default is already in place), respects the tenant’s quiet hours, and can be acknowledged without logging in via a signed link or straight from the bell. Any flow can also be excluded from statistics and have its own retention. Contains a database migration.
July 11, 2026
The interface comes alive: items, tasks and notifications update in real time, with no page reload. Whoever is looking at an item sees transitions, tasks and history move on their own while the engine works; the bell rings instantly; the Chrome extension cockpit refreshes as soon as the entity changes. And tasks become first-class events: completion and failure can now drive notifications and automations.
July 11, 2026
The Saving Challenge becomes contract-proof: the frozen baseline now carries a SHA-256 fingerprint that makes the integrity of the numbers provable, a simulator lets you try fees and parameters before proposing the contract, and every monthly consolidation arrives as a notification. List and detail tell the accrued story at a glance: cumulatives, chart, measured vs estimated savings. Contains a database migration.
July 11, 2026
The Automation Backlog is born: the "automation candidates" of your process maps stop being a suggestion that gets lost and become tracked initiatives — with costs, planned date, owner and external reference — governed by a dedicated flow all the way to the measured verification of the savings achieved. The "measure → automate → prove" loop now applies to the single initiative too. Contains a database migration.
July 11, 2026
A fixes release, with one structural improvement: the historical cost of an activity no longer changes retroactively if you later edit its configuration. It also hardens the n8n integrations (production send, import, execution tracking) and PDF printing (never again a silently incomplete document). Includes a database migration (a cost snapshot on activities).
July 10, 2026
A fixes-only release: a round of API and UI hardening. It closes situations where you could silently lose work (a repeated request with different data, two operations racing on the same item) and some mismatches between what the interface shows and what it then acts on (flow list, map printing, event roles). No database migration.
July 9, 2026
A fixes-only release: a full sweep of bugs collected across v0.36–v0.39. It mainly improves the Process Map lifecycle (versions, archive, restore, "deleted" maps), removes situations where you could lose work in the designer, adds a dedicated Admin force-transition to unblock stuck items, and polishes several UI details. No database migration.
July 9, 2026
Two big process-governance features. Ideal path and deviations: declare a flow’s “happy path” and FlowSharp flags on its own the items that stray from it. Exception routes: timeouts, WIP limits and SLA breaches can move an item into states the operator must not be able to pick by hand (Escalation, Overdue, Out-of-WIP), with automatic SLA escalation to a dedicated state.
July 7, 2026
New: manual work with estimated costs on Process Maps — manual procedures and documents declare what they cost, the Cost lens compares them with flows, and Diagnostics tells you what to automate first.
July 7, 2026
PDF export polish after first field tests: the graph actually shows, phases get a clear visual hierarchy, AI tasks are described correctly.
July 7, 2026
Quality pass on maps and designers: no duplicates in flow linking, the Diagnostics spots flows with no activator, warnings for incomplete event activation — and the Flow Agent now links the guide.
July 7, 2026
Tidier Process Map: compact toolbar, map import, the Flow Agent lands on the designers — plus an MCP security fix.
July 6, 2026
Execution times visible in the item history, always-unique task codes, snappier worker.
July 6, 2026
Real-time flow diagnostics in the designer, n8n payload halved and safer, AI generation that always produces publishable flows.
July 5, 2026
QA fix batch for n8n and the designer: clearer import, idempotent snippets, connector test aligned with the real contract, a more honest designer on errors.
July 4, 2026
Quality and security hardening: more tenant-isolation tests, agent Data Shield refinements, updated in-app guide.
July 4, 2026
"Secret" variables for credentials and tokens, plus Process Maps list refinements.
July 4, 2026
QA fix batch: more robust filters and parameters, more consistent designer, more reliable dashboard, clearer Chrome extension.
July 4, 2026
Consolidation release: anti-duplicate reliability, consistent access control, and clearer WIP.
July 3, 2026
Polish for the freshly released live Process Map.
July 1, 2026
Dynamic thresholds in rules, sturdier validations and a tidier What's New.
July 1, 2026
Flow and global variables now also resolve inside embed content.
July 1, 2026
The {x} variable picker is now on every field that accepts expressions — assignees, event fields, embeds and more.
July 1, 2026
Technical release: a much lighter backend Docker image and image builds moved to GitHub Actions — faster, lighter updates.
June 30, 2026
Variables get much easier to use — the {x} picker respects your selection, fields show the resolved variable value, and the variables editor is cleaner. Plus a round of quality and security fixes.
June 29, 2026
Bug fixes: correct WIP response after transition, SPA routing, WIP copy on new flow version, clearer validations and process map cleanup on flow delete.
June 29, 2026
Smarter flow list: filter by status, see only flows relevant to your role, and the WIP APIs now cover the queue and saturated phases.
June 29, 2026
WIP is now visible: badges and actions right on the item and the board, so you grasp at a glance what is queued and why — plus an alert for updates you have not read yet.
June 28, 2026
Meet the Copilot for process maps: describe how to change the map in words and the AI builds it — always with a preview before applying. Plus search in the Documentation.
June 28, 2026
Process Maps come alive: maps now see the real event links between flows, you can create draft flows straight from a map, and jump between map and flow in one click — plus a new panel to edit map nodes and a rewritten product documentation
June 28, 2026
Flow import/export is more transparent: errors and incomplete references are now visible, no longer silent.
June 26, 2026
The in-app guide becomes clearer, along with a round of internal improvements for greater reliability.
June 25, 2026
Sturdier foundations: a single source of truth for flows and tasks, more robust saves and more reliable releases
June 24, 2026
Data-contract diagnostics in the designer + data governance extended to the Flow Agent
June 23, 2026
Consistent start requirements across every channel + shared "when to use a flow" between the built-in Flow Agent and external MCP agents
June 22, 2026
Sequential task execution, Flow Agent start form, drag&drop task reorder
June 22, 2026
AI never runs on empty data, per-phase force transition, entity naming
June 21, 2026
Data Shield on nested fields, richer rule builder, readability fixes
June 21, 2026
Resilient automation: retry failed tasks, per-state iteration cap, advanced data-gate rule
June 21, 2026
Data governance suite: shielding, minimization, data-gated states, readable audit
June 20, 2026
Read-only access for non-editors, stricter API validation, cleaner designer edges and dark-mode fixes
June 19, 2026
Clean portable flow export/import format and the ability to delete user accounts
June 19, 2026
Faithful flow import (routing rules + extension/agent fields), extension reliability, and read-only design action
June 19, 2026
Consistent required-data validation across all create channels, enforced entity reference, and persistent list filters
June 19, 2026
Automation trajectory visible immediately, save confirmation, and extension stability on SPA CRMs
June 19, 2026
Consistent, re-importable flow export/import and stricter extension settings
June 19, 2026
Scheduled item start, working state timeouts, MCP start-events, stronger API-key security and import/export fidelity
June 19, 2026
Reliable task open/reassignment tracking, observable events, more accurate metrics, and security hardening
June 19, 2026
Task completion data is now saved & validated, consistent required-field checks, and UI fixes
June 18, 2026
Items no longer get stuck on automatic steps, stronger API/MCP security & privacy, paginated lists, fuller audit trail, and admin unblock for AI tasks
June 18, 2026
No more blank dashboard, safer n8n form, admin unblock for stuck AI tasks, and flow publishing via MCP
June 18, 2026
Security hardening (extension token scope, CORS, HSTS) and extension robustness fixes
June 18, 2026
More intuitive task editor, dark-theme readable charts, and multi-tenant correctness in the Chrome extension
June 11, 2026
Sturdier AI flow generation, tenant-language demo data, persistent uploads, and several Chrome extension improvements
June 9, 2026
Smarter item search in the Flow Agent, consistent errors between REST and MCP, plus interface fixes
June 7, 2026
Demo flows with invalid IDs now save + aligned action icons in the flow list
June 7, 2026
Flow designer: faster state creation, safe delete, connectors that avoid nodes, and rules reachable from the diagram
June 6, 2026
Completed-items history in the extension + link an entity after creation + branding logo
June 6, 2026
Extension panel refinements + page-aware Flow Agent
June 6, 2026
Work on items from a popup that reuses the real web UI (SSO) + optional item title
June 6, 2026
Operational side panel for the Chrome extension (mini-cockpit) + per-tenant disconnect
June 6, 2026
Chrome extension: connection and page recognition fixes
June 4, 2026
Critical deploy fix (production crash)
June 4, 2026
Delete mistakenly-created items, list-view action parity, opt-in strict trigger
June 2, 2026
Reusable AI Assistants, AI output mode, ROI & What-If report, copy n8n node
June 2, 2026
Security hardening, flow-scoped API keys and Flow Agent polish
May 28, 2026
Event-triggered flow activation, item provenance, portable import/export
May 10, 2026
Visual flow progress, related items, activation mode
May 9-10, 2026
n8n Native Bridge, task views, deploy with SSL
May 9, 2026
AI copilot, analytics dashboard, calendar view
May 2-6, 2026
Version comparison, multi-AI, MCP Server, CI/CD
Apr 19-20, 2026
pg-boss, dashboard quick-start, multi-tenancy