Integrations runtime
Packages group secrets, outbound queries, and inbound webhooks. Runs and receipts show what actually happened.
Packages
A package is the unit you install and configure. It holds non-secret variables such as baseUrl, default headers, and the secrets its queries and webhooks reference. Sandbox versus live is a baseUrl value plus two secret names, not an environment column.
Installing a catalog template copies the definition onto the website. Secret values are never copied.
Secrets
Secrets are write-only. Reads return metadata — name, allowed hosts, rotation time — and never the value. A query or webhook references a secret slot, and secretSlotRefs stores the secret id, never the secret name.
Queries
A query is an outbound HTTP call built from a mapping. It has a source (a lifecycle trigger or manual), a request template, an optional body, response handlers, and bindings. request.delivery decides whether the caller waits for the result (await) or the call is queued.
Webhooks
A webhook is an inbound endpoint with a URL name. It accepts JSON, XML, or form bodies, authenticates with a bearer token or an HMAC comparison, maps the payload onto fields, and can create or update entries. idempotency.keyParts prevents double-processing when a provider retries.
Runs and receipts
Every execution is recorded as a run with a sanitized outbound request and the upstream response. Failed runs keep the status and error, so a payment or delivery problem can be traced without guessing.