Expected outcome
You can prepare the integration boundary without inventing a public endpoint, client package, credential, or execution result
You can use this public guide without a Tempera account, product credential, or private workspace. Product access begins only after private onboarding.
Before you start
- A saved or proposed workflow with a named input and result boundary
- A service owner who can accept a narrow workspace grant
Steps
- 01
Start from the workflow record
The integration should name the workflow and its declared input rather than recreate its logic in a second, undocumented API path
- 02
Request the smallest execution grant
A private service needs only the workspace audience and scopes that match the workflow or connector operation it owns
- 03
Preserve the authority pause
Calling a workflow from an integration does not remove its configured authority signal. A workspace may bind that explicit signal gate to human or policy review
- 04
Consume the declared result
Treat the returned value as the workflow’s typed result, and agree how the integration should handle a blocked or incomplete state before it runs
What success looks like
- The service has a clear request, grant, authority, and result boundary to review during onboarding
- The integration does not assume a shared public endpoint or unauthenticated execution path
- The configured authority signal remains visible to both the workflow owner and the integration owner
If something is blocked
- If the integration needs a bypass around an explicit signal gate, revise the workflow contract instead of hiding the decision in client code
- If the result shape is unclear, keep the integration in planning until the workflow owner declares the output it expects