Skip to main content
FlowX.AI 5.11 is a SaaS release. New capabilities are available on managed (SaaS) deployments; self-hosted deployments will receive them with the next LTS release family.
Deployment models:
  • SaaS Managed FlowX cloud deployments
  • All Deployments Available in both self-hosted and SaaS
FlowX.AI 5.11 is a SaaS-managed release: FlowX handles deployment-level changes such as infrastructure, Kafka topics, and service configuration. This release turns Custom Agents into orchestrators that call FlowX workflows as tools and search knowledge bases agentically, adds per-Knowledge-Base embedding models with local embedders for personal-information content, and introduces document classification. It also extends response caching and subworkflow data mapping in the Integration Designer, moves document and notification templates onto the structured data model, and adds chat notifications, session ownership, and richer runtime audit to the renderers.

​
What changed since 5.10.0

What’s new?
🧰 Workflow tools on Custom Agents - Attach FlowX workflows as callable agent tools, with usage hints and tool-calling caps
🔎 Agentic knowledge base search and Show Reasoning - Query decomposition, relevance grading, and a reasoning summary in the run log
🧠 Per-knowledge-base embedding models - Pick an embedding model per KB and keep personal-information content on a local embedder
🗂️ Knowledge Base content lifecycle - Delete entries by metadata filter, structured failure handling, per-chunk timestamps
🏷️ Document classification - Train or import a classifier and route document pages in a workflow
💬 Conversational chat reply requirement - A conversational run that never replies to chat now fails with a clear error
✍️ Custom Agent instruction limit - The Instructions field is capped at 10,000 characters

​
Workflow tools on Custom Agents

Attach FlowX workflows as callable tools on a Custom Agent

Before 5.11: a Custom Agent’s tools were MCP servers, built-in tools, web search, and Knowledge Base retrieval. Now: you can also attach FlowX workflows as callable tools.In the Custom Agent node’s Tools section, add a workflow as a tool and fill the per-tool When should the agent use this workflow? hint that tells the agent when to call it. The agent calls the workflow like any other tool, passing arguments that match the workflow’s Start-node input parameters. A workflow with no input parameters cannot be attached. Each tool call starts a fresh workflow run whose output returns to the agent, and the child run is linked in the console log.

Documentation

See the Custom Agent node documentation.
SaaS

​
Agentic knowledge base search and Show Reasoning

Agentic knowledge base search and reasoning summaries

The Custom Agent node gains agentic knowledge base search and a Show Reasoning toggle.With agentic search on, the agent breaks a question into sub-queries, retrieves and grades results for relevance, and retries with reworded queries if the first pass finds nothing. It is better on complex questions and uses more model calls; a single pass with three sub-queries is the default. Agentic search never returns worse results than plain retrieval. Show Reasoning captures the model’s reasoning summary in the run and console log; the structured response and the chat reply shown to the user are unchanged.

Documentation

See the Custom Agent node documentation.
SaaS

​
Per-knowledge-base embedding models

Per-KB embedding models and local embedders for personal information

Knowledge Bases can now use a per-KB embedding model, and a KB that holds personal information can keep its content on a local embedder.Turn on Containing Personal Information on a Knowledge Base to enable a local embedding model, then pick one from the Embedding model list. Local embedders (for example a text-embedding-inference or Ollama endpoint, or any OpenAI-compatible endpoint) are configured as a single CUSTOM provider in the organization AI settings, with a free-form base URL and no API key. The embedding model is set before the first store and cannot be changed afterward. Non-personal-information Knowledge Bases use the organization’s default embedding model.

Documentation

See the Knowledge Base documentation.
SaaS

​
Knowledge Base content lifecycle

Delete entries by filter, structured failure handling, and per-chunk timestamps

The Update Knowledge Base node gains a Delete entries operation and structured failure handling, and retrieval results now carry per-chunk metadata.Delete entries soft-deletes chunks whose entry-level metadata matches a filter, in one store or across the Knowledge Base; an empty or match-all filter is rejected so a misconfigured node cannot wipe a store. When an update operation fails, the node’s FAIL branch returns a structured output with the operation, store, failure reason, and how many chunks were rolled back, and any partial changes are reversed. Retrieval results now include a per-chunk identifier and an ingestion timestamp.

Documentation

See the Managing Knowledge Base content documentation.
SaaS

​
Document classification

Classify document pages with a trainable ML model

FlowX.AI adds Document Classifiers: deterministic ML models that sort document pages into categories. Define classes, upload training data, and train or import a model, then route each page in a workflow with the new Document Classification node.The node runs the active model over a document, returns a predicted label and probability per page with a configurable confidence threshold, and flags low-confidence pages. A page-level failure does not fail the node.

Documentation

See the Integration Designer documentation.
SaaS

​
Conversational chat reply requirement

Conversational runs must reply to chat

A conversational (chat-driven) workflow must send at least one chat reply, either from a Custom Agent node with Send as Chat Reply on or from a Navigate in UI Flow node that completes the turn. A run that reaches the end without replying now fails with a clear error instead of ending silently.Learn more about chat-driven workflows. SaaS

​
Custom Agent instruction limit

Instructions field capped at 10,000 characters

The Custom Agent Instructions field is now limited to 10,000 characters. SaaS

​
Reusable functions in Integration Designer

Call reusable functions from Script and Condition (Fork) nodes

Reusable functions can now be called from Script nodes and Condition (Fork) nodes in the Integration Designer, not just from Business Rule actions in processes. Functions are referenced in the node’s JavaScript or Python and resolved at runtime from the app version’s function copies, including functions that call other functions and cross-app references. A Fork node resolves the references used across all of its branch conditions.For more information, see the reusable functions documentation. SaaS

​
Extended response caching

Cache POST REST, file-storage reads, and Mongo reads

Response caching in the Integration Designer now covers more operation types. POST REST endpoints are cacheable alongside GET, with the request body forming part of the cache key so different bodies cache separately. Read file-storage operations (LIST and DOWNLOAD) and read Mongo operations (FIND, FIND_ONE, AGGREGATE) are cacheable alongside SQL. Mutating operations are never cached.For more information, see the Integration Designer documentation.
SaaS

​
Subworkflow data mapping

Map data in and out of a subworkflow with input and output mappers

The Subworkflow node adds data mapping as an alternative to raw JSON. Turn on Enable data mapping to define an Input mapping per subworkflow start node and an Output mapping per end node, mapping individual data slices instead of hand-editing JSON. Output mapping does not apply to asynchronous subworkflows. Each mapping opens a mapper with a test action, and mappings travel with import, export, and clone.For more information, see the Integration Designer documentation.
SaaS

​
Email attachment filtering by extension

Filter email attachments by individual file extension

Email Trigger and Microsoft Outlook data sources now filter attachments by individual file extension instead of the five broad file-type categories. Choose the exact extensions to accept and to forward into a process. Existing category selections are migrated to their individual extensions automatically on upgrade, so current triggers keep working.For more information, see the Email Trigger documentation. SaaS

​
Structured data model for templates

Document and notification templates use the structured data model

Before 5.11: document and notification templates declared parameters in a free-form key/value Data model tab. Now: templates use the same structured data model as the rest of the platform.On the Data Model tab you define typed attributes with validations, sensitive-data and reporting flags, and references to project or library data types. On the Input Parameters tab you select which attributes the template expects. Values sent in the request are substituted for those attributes at generation time.

Documentation

See the notification templates documentation.
SaaS

​
Data model attribute validators

Validators on data model attributes

Data model attributes now support validators. Available rules depend on the attribute type and include Required, Min/Max Value, Min/Max Length, Pattern, Email Format, and Min/Max Items, plus currency-specific amount and code rules. Validators are stored on the attribute and apply wherever that data model is used, including project, process, template, and reusable UI template data models.For more information, see the project data model documentation. SaaS

​
UI Flow runtime audit

Audit UI Flow runtime activity

UI Flow runtime sessions are now audited in more detail. The audit log records workflow-instance runs, chat message sends, conversation list and history reads, and whether the Process Renderer performed a render or a start. Entries name the app and the workflow instance.For more information, see the audit documentation. SaaS

​
Cross-version export adaptation

Exports adapt UI templates for older LTS targets

When you export a project to an older platform version, UI-template features the target version cannot understand are removed during down-adaptation, so the export imports cleanly. This currently covers Process Renderer process-end event handlers and the Navigate To forms to validate setting.For more information, see Cross-version export and import. All Deployments

​
Platform and runtime improvements

Runtime access-control hardening

Runtime API requests are now authorized against the roles defined in the running build across start-process, start-workflow, task views, conversation history, and the public runtime API. Requests without a matching build role are denied, and enforcement is on by default. All Deployments

Theme import no longer duplicates system icons

Exporting a theme no longer includes duplicate copies of built-in system icons, and importing a theme no longer creates new ones. Duplicate icon copies that accumulated in earlier versions are cleaned up automatically on upgrade — no action is required. All Deployments

Unread-message badge and conversation search in chat

The chat floating action button gains an unread-message notification badge, with a themeable Notification Dot you can position in the chat style panel. The chat panel also adds search across conversation history, which filters conversations by a text query, highlights matches, and shows an empty state when nothing matches.For more information, see the Chat component documentation.
SaaS

​
Disable chat input on a condition

Make the chat input read-only with a business condition

The chat Input component can be disabled by a business-condition expression. When the condition evaluates true, the input becomes read-only with an explanatory tooltip, and any pending attachments and voice input are cleared.For more information, see the Chat component documentation. SaaS

Require form validation before a Navigate To action

A Navigate To action can now require selected forms to pass validation before navigating, matching how Start Process and Start Workflow actions gate on validation. This is available on web, iOS, and Android.For more information, see the UI Flows documentation. SaaS

​
Expired UI Flow sessions

A session-expired screen with a start-fresh option

Expired UI Flow sessions now show a session-expired screen with a start-fresh option instead of leaving the previous data visible in read-only form. Expired and unauthorized access is written to the audit log. SaaS

​
UI Flow session owner

Restrict a running session to a single user

A UI Flow can restrict a running session to a single owner. When Allow multiple editors is off, other users who try to open the session are shown an access-denied screen, and unauthorized access is audited. Newly created flows default to single-owner; imported and existing flows keep the previous shared behavior. A session-owner value type is available for permission-based hide and disable rules.For more information, see the UI Flows documentation. SaaS

​
Process Renderer process-end handling

Run a configurable action when an embedded process ends

The Process Renderer can now run a configurable action when its embedded process ends, using a new process-end trigger on event handlers. Configure what happens at that point instead of leaving the renderer idle when the process completes.For more information, see Process end handling. SaaS

​
Renderer improvements

Renderer performance and behavior

  • Batched enumeration fetch: renderers batch enumeration lookups into a single bulk request, cutting the number of calls when rendering enum-backed fields. Applies to web and mobile renderers.
  • Process-start loader alignment: the web renderer keeps the process-start loader visible until the first user task, matching the mobile SDKs. SaaS

​
Shipped by

This release is the work of the FlowX engineering team across backend, frontend, AI, infra, QA, and docs. It also belongs to the customers who told us what was broken last quarter. Thank you.

​
Deployment guidelines

FlowX.AI 5.11 is a SaaS-managed release: FlowX handles deployment-level changes such as infrastructure, Kafka topics, and service configuration. For component versions and infrastructure notes, see the 5.11 deployment guidelines.
Last modified on August 11, 2026