Expected outcome
You can describe the operation, credential boundary, failure posture, and workspace review condition without pretending that a public page configured or invoked it
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
- One API operation with a clear business purpose and owner
- An understanding of what the operation may read or change
Steps
- 01
Name one operation
Start with the narrowest useful operation rather than an entire provider account or a broad integration category
- 02
Keep the credential reference separate
The workflow should reference a named connection and operation. Endpoint values and credentials remain inside Tempera Connectors after private provisioning
- 03
Classify a failure before changing anything
A missing permission, rate limit, or changed response shape needs evidence and a bounded recovery path. A failure is not a reason to silently rewrite an integration
- 04
Set the change boundary
A recovery that would change an endpoint, permission, or effect stays a bounded proposal for workspace review. A failure does not authorize an automatic repair
What success looks like
- The workflow sees a declared operation, not the credential material behind it
- A failure can be investigated and proposed for recovery without implying an automatic change
- The owner can explain the workspace policy and review path required before a private connection is configured or invoked
If something is blocked
- If the operation needs a broad credential, reduce the operation boundary or complete the security review before continuing
- If a recovery would change an endpoint, permission, or effect, keep it as a reviewable proposal rather than treating it as an automatic repair