OptionalbodyZod schema for the request body — converted to JSON Schema at sync time.
OptionaldescriptionOptional longer description shown in the action picker.
Path appended to the integration baseUrl (e.g. /contacts).
OptionalheadersZod schema for additional HTTP headers (rare; auth headers are added by Bondi).
Human-readable label shown in the Bondi Studio UI.
HTTP method Bondi should use to call your endpoint.
Stable identifier — used in workflow nodes and webhook signatures.
OptionalqueryZod schema for query string parameters.
OptionalresponseZod schema describing the expected response — drives autocomplete in workflows.
A single action exposed by your integration — Bondi calls this from a workflow, signing the request with the integration token (HMAC-SHA256).
The generics
TBodyandTResponsecapture the inferred Zod types soactionHandler(action, ...)adapters can type their handler context end-to-end. They default tounknownso heterogeneous arrays of actions (e.g.ServiceDefinition.actions) still type-check.Example