TestingOps.ai

Process models (BPMN) · Native connection

Celonis Process Management and TestingOps: test scenarios from modeled processes

Celonis Process Management, formerly Symbio, holds the modeled processes of a storage. TestingOps exports them as BPMN 2.0 and lists the paths through each process as scenario candidates. It reads the models, not process mining data.

  • Native connection
  • Available
Request a demo
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Celonis Process Management and TestingOps in short

The Celonis Process Management connection reads one storage with the storage's REST authentication token: it lists the storage's processes through the Data API and exports a linked process as BPMN 2.0 through the BPMN API.

Each process becomes a knowledge-base document with steps, decisions, exceptions and bounded paths from start to end, marked as scenario candidates for review.

This is the modeling side of Celonis: event logs, conformance results and other process mining data are not read, and nothing in the storage is changed.

What it does

What it does for your testing

  1. 1

    Storage processes become test input

    Input
    Processes of the storage with their name and state
    TestingOps
    Lists them, 100 per page and up to 500, for linking to a project
    Output
    The modeled process as the basis for scenarios
  2. 2

    The BPMN export becomes paths

    Input
    A process exported as BPMN 2.0
    TestingOps
    Parses steps, lanes, gateways and events and numbers the paths from start to end
    Output
    Scenario candidates for review
  3. 3

    Version IDs decide when to re-read

    Input
    The element's version ID and, when present, its last-change attribute
    TestingOps
    Exports the process again only when they changed
    Output
    Candidates that follow the model without downloading unchanged processes

Step by step

How it works

  1. Create a REST tokenIn the storage's Automation settings, create a REST authentication token.
  2. Connect the storageUnder Integrations → Platforms → Process models (BPMN 2.0) → Celonis Process Management, enter the storage address in the form https://<host>/<collection>/<storage> and the token. Browser address tails such as /editor are cut off.
  3. Link a processIn the project's Knowledge tab, add a source under Process models (BPMN 2.0): pick a process or paste its element ID or a link that contains it.
  4. SyncSync now exports and parses the process; automatic syncs follow and skip a process whose version did not change.
  5. Review the candidatesAgents and testers read the process document from the knowledge base and write scenarios from the candidates they keep.

Connect

Setup

  1. In Celonis Process Management, open the storage's Automation settings and create a REST authentication token.
  2. In TestingOps, open Integrations → Platforms → Process models (BPMN 2.0) → Celonis Process Management, enter the storage address (https://<host>/<collection>/<storage>) and the token, then select Test connection and Save.
  3. In the project's Knowledge tab, select Add source under Process models (BPMN 2.0) and pick a process, or paste its element ID or a link that contains it.
  4. Select Sync now. Automatic syncs export a process again only after its version changed.
Where you connect it in TestingOps: Integrations → Platforms → Process models (BPMN 2.0) → Celonis Process Management

Use cases

Use cases

Start test design from the reference process

Trigger
A team links the processes it is about to implement
Uses
The BPMN export of each process
Agent activity
Writes scenarios from the numbered paths, with the lane and decision at each step
Result
Draft scenarios tied to the modeled process
Condition
Up to 30 paths per process are listed

Keep scenarios current when the model is updated

Trigger
A process gets a new version in the storage
Uses
The version check on the next sync
Agent activity
Searches the existing scenarios before writing scenarios for new paths
Result
Scenarios for what changed in the model
Condition
TestingOps does not mark which existing cases the change breaks

Keep modeling and mining apart

Trigger
A team also uses Celonis process mining
Uses
Only the Process Management storage
Agent activity
Works from the modeled paths, not from observed process variants
Result
Scenarios from the intended process
Condition
Observed variants from event logs are not read; compare them with the candidates yourself

Capabilities

Capabilities and limits

What is read

  • Processes of one Process Management storage (name, state) from the Data API v2; the element's version ID and last-change attribute; the BPMN 2.0 export from the BPMN API v2
  • Per process (named after its pool when there is one): start, end, intermediate and boundary events with their type, such as timer, error or message; tasks, including user, service, script, business rule, manual, send and receive tasks; call activities, without following the called process; sub-processes, ad-hoc sub-processes and transactions with their inner steps; exclusive, inclusive, parallel, event-based and complex gateways; sequence flows with their name or condition; lanes; documentation; inline form fields such as camunda:formField
  • Not parsed: message flows between pools, data objects and data stores, text annotations, the DMN tables behind business rule tasks, linked forms, and timer or expression details beyond the event type

What is produced

One knowledge-base document per process: steps with kind, lane and documentation, decisions with their outcomes, exceptions from boundary events, form fields, and numbered paths from start to end marked as test scenario candidates

Where it can write

Nothing in the storage: processes are only listed and exported

How it connects

Celonis Process Management REST APIs of one storage, with the storage's REST authentication token

Account and permissions

  • A REST authentication token created in the storage's Automation settings
  • The storage address: host, collection and storage

Limits

  • Paths are bounded: at most 30 per process and 60 steps per path; a loop is followed once and the path ends with "back to" the step it returns to; each outgoing branch of a gateway, parallel and inclusive ones included, becomes its own path, so branches are not combined
  • Paths are candidates for review: no TestingOps scenarios or cases are created from them automatically
  • One storage per connection; up to 500 processes listed
  • Process mining data (event logs, conformance, variants) is not read
  • Up to 12,000 characters per process section and 200 processes per model; files and exports up to 15 MB

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team preparing a procurement rollout links the Purchase requisition approval process from its storage. The export shows lanes for Requester and Budget owner, an inclusive gateway for the approvals a requisition needs, and an end event for rejection.

The document lists the gateway's outcomes as separate paths. An agent writes scenarios for the single-approval and rejection paths, and the team adds the case where two approvals are needed together, which the path list does not combine.

Frequently asked questions

Is this the same as Symbio?

Yes. Celonis Process Management was formerly called Symbio, and the connection reads a Process Management storage at an address such as https://example.symbioweb.com/collection/storage.

Does TestingOps read Celonis process mining data?

No. It reads modeled processes from a Process Management storage. Event logs, conformance checks and other process mining results are not part of this connection.

Which token does it need?

The storage's REST authentication token, created in the storage's Automation settings and sent in the symbio-auth-token header.

Are parallel or inclusive approvals combined into one scenario?

No. Each outgoing branch of a parallel or inclusive gateway becomes its own path, so combinations of branches have to be added by the tester. Up to 30 paths per process and 60 steps per path are listed.

Does it change our models?

No. TestingOps lists processes, checks their version and downloads the BPMN export. It does not write to the storage.

Next step

See a modeled process as scenario candidates: request a demo and bring one process from your storage.

Request a demoMore process models integrations