Webhooks

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).

1. Click Create Webhook.
2. Paste your Webhook URL — an HTTPS endpoint that accepts POST requests with a JSON body (for example a Zapier catch hook, n8n workflow URL, or your own API route).
3. Enter a Name so you can recognize it in the list (for example “CRM pipeline” or “Slack bridge”).
4. 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.

View delivery logs

When your plan includes webhooks, the Webhooks screen has two tabs: Endpoints (create, edit, pause, and test URLs) and Log (outbound delivery history).

On Log you will see each POST we made to your endpoints:

• Date & time of the delivery
• Endpoint name
• Mention — link to open that match in the feed
• Code — HTTP status from your server, when we received one
• Response body — truncated in the row; click the row to expand an accordion and read the full body when we stored it
• Status — delivery outcome (pending, success, failed, retrying)

Use Status, Endpoint, and Date range to narrow the list. Results are paginated (100 deliveries per page) with Previous and Next—not infinite scroll.

For how we retry failed deliveries, backoff timing, and workspace pacing, see Webhooks (API overview).

Events

Outbound webhooks fire for one event type:

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, pacing, and delivery history: