← back to reference index

Webhooks

Owner only

Push events to your own systems as they happen (§5.4) — the same events an n8n or Zapier flow would subscribe to.

Endpoint Events Last delivery Status Actions
n8n.thelocalcraftfood.ph/hook/bookings booking.createdbooking.cancelled 2 min ago · 200 OK Active
hooks.mailmarketing.io/schedhubph/vip customer.became_vip 1 day ago · 200 OK Active
old-pos-integration.example.com/hook booking.completed 12 days ago · 3× failed Failed · disabled

Delivery is at-least-once, HMAC-signed, 3 retries with exponential backoff, then marked failed and surfaced to you here — not silently dropped (§5.4).

Implementation notes for Cursor

Entities: WebhookSubscription (target URL, subscribed event types, secret, status), delivery attempts logged per event (§5.4).

Key states: Active / Failed · disabled — a subscription whose deliveries have all failed for 24 hours is auto-disabled and the Owner is emailed (§5.4, D61); re-enabling is an explicit owner action (Retry here is scoped to the failed delivery, not a blanket re-enable). Creating a webhook happens on settings-webhook-new.html (D29), which shows the signing secret once; it is never re-displayed after that, matching API key behavior (§18).

Forbidden inventions: no visual payload/log inspector here — this is config + status only. Test/Retry/Delete are mocked (see button titles); wire to the real delivery-attempt endpoints, don't fabricate a new retry-policy.

Governs: §5.1/D20 (Owner-only settings), §5.4 (webhook delivery contract), §5.1/D20 (Owner-only gate).