Webhooks

SnitchFeed can POST JSON to URLs you configure whenever a feed surfaces a new match. Webhooks are per feed: you register endpoints here, then choose which ones fire for each feed in that feed's notification settings.

Register a webhook endpoint

In the SnitchFeed app, open Integrations → Webhooks.

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 later (for example "CRM pipeline" or "Zapier bridge").
4. Click Save.

Use the Status toggle to pause or resume an endpoint without deleting it. Click Test to send a sample payload to the endpoint.

One endpoint can be selected across multiple feeds.

Delivery limits

Open Advanced: delivery limits in the webhook dialog to tune how SnitchFeed paces deliveries to that destination:

• Max concurrent requests — how many deliveries can be in flight to this endpoint at once. Defaults to 1. Some automation tools (n8n, for example) drop requests beyond their own inflight limit, so keep this at or below whatever your destination supports.
• Max requests per minute — how many deliveries can be sent to this endpoint per minute. Defaults to 10.

Both are configurable per destination. Delivery retries are fixed at up to 10 attempts per delivery with exponential backoff for transient failures, and are not configurable. 401, 403, 404, and 410 fail immediately without further retries. See Retries and exponential backoff for details.

Route webhooks to a feed

After registering an endpoint, open any feed and click the Bell icon in the top-right navbar. In the Webhooks tab, select the endpoints that should fire when new matches arrive in that feed, then click Save changes.

View delivery logs

The Webhooks screen has two tabs: Endpoints and Log.

On Log you will see each delivery SnitchFeed made to your endpoints (one row per mention × endpoint, not one row per retry):

• Date & time of the latest attempt for that delivery
• Endpoint name
• Mention — link to open that match in the feed
• Attempts — how many times we POSTed (including retries)
• Code — HTTP status returned by your server on the latest attempt
• Response body — click a row to expand the full body
• Status — pending, success, failed, or retrying

Filter by Status, Endpoint, and Date range. Results are paginated at 100 per page.

Events

The payload includes event.type, a stable event.id across retries of the same delivery, a stable event.version (1.0), and the full mention (platform fields, AI summary, Fit Score, and related IDs).

API reference