BPMN with AI Agents: Spec-Correct Element Reference (2026)
The OMG BPMN 2.0 specification (formal/2014-01-03) is the canonical process-modelling notation. No vendor page applies it correctly to agent-augmented processes. The reference below walks each relevant element with its agent-process meaning, citing the specification by section.
Specification reference: Object Management Group, “Business Process Model and Notation (BPMN) Version 2.0.2”, omg.org/spec/BPMN/2.0 (formal/2014-01-03, accessed April 2026). All section references below are to that document.
BPMN 2.0 is an OMG standard adopted as ISO/IEC 19510:2013. The specification is normative for shape semantics on this site.
Elements with agent-process meaning
| Element | Spec section | Canonical use | Agent-process application |
|---|---|---|---|
| bpmn:lane | §10.5.5 | Actor partition. A horizontal subdivision of a pool, normally one per actor type (human, agent, tool, system). | Used to represent each actor in an agent-augmented process. The agent lane carries service-tasks, the human lane carries user-tasks, the tool lane carries generic tasks or send/receive markers. |
| bpmn:pool | §10.5.4 | Participant grouping. Often the organisation, the process boundary, or an external participant. | Use one pool per organisational boundary. Cross-organisation agent-to-agent handoffs (e.g. an external scheduling agent being asked to book) become message flows across pools. |
| bpmn:task | §10.3.1 | Generic atomic activity. The base task type with no markers. | Use sparingly for AI agent steps. A generic task with no marker fails to encode whether the step is automated or human, which defeats round-tripping with downstream BPMN tools. |
| bpmn:userTask | §10.3.5 | A task performed by a human with software support. | The canonical home for the human review step. Approval, manual classification, escalation handling, sign-off. |
| bpmn:serviceTask | §10.3.4 | A task performed by an automated system or service. | The canonical home for an autonomous agent step. The implementation attribute can record the framework (LangGraph, CrewAI, AutoGen, OpenAI Agents SDK). |
| bpmn:businessRuleTask | §10.3.6 | A task that applies a business rule. | Use when the agent is essentially classification or decision-only with no tool use. A pure intent classifier or sentiment scorer is a business rule task. |
| bpmn:callActivity | §10.4.4 | A reusable sub-process invoked from the parent. | The recommended wrapper for the agent's internal sense-think-act loop. The wrapper process is BPMN-deterministic; the loop is detailed elsewhere (typically in an engineering reference, not in the BPMN diagram itself). |
| bpmn:exclusiveGateway | §10.6.3 | A decision point with one outgoing path. The default gateway for branching. | Used at human-vs-agent gates and at confidence routing. Each outgoing path carries a named condition. |
| bpmn:eventBasedGateway | §10.6.7 | A decision based on incoming events rather than a condition. | Used at escalation gates where the next step depends on whether a signal arrives, a timer fires, or a message is received. |
| bpmn:messageFlow | §10.7.4 | Communication across pools. Drawn as a dashed arrow. | The canonical agent-to-agent handoff shape across organisational boundaries. Inside a single pool, sequence flow is correct; across pools, message flow. |
| bpmn:signalEvent | §10.7.6 | A broadcast event. Throwing or catching, intermediate or boundary. | Used for agent escalations. The agent throws a signal from its lane; a human catches it in another lane and continues the process. |
| bpmn:startEvent / bpmn:endEvent | §10.7.1 / §10.7.2 | Process boundaries. | Standard usage. The start event is normally triggered by an inbound message (a customer query) or a timer (a scheduled run). |
Modelling an agent's internal loop
The agent's sense-think-act loop is non-deterministic and out of scope for BPMN's deterministic process semantics. Trying to render the loop inline blows up the diagram and forces the modeller into constructs that BPMN never intended.
The recommended pattern is a single bpmn:serviceTask for short, scoped agent operations, or a bpmn:callActivity for longer loops that should be reusable. The wrapper process stays BPMN-deterministic. The agent loop's internals are detailed separately (in an engineering reference such as buildingeffectiveagents.com or whatisanaiagent.com / how AI agents work). Anthropic's December 2024 paper makes the same workflow-vs-agent distinction in plain prose.
Common BPMN-misuse patterns on vendor pages
1. Generic task instead of service task
Vendor diagrams often render an autonomous agent step as a generic bpmn:task. The shape is BPMN-legal but loses the automation classification. Tool round-tripping (Camunda Modeler, Signavio, bpmn.io) reads the missing marker as user-mediated by default. Use bpmn:serviceTask for autonomous agent steps and bpmn:businessRuleTask for classification-only.
2. User task for a step the user does not perform
The opposite mistake. A decision flow rendered as bpmn:userTask when no user is involved (the rule engine or the agent classifier acts alone). The shape implies a human in the loop where there is none, and downstream tools generate a task in a worklist that nobody sees.
3. Inline rendering of the agent loop
The agent's internal loop drawn inline as a series of tasks and a back-edge. The diagram becomes unreadable; the loop's non-determinism is misrepresented as a deterministic cycle. Wrap the loop as a bpmn:callActivity and document the internals separately.
Reference example: customer support intake
The diagram below is a BPMN 2.0 swimlane for a customer support intake process where an AI tier-1 agent handles classification and most replies, with escalation to a human tier-2 agent on ambiguity. Every shape on the diagram is spec-correct.
Related pages
- Handoffs : message flow vs sequence flow vs signal event in handoff patterns.
- Human vs agent swimlanes : when to add the gateway and the user task.
- By process : five processes, each with a BPMN-correct swimlane.
- whatisanaiagent.com / how AI agents work : what the call-activity contains.