Autonom8 vs Bizagi (2026)

Workflows reach outside systems through service tasks, which run JavaScript or TypeScript services, Java classes or expressions to call web services, APIs and databases as a step in the process. Credentials for those calls can sit in secure variables, and A8Flow has built in SMS providers, MSG91 and Prowtext, for one time passwords, password resets and task notices. Each integration is written as a custom service, with no catalog of ready connectors. Agent tools are still on the way, so an AI agent cannot call an outside system itself today.

Sourcedocs.autonom8.com studio services, service tasks and ai-agents, flow integrationread 2026-10-12

Agents act through AI Actions. A builder links connectors already set up in the project, SAP BTP connectors or MCP servers reached over server sent events, picks which of their actions the agent may use and writes the goal into the prompt, and the agent decides when to call each one, with up to 100 actions in total. MCP servers authenticate with an API key sent as Basic, Bearer or a custom header. Agents can gather more data, act in outside systems and start processes in Bizagi or third party systems this way.

Sourcehelp.bizagi.com/platform/en/ai_actions.htmread 2026-10-13

A8Studio builds each app around a BPMN journey with user, service, script, send, receive, manual and business rule tasks, so one process can run steps in sequence or in parallel across people, systems and AI agent steps. Assisted journeys have several actors working a case, such as loan origination, while Solo journeys let one customer complete a flow made of form, condition, timer, webhook and service nodes. Deployed apps run in the A8Flow runtime, which moves each instance through its steps and tracks it to completion, and A8Flow processes and Solo sessions can call each other.

Sourcedocs.autonom8.com studio journey, task types and solo nodes, autonom8.com a8flowread 2026-10-12

Agents run inside BPMN processes built in Bizagi Studio, as an action on an AI task that fires when a case enters or leaves it, from a button on a form, from entity forms or inside data pipelines, and Master and Persona entities can now run an agent as an Entity Action with its own input and output mappings. Several agents can run in one process, side by side or one after another, and their outputs map to typed fields in the data model, so later steps, business rules and people use them like any other case data.

Sourcehelp.bizagi.com/platform/en/ai_agents.htmread 2026-10-13

Work reaches a running app on its own. A8Chat takes customer messages from channels such as Facebook Messenger through a webhook, and BPMN receive tasks hold a process until a message arrives from an outside system.

A webhook node hands a third party a callback address, then authenticates the caller, checks the incoming data and moves the journey on when the provider reports back, as with a payment or identity check. Server side functions can be exposed as endpoints that outside systems call, protected by an API key. Timer nodes pause a journey for anything from 30 seconds to 30 days, though nothing starts a new run on a schedule.

Sourcedocs.autonom8.com chat integration, solo webhook and timer nodes, receive tasks and expose endpointread 2026-10-12

An agent on an AI task runs whenever a case reaches that task, with no one asking. Cases themselves start from a timer start event on a schedule, from a message or signal thrown by another process, from events Bizagi consumes off Kafka topics, or from a person in the work portal, and AI Jobs in the Management Console schedule and monitor AI work on their own. Agents can in turn trigger events that start processes in Bizagi or in other systems, and processes can publish events back to Kafka.

Sourcehelp.bizagi.com/platform/en/start_events.htmread 2026-10-13

Agents in A8Studio work from the instructions, variables and output fields set on each agent, with workflow data passed in when the agent runs. Knowledge bases for agents are still to come, so today an agent cannot search a company's own files or policies, and nothing ingests or indexes them for it. A8iQ studies operational data from running workflows to produce process metrics, and agents do not draw on it as company knowledge.

Sourcedocs.autonom8.com studio ai-agentsread 2026-10-12

Enterprise Knowledge holds catalogs that are processed, indexed and served through retrieval augmented generation while agents run, kept in a vector database that serves retrieval and never trains a model.

File Knowledge builds a catalog from content extracted from documents and serves AI Agents, AI Workers and the Ask Ada assistant, and Bizagi Data Knowledge builds one from records stored in Bizagi entities for AI Agents. Catalogs sit in categories in Studio's AI Hub and are reindexed after a deployment or update.

Agents can also find conceptually similar past cases without exact keyword matches, and the knowledge can extend or replace an agent's default instructions with a company's guidelines and procedures.

Sourcehelp.bizagi.com/platform/en/enterprise-knowledge.htmread 2026-10-13

Long running workflows keep their state across channels and steps until they finish, and the variables on each assisted instance can be viewed, edited or deleted by users with the right permissions. The Export Application API returns those variables for instances started within a chosen window. Agents start each run from their instructions and the variables a workflow passes in, and keep nothing they can recall in a later, separate run.

Sourcedocs.autonom8.com flow history access control and export application api, autonom8.com a8flowread 2026-10-12

Each agent call works from inputs mapped from the case and the knowledge catalogs attached to it, and writes its outputs back to case fields, so the case carries the state while it runs. Inputs can run to 500,000 characters, so whole documents and long case histories can be passed in on each call. An agent keeps no memory of its own that it reads from one case to the next.

Sourcehelp.bizagi.com/platform/en/ai_agents_faqs.htmread 2026-10-13

People can be placed at any point in a process. When a journey reaches a user task, A8Flow creates a task and the instance waits until a person completes it, whether that means filling a form, checking data or signing off.

Tasks go to a named assignee, candidate users or candidate groups, show up in My Tasks and My Group Tasks lists, can be claimed or reassigned under permission rules, and can send SMS notices to the group. A8Chat pairs its chatbot with live chat support.

Review points are designed into each journey by its builder, and there is no separate setting that holds an AI agent's output for approval.

Sourcedocs.autonom8.com studio user tasks, flow tasks and group managementread 2026-10-12

AI Workers take on tasks people would normally do in one of three modes. In supervised processing the worker does as much of the task as it can and hands it to a person to review or finish, conditional processing follows rules the customer sets to decide when it works alone, and autonomous processing falls back to a person whenever it cannot finish. Each decision comes with its reasoning for a person to check, and agent outputs land in form fields that people review before a case moves on.

Sourcebizagi.com/en/platform/ai-workersread 2026-10-13

Access is controlled at a fine grain. A8Flow signs users in through OpenID Connect single sign on, with an optional mixed mode that keeps passwords alongside it and a default group for first time users.

Authorization rules allow or deny each user or group specific actions on process definitions, instances, tasks, users and other resources, and A8Studio policies build custom roles with separate rights to edit AI agents, deploy live or export audit logs.

Secure variables are encrypted with AES 256 GCM, variable groups carry their own access lists, and audit logs are immutable and record the source IP of each request. The product docs show no SOC 2 report or ISO 27001 certificate behind these controls.

Sourcedocs.autonom8.com flow sso, authorization and audit logs, studio policy and secure variablesread 2026-10-12

Bizagi holds ISO/IEC 27001:2022, its cloud for US government is FedRAMP Moderate, and independent reviews found the cloud meets HIPAA and HITECH requirements. Users sign in through SAML, OAuth or LDAP with two factor authentication, role based segregation of duties and delegated administration govern who can do what, and roles can be kept in step with Microsoft Entra ID. Data is encrypted in transit and at rest, each customer's applications and data are isolated, and an annual transparency report covers government requests for customer data.

Sourcebizagi.com/en/platform/complianceread 2026-10-13

Each run can be traced afterward. The Solo history lists finished sessions as complete, expired, errored or timed out, and its timeline shows the exact path a session took, including the branch it followed at each condition. Assisted history covers running and completed instances and their variables.

The A8Flow audit log records every create, edit and delete on tasks, users, deployments and settings, tagged with the user, process instance, task and source IP. Application logs stream live during a session and are kept in the cloud for search and export through the a8flow command line tool. What an AI agent was prompted with and returned inside a step does not appear in these views.

Sourcedocs.autonom8.com solo history, flow audit logs, logs and cliread 2026-10-12

Tracing in the Management Console records AI agent invocations, the requests and responses of the connectors an agent calls, tagged with the case number, and the responses AI Workers produce, at error, warning or information level, and AI Workers show the rationale behind each decision.

Traces are kept for 90 days and are meant for troubleshooting, with the platform's audit and accountability controls kept apart from them. An AI consumption report traces usage to processes, tasks, entities and applications and shows the models and tokens behind each execution, and an AI Metrics dashboard tracks agent use over time by process and by agent.

Sourcehelp.bizagi.com/platform/en/tools-tracing.htmread 2026-10-13

Workflows, forms and agents run on Autonom8's own cloud, deployed from A8Studio into A8Flow environments that an organization sets up with a runtime address and an API key. The rules engine is the exception. DMN Hub runs as a Docker container with its own Postgres and Redis on the customer's systems, so decision tables can be built, stored and evaluated in house while A8Flow calls them through its SDK. Workflows themselves have no region choice, private cloud or self hosted runtime.

Sourcedocs.autonom8.com dmnhub overview and install, studio environments and deploymentread 2026-10-12

Each customer gets a dedicated cloud setup with isolated storage and its own URL, provisioned in the Azure geography it picks at onboarding, US, EU, Asia or US Government, and every service and resource stays inside that geography. Bizagi chooses the exact Azure region within it. Production data is replicated to a paired region and backed up nightly, with a 5 minute recovery point and a 3 hour recovery time.

Sourcehelp.bizagi.com/platform/en/available-regions-for-bizagi-c.htmread 2026-10-13

Builders start from shared parts more than finished agents. The Prompt Gallery holds prebuilt prompts for common jobs that fill in an agent's instructions, and Generate Prompt turns a plain request into a structured one. A8Marketplace is a store of form widgets an organization installs, built with the create a8 component command line tool, and the A8Studio library carries flows, templates, components, services, integrations and themes. There is no catalog of ready made agents or journeys for a job such as loan origination or account opening.

Sourcedocs.autonom8.com studio ai-agents and marketplaceread 2026-10-12

AI agent templates deploy straight from Bizagi Studio, with 13 for banking and investments, 7 for customer service and 10 for manufacturing and retail, grouped into predefined Solutions a builder can search by Solution, title or description. They cover jobs such as generating and comparing earnings reports, categorizing customer incidents, obfuscating personal data, composing incident responses, writing knowledge base articles, translating policies, comparing vendors and summarizing RFx responses. Bizagi Copilot helps refine a template's prompt in plain language.

Sourcebizagi.com/en/platform/ai-agent-templatesread 2026-10-13

The builder picks the model behind each agent from a configuration panel, choosing among Google Gemini (Gemini Pro, Gemini Flash), OpenAI (GPT 4, GPT 4o, GPT 4o mini) and Anthropic (Sonnet, Opus, Haiku) models, with guidance to weigh cost against capability. Temperature, output token limit (4,000 by default) and top p are set per agent, and output can be plain text or JSON with typed, required fields. TARS, the code helper inside A8Studio, runs on GPT 3.5 Turbo. There is no bring your own key option and no automatic routing or fallback between models.

Sourcedocs.autonom8.com studio ai-agents and tarsread 2026-10-12

Agents run on Azure OpenAI through Bizagi's private GPT service. For each agent a builder picks a model from those OpenAI currently offers, which change with OpenAI's updates and deprecations, choosing between direct response models and reasoning models with a set reasoning level, and tunes temperature, top p, frequency penalty and presence penalty. Files as inputs need GPT 4o or a newer model. Every choice stays within OpenAI's models, with no option to bring another maker's model or a customer's own deployment.

Sourcehelp.bizagi.com/platform/en/ai_agents_from_scratch.htmread 2026-10-13

Four APIs open the platform to code, each reached with a scoped API key that carries its own expiry date. The Deployment API pushes A8Studio apps into the A8Flow runtime, the Export Application API returns instance data and variables for any window up to 24 hours, the Start New Process API opens an assisted case remotely, and Check Dedupe tests for duplicate records. Android and iOS SDKs embed A8Flow in mobile apps, the a8flow command line tool handles sign in and logs, and services and functions are written in JavaScript or TypeScript against the A8Data, A8Config, A8Astro and A8Func SDKs.

Sourcedocs.autonom8.com flow api keys, export application api, sdks and cliread 2026-10-12

The Bizagi API is a RESTful service on OData 4.0 with OAuth 2 bearer tokens, so outside applications can start cases for a process, search cases and work with process data. A JSON file in Swagger 2.0 and OpenAPI 3.0 format describes every OData endpoint for middleware, a full service index lists them, and examples include C# code. Since the Summer 2026 release a REST API also exports and imports deployments, so a team can automate releases from its own pipeline, and API traces can be switched on for debugging.

Sourcehelp.bizagi.com/platform/en/api_odata.htmread 2026-10-13

Tuning happens after launch. A8iQ tracks business metrics across activated workflows so teams can adapt each workflow to those metrics in a continuing loop, and flow mining shows key measures and bottlenecks for each flow and each version over a chosen period, so a new version can be compared with the last one in production. There is no test suite or quality gate that checks an AI agent's answers before a release.

Sourceautonom8.com a8iq, docs.autonom8.com flow miningread 2026-10-12

Builders try an agent in a Test Prompt window, which runs one input file at a time, shows which actions the agent called, and can differ from what happens at run time. AI Workers in supervised mode learn from each user after the 50th interaction on a task, building a personal policy from that user's behavior and feedback, and a team can switch that reinforcement learning on or off per task. Bizagi has retired its Autotesting tool, and there is no saved test set, quality gate or measure of how the learning changes results before an agent goes live.

Sourcereleasenotes.bizagi.com/en/release-notes/releases/fall-2025read 2026-10-13

Autonom8 connects to other systems through services, APIs and SMS providers, and its agents work on the data a workflow hands them. Scanner, selfie, signature and video KYC widgets collect documents and identity checks from customers inside the app's own forms. Nothing in the platform drives a browser, a desktop or another application's screen on a user's behalf.

Sourcedocs.autonom8.com studio services and widgets, autonom8.com a8flowread 2026-10-12

Screen level work runs through RPA bots from partners such as Automation Anywhere, which handle manual tasks while Bizagi manages the flow of data between people and robots. The bots and their runtime come from the RPA vendor, and Bizagi's own agents do not drive a browser or desktop themselves.

Sourcebizagi.com/en/solutions/robotic-process-automation/automation-anywhere-and-bizagiread 2026-10-13