New entries, to any service.

Step 1

Prepare an endpoint

Anything that accepts an HTTPS POST with a JSON body works: a route in your own app, a Cloudflare Worker or AWS Lambda, or the catch-a-webhook URL of platforms like Zapier, Make, or n8n. For local experiments, a service like webhook.site shows the incoming payloads instantly.

Step 2

Register the webhook in SlashFeed

Open Webhooks in the app, paste the endpoint URL, and add a label. SlashFeed generates a signing secret for the webhook — store it in your service's configuration; you will use it to verify deliveries in the next step.

Step 3

Verify the signature

Every delivery carries an HMAC-SHA256 signature of the raw request body, computed with your webhook's secret:

x-slashfeed-signature: sha256=9f2c4a…

Before trusting a payload, recompute the HMAC over the exact bytes you received and compare it (constant-time) to the header value. Reject anything that does not match — it did not come from your SlashFeed instance.

Step 4

Send a test and watch the delivery log

Use the test-deliver button next to the webhook to fire a sample payload at your endpoint. Every attempt — test or real — is recorded in the delivery log with its HTTP status and response, so debugging a misbehaving endpoint never requires guesswork. Failed deliveries are retried automatically with backoff.