Divan Talk to us
All documentation

Orchestration Studio

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.

The eight studios About Orchestration Studio

What it is for

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

  1. Open Orchestration Studio and say what should happen, starting with "when".
  2. Add a connection for each system it touches; its secret goes to the Vault.
  3. Run it once with a sample, then switch it on.

Tasks

Receive a webhook

  1. Add a webhook trigger and choose the sender.
  2. Give the sender the address and paste its signing secret.
  3. Calls that do not verify are refused before any step runs.

See where a record went

  1. Open the flow's journey.
  2. Pick a run.
  3. Each step shows what came in, what went out and how long it took.

Bring flows from n8n

  1. Choose Import.
  2. Give the exported workflow.
  3. It becomes a flow you can read, test and change.

Questions

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.

Process Studio
Business processes: model them, run them, work them.
Data Studio
Business intelligence on governed data.
Agent Studio
AI agents that work as staff - and wait for people.
Vault
Credentials that are used, never shown.