Slack alert recipe
Wire a Yesoma outbound webhook to Slack so urgent inquiries and approvals ping the right channel.
Get a ping in your team Slack the moment an urgent inquiry lands — useful when you're not staring at the inbox and a complaint comes in cold.
What you'll build
A Slack channel that receives a one-line message every time Yesoma sees inquiry.flagged_urgent, with a link straight to the case.
🚨 Urgent inquiry from Felix Adjei — "Refund request — order #4421"
↗ View in Yesoma
Step 1: Create a Slack incoming webhook
- In Slack, Settings & administration → Manage apps → Custom Integrations → Incoming Webhooks → Add Configuration.
- Pick the channel that should receive the alerts.
- Slack gives you a webhook URL:
https://hooks.slack.com/services/T.../B.../.... Copy it.
Step 2: Add the destination in Yesoma
- Settings → Notifications → Webhooks → Add destination.
- Label: Slack — urgent alerts.
- URL: paste the Slack webhook URL.
- Format: pick Slack (Yesoma formats the body as Slack's
textpayload instead of the default JSON). - Events: tick
inquiry.flagged_urgent. Optionally addapproval.requestedif you want managers pinged for sign-off. - Save.
Step 3: Test
Hit Send test in the Yesoma destination panel. A sample alert should arrive in Slack within a few seconds.
Then trigger a real one: open an inquiry, mark it urgent, and confirm the alert lands.
Customize the message
The Slack format is fixed by default (single-line + link). If you want richer formatting — attachments, custom fields, the AI confidence score — pick the JSON format instead and run the webhook through a small bridge (e.g. a Cloudflare Worker or n8n) that reshapes Yesoma's payload into a Slack Block Kit message.
Don't want urgents in Slack?
Subscribe to a different event mix on the same destination:
inquiry.received— every new inquiry (high volume!)followup.overdue— quiet leads slippingapproval.requested— manager queue
You can have multiple Slack destinations to different channels (e.g. #leads vs. #urgent).
Related
- Webhook events — full event reference
- API authentication
More in Technical setup
- Technical8 min
Website form endpoint
Yesoma's inbound HTTP endpoint that turns form submissions into inquiries. Reference for the URL, payload shape, and field aliases.
Read guide - Technical10 min
Supported form providers
Provider-specific walkthroughs for Web3Forms, Tally, Jotform, Formspree, Netlify Forms, Webflow, and plain HTML.
Read guide - Technical10 min
Webhook events
Outbound webhook destinations: which events Yesoma sends, the payload shape, and signing.
Read guide - Technical8 min
API authentication
Create an API key, scope it to the right permissions, and call the /api/v1/* endpoints from your tools.
Read guide - Setup10 min
Email forwarding setup
Per-provider forwarding for Gmail, Google Workspace, Outlook, iCloud, and Fastmail — point your business email at Yesoma.
Read guide
Was this article helpful?
If something was unclear or missing, tell us and we'll fix it.
Still stuck?
We'll help you get this working. Send us a message, or ask about Managed Setup.