Event-driven integration

Inbound HTTP → optional security function → Trigger → server function → logs.

Public name: API Endpoints. Canopy still says Webhooks. Paths stay under /webhooks/.

  1. Create a handle: Managing API Endpoints (Webhooks). Event Payload is a type sample. Response is a static ACK unless a trigger waits.

  2. URL path/query: Webhook URL Parameters (values land in paramsPayload).

  3. Security function that returns boolean: Webhook Security Functions. IP allowlist recipe is on that page. Send JSON/XML/text, not raw binary.

  4. Server function with (eventPayload, headersPayload, paramsPayload): Events and Triggers. Read x-http-method and x-original-uri from headers.

  5. Trigger, Wait for Response if the HTTP client needs the function result. Only one wait-for-response trigger per webhook: Managing Triggers.

  6. Test: Testing Webhooks. Logs: Logging.

Always-on errors without a connected client: Error Handler Triggers. In-process listeners: errorHandler Module.