Webhook events

Outbound webhooks let you fan Yesoma's events into the tools you already use — Slack, n8n, Zapier, your own service. Configure them under Settings → Notifications → Webhooks.

Create a destination

1. Open Settings → Notifications → Webhooks → Add destination.
2. Pick a label (e.g. "Slack — urgent inquiries"), the destination URL, and the events to subscribe to.
3. Yesoma generates a per-destination signing secret. Save it on your receiver — every payload is signed with HMAC-SHA256 so you can verify Yesoma sent it.

Events

| Event | Fires when | | --- | --- | | inquiry.received | A new inquiry lands (any channel). | | inquiry.assigned | An inquiry is assigned to a teammate. | | inquiry.replied | A reply is sent or marked sent. | | inquiry.closed | A case is closed with an outcome (won/lost/no_decision). | | inquiry.flagged_urgent | An inquiry is escalated to urgent. | | followup.scheduled | A new follow-up is created. | | followup.overdue | A follow-up passed its due time without being completed. | | approval.requested | A reply was sent for manager approval. |

Payload shape

{
  "event": "inquiry.received",
  "id": "evt_...",
  "created_at": "2026-05-22T15:00:00.000Z",
  "organization_id": "...",
  "data": {
    "inquiry": { "id": "...", "subject": "...", "source": "email", ... },
    "customer": { "id": "...", "name": "...", "email": "...", "tags": [...] }
  }
}

Field names mirror the database columns; the shape is stable across versions (additive changes only).

Signature verification

Every request includes:

X-Yesoma-Signature: sha256=<hex>
X-Yesoma-Event: inquiry.received

Compute HMAC-SHA256(secret, raw_body) and compare to the header value, constant-time. Reject the request if the signature doesn't match.

Retries

If your endpoint returns anything other than 2xx, Yesoma retries with exponential backoff up to 6 times over ~24 hours. Failed deliveries are visible in the Webhooks panel.

Disabling a destination

Toggle the Active switch in the panel to stop sending. The destination stays configured so you can re-enable it later without losing the secret.

Related

• Slack alert recipe — a concrete end-to-end recipe
• API authentication — for reading data from Yesoma