Feature
Events you can trust on the wire.
Subscribe an HTTPS endpoint to the writes that already happen in Fresno. Every delivery is HMAC-signed, retried with backoff, and stored so you can see what was sent.
Events you can subscribe to
Dot-notation types, the same write edges the rest of the product already observes.
Contacts & companies
- contact.created / contact.updated
- company.created / company.updated
Deals & tasks
- deal.created / deal.updated / deal.closed
- task.created / task.updated / task.completed
HMAC-SHA256 on every POST
Payloads are signed with the webhook secret. Verify X-Fresno-Signature (sha256=…) plus X-Fresno-Event and X-Fresno-Delivery before you act on a body.
Six attempts, then stop
Failed deliveries retry on a backoff (30s → 2m → 10m → 30m → 2h). After six attempts the delivery is marked failed and left in the log — it is not silently dropped.
Every attempt is stored
Each delivery records status, HTTP result, truncated response or error, and when it succeeded. You can list deliveries for a webhook instead of grepping your own logs.
Your endpoints, your events
Webhooks are tenant-scoped, can subscribe to a subset of event types, and can be paused or soft-deleted without losing history.
Push, don't scrape
Pair outbound webhooks with custom objects when your integration needs a model Fresno does not ship — events for the core records, your schema for the rest.