Orchestration Studio : Connect the systems of the organisation.
Data and process integration in flows: something happens in one system, and the right things happen in the others. Databases, queues, files, mail, web services and the platform itself are steps in the same picture.
What it does
Orchestration Studio, point by point.
Adapters for what you already run
SQL and NoSQL databases, message queues, files and object stores, mail, directories, HTTP, GraphQL, SOAP and the platform's own lists and files.
Webhooks, verified
Incoming calls from GitHub, Stripe, Slack, Shopify and others are checked by their signature before a flow runs. CloudEvents are understood.
Business rules beside the flows
A rule set is a table the business owns and versions. Flows, processes and apps ask it for a decision.
The platform has an event bus
A flow can start on something that happens in Divan - and hears only what its owner would be allowed to see.
Speaks MCP both ways
A flow can call tools on an MCP server, and your flows can be offered as tools to agents.
Connect the dots
The studio looks at your systems' data, finds the islands and proposes the bridges between them.
Getting started
Three steps in.
- Open Orchestration Studio and say what should happen, starting with "when".
- Add a connection for each system it touches; its secret goes to the Vault.
- Run it once with a sample, then switch it on.
Questions
What people ask about Orchestration Studio.
What happens when a system is down?
Runs are durable: a step is retried, and a run picks up where it stopped after a restart.
Who may change a connection?
Flows, connections and rule sets are each secured like everything else on the platform: by department, group or named people.