Webhooks
Receive HTTP POST payloads when SnitchFeed creates a new match—event type match.created only.
SnitchFeed can POST JSON to URLs you configure so your own services react when a listener surfaces a new mention.
Configure webhook endpoints
In the SnitchFeed app, open Integrations → Webhooks (or go straight to that URL while signed in).
- Click Create Webhook.
- Paste your Webhook URL — an HTTPS endpoint that accepts
POSTrequests with a JSON body (for example a Zapier catch hook, n8n workflow URL, or your own API route). - Enter a Name so you can recognize it in the list (for example “CRM pipeline” or “Slack bridge”).
- Click Save.
You can register multiple destinations; each new match can be delivered to every active webhook for your workspace.
After a webhook exists, use the Status toggle to pause or resume deliveries without deleting it.
You can also test the webhook by clicking the Test button.
Plan requirement
Creating webhooks requires a subscription that includes webhooks. If Create Webhook is unavailable, open Settings → Billing in the app and upgrade to a plan that supports them.
Events
Outbound webhooks fire for one event type:
| Event | When it is sent |
|---|---|
match.created | When SnitchFeed creates a new match (a post or comment that matched your listener and was saved). |
The envelope includes event.type set to match.created, a stable event.version (currently 1.0), and the full match payload (platform fields, AI summary, relevance, and related IDs).
API reference
Technical details for outbound delivery—payload shape, HTTP expectations, retries, and timeouts: