Private preview · public architecture
Read the supported integration path
Inspect the private-preview integration boundary for calling a saved workflow or declared connector operation. This page does not publish an endpoint or credential.
Browse only. No account data, credential, MCP session, or product runtime is contacted here.
Public contract example
The API follows the same contract as the workflow
A private integration meets the same declared input, authority signal, and typed-result boundary as Studio, not a parallel shortcut.
Request boundary
- Saved workflow
- Declared contract
- Workspace grant
- Run workflows
- Connection use
- Invoke connections
Outcome boundary
- 01 · Send a declared input The integration meets the workflow’s named input boundary
- 02 · Respect authority A required signal remains a required signal when the call originates through an integration
- 03 · Receive a typed result The result is described by the workflow contract rather than an undocumented shortcut
What this surface owns
A specific boundary, not a generic feature list
The public record shows the contract a buyer can inspect. Configuration, credentials, and effectful actions remain inside a provisioned workspace.
- 01Private workspace
Saved workflow call
Call a saved workflow only after a private workspace grants the execution scope.
Run workflows
- 02Private workspace
Declared connection operation
Invoke only the declared connector operations granted to the service.
Invoke connections
- 03Private policy
Model policy boundary
Model access, invocation, and usage reservation remain their own policy surface.
Read model access · Invoke models · Reserve model usage
The suite