Webhook events

Outbound webhooks send selected Yesoma events to Slack, Discord, or a generic HTTPS endpoint. Workspace Owners and Admins configure them under Settings → Automation → Webhooks.

Create a destination

1. Open Settings → Automation → Webhooks → Add destination.
2. Choose Slack, Discord, or generic JSON.
3. Add a label, a public HTTPS webhook URL, and the events that destination should receive.

Yesoma rejects non-HTTPS URLs, credentials in URLs, redirects, and private or reserved network destinations. Slack and Discord destinations must use their official webhook hosts.

Events available today

Event	Fires when
approval_requested	A reply is submitted for approval.
case_assigned	A case is assigned to a teammate.
case_closed	A case is closed.
complaint_received	An inbound complaint is detected.
urgent_inquiry	An urgent inquiry is detected.
follow_up_overdue	An open follow-up is more than 24 hours overdue.
case_stale_needs_reply	A needs-reply case exceeds the workspace SLA.

Generic JSON payload

Generic destinations receive this envelope:

{
  "source": "yesoma",
  "event": "follow_up_overdue",
  "title": "Follow-up overdue for Ama",
  "description": "Bridal consultation — was due Aug 3, 9:00 AM",
  "actorName": null,
  "customerName": "Ama",
  "url": "https://getyesoma.com/inbox/...",
  "metadata": {
    "follow_up_id": "...",
    "due_at": "2026-08-03T13:00:00.000Z"
  },
  "sentAt": "2026-08-04T13:00:00.000Z"
}

Slack destinations receive Block Kit; Discord destinations receive an embed.

Delivery and retries

Overdue follow-up notifications use a durable per-destination delivery ledger. A failed destination is retried with backoff up to five total attempts, without repeating destinations that already succeeded.

Other webhook events are currently best-effort and are attempted once. Their durable delivery ledger is planned for a later phase.

Request authentication

Phase 1 webhook requests are not HMAC-signed. For a generic endpoint, use a long, unguessable token in the HTTPS path and rotate the destination URL if it is exposed. Do not rely on headers that Yesoma does not currently send.

Disabling a destination

Toggle Active to stop future deliveries. The destination remains configured so it can be re-enabled later.

Related

• Slack alert recipe
• API authentication — for reading data from Yesoma