Flowable

Agents call tools to query data sources, call APIs and take actions, and tools can be attached to a whole agent or to one operation so a capability is only available where it is needed. Around the agents, cases and processes reach other systems through about 30 connectors, among them Salesforce sObjects, SharePoint documents, ABBYY document capture and Apache Camel, plus HTTP tasks, MuleSoft and Power Automate tasks, a service registry for REST services and an OpenAPI generator. External and A2A agents hand work to Salesforce Agentforce, Azure AI Foundry or any agent that speaks A2A.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/concepts/tools/index.htmlread 2026-10-12

Work runs on BPMN processes, CMMN cases and DMN decisions, and agents are steps inside them through the AI Agent task. The orchestrator agent coordinates several agents and outside APIs within a case. Each time the case changes it reads what the case allows, reasons about the best next step, and takes it or proposes it. Agent calls can run outside the database transaction, so a long model call does not hold up the case, and the case model decides which data each agent sees and where it may act.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/introduction/index.htmlread 2026-10-12

A knowledge base in Flowable Design turns policies, product documentation, FAQs and other content into a semantically indexed store. Content comes in from folder paths or uploads, is extracted and split automatically, and is embedded in Elasticsearch 8, an OpenAI vector store or a custom store, with tunable top K, candidate and similarity settings. Knowledge agents query it at run time, and the same knowledge base can serve processes, forms or a standalone search.

Sourcedocumentation.flowable.com/latest/reactmodel/knowledge-base/introduction/index.htmlread 2026-10-12

The orchestrator agent can be set to suggest instead of act, presenting its next step as an option in the case chat for a person to accept, and high stakes actions always wait for a human. User tasks, including a four eyes check pattern, put sign off wherever the case needs it. Guardrail agents check content before and after each model call, blocking prompt injection or hate speech, redacting phone numbers, emails and card numbers, and rejecting off topic or non compliant answers.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/reference/orchestrator-agent/index.htmlread 2026-10-12

Flowable holds ISO 27001 and SOC 2, and its cloud supports single sign on through OAuth and SAML, with Entra ID for identity and SSO on dedicated environments. Each agent sees only the data its task needs and can act only where the case allows, and agents exposed over REST answer only to user groups listed on the agent model. The Work MCP server enforces the same permissions and tenant scoping as the Work REST API, so an assistant can do nothing the signed in user could not. Flowable also runs a public trust center.

Sourceflowable.com/product/enterprise-cloudread 2026-10-12

Agents are audited by default at three levels. The basic level records each agent instance's start and end, status, definition, starting user, calling case and task. The low level exchange adds the operation invoked, the content sent to the model, what the user saw and the request and response tokens. For knowledge agents, the sources used and how closely each matched are stored as well, so retrieval can be tuned. Audit records sit in history tables apart from the running agents and are read in Flowable Control.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/concepts/auditing/index.htmlread 2026-10-12

An agent's context is the case it works in. The orchestrator agent reasons from the current case data and state and keeps its chat with users inside the case, so what it knows lasts as long as the case does. Other agents receive the input their operation defines on each call. There is no memory store an agent reads from one case to the next, such as what it learned about a customer last time.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/reference/orchestrator-agent/index.htmlread 2026-10-12

Flowable Cloud runs on Microsoft Azure with EU and US hosting as standard. Cloud Shared is a multi tenant service with logical data separation, while Cloud Dedicated gives each customer a physically separate environment with its own release schedule, dev, test and staging environments, VPN integrations and other regions on request. The same platform installs on premises or in a customer's own cloud with Docker, Helm charts or WAR files.

Sourceflowable.com/product/enterprise-cloudread 2026-10-12

Builders start from agent types, utility, knowledge, document, orchestrator, external, A2A, guardrail and evaluator, each a component they configure with their own prompts and operations. Any model in Flowable Design can be marked as a template so teams copy their own processes, cases and agents, and worked examples include a document analysis agent. There is no catalog of ready made agents or case apps to install for a job such as onboarding or claims.

Sourcedocumentation.flowable.com/latest/reactmodel/model-templates/index.htmlread 2026-10-12

Processes and cases start or move on from outside events. Inbound channels in the event registry listen on Kafka, JMS, RabbitMQ, AWS SQS, email, REST and Apache Camel, and an event registry start subscribes to a channel and starts a new instance, or only one per set of correlation values. Timer, message and signal start events cover schedules and messages, and agents other than the orchestrator can also be started directly over the REST API when the agent model allows it.

Sourcedocumentation.flowable.com/latest/reactmodel/bpmn/reference/event-registry-start/index.htmlread 2026-10-12

Each agent sets its own vendor, model, temperature, endpoint, custom headers and authentication. Supported vendors are OpenAI, Anthropic and Azure OpenAI, and the OpenAI and Anthropic settings also cover compatible endpoints such as a locally hosted model on Ollama or vLLM. Admins can instead define shared agent connections that agents reference by key. On Cloud Shared, agents connect to the supported providers, and custom models on Cloud Dedicated are still to come.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/concepts/model-settings/index.htmlread 2026-10-12

Flowable Work has a REST API for processes, cases, tasks, users and agents, and the open source engines add Java APIs for embedding. The Work MCP server lets outside AI assistants browse process and case definitions, act on running instances and tasks, look up users, groups and master data and invoke actions, returning the same data as the REST API under the same permissions. It is off by default and needs an AI connector license, and a separate Design MCP server works on models.

Sourcedocumentation.flowable.com/latest/ai/ai-work-mcp-server/index.htmlread 2026-10-12

Flowable Design runs automated unit tests for every agent type except the orchestrator before an app goes live. A test runs the agent on a given input, asserts on the response text, structured fields, guardrail outcomes or extracted data, and mocks the services the agent calls, and Flowable Inspect runs the test sets in bulk. In production, evaluators judge each answer for correctness, tone, faithfulness or format, through an evaluator agent or an outside service, and record the verdict without holding up the reply.

Sourcedocumentation.flowable.com/latest/reactmodel/agent/concepts/testing/index.htmlread 2026-10-12

The Flowable RPA Framework client runs bots built with the open source RPA Framework, either robot files or Robocorp actions and tasks, on a host of the customer's choosing and connects to Flowable over the REST API. A bot runs as a step in a case or process, for example pulling data out of a desktop client application, and hands the result back to the case when it finishes. The client installs with pip.

Sourcedocumentation.flowable.com/latest/develop/external-clients/rpaframework/introduction/index.htmlread 2026-10-12