Integration concepts
A practical way to reason about triggers, transformations, side effects, and flow boundaries. Conceptual guides, without invented flow syntax.
Understand flow designDEVELOPERS
Understand it. Then build on it.
Good developer tools begin with clear contracts. Explore the foundation while the implementation takes shape.
Connector authoring direction
Questions an extension contract needs to answer: lifecycle, authentication, cancellation, error mapping, and compatibility.
Explore connector boundariesSDKs & API contracts
No SDK packages or stable API definitions are published. Read the contract checklist that future releases will need to satisfy.
Read the SDK readiness guideMCP & Developer Skills
The intended AI extension model, with explicit boundaries for context, tool permissions, and reviewed changes.
Read the AI design directionA path to the future Platform.
Platform access is planned. Accounts, sign-in, licensing and Exchange are not available on this website. No account is needed to read the public documentation.
- Explore the integration concepts.
- Check Runtime and Studio documentation readiness.
- Check approved release availability.
- When Platform is released, continue to account setup and any required entitlements.
- When Exchange is released, discover compatible packages and their license requirements.
There is no sign-in or Exchange link to an unavailable service.
Examples that earn
your confidence.
Executable tutorials and sample projects will be published only when they can be reproduced against a verified Runtime release. There are no public sample repositories or install commands to point you to yet.
Available now: a design exercise.Trace a request from receipt to response. Identify its data contract, side effects, retry boundaries, and the observations you need to diagnose failure. Start the guided walkthrough →