Guides

Webhooks: push signals to your own tools

A webhook pushes each signal to a URL you own the moment it's found — so buyer pains, competitor mentions, and self-promotions land straight in your own tools. Here's how to turn it on.

Last updated July 18, 2026

On this page

What a webhook is

A webhook pushes each signal to another tool the moment it's found — no waiting for the daily brief, no copy-paste. You give dist0 a URL that one of your own tools listens on, and every time a new signal shows up for your project, dist0 sends it there.

Most marketers point that URL at a no-code tool like Zapier or Make, which then drops the signal wherever they want it — a spreadsheet, a Slack channel, a task list. Teams with their own app can point it there instead.

Turn it on

  1. Open Settings → Developer → Webhook in your dashboard.
  2. Paste the URL your tool listens on into the URL field. It must start with https://.
  3. Under What to send, tick which signals you want sent.
  4. Click Save.

Right after you save, dist0 shows a signing secret once — copy it and keep it somewhere safe.

You can turn the webhook off without deleting it, edit the URL or which signals it sends, or remove it entirely — all from the same panel.

Which signals it can send

3 kinds, each its own checkbox. Tick any mix:

  • Buyer pains — the recurring problems people raise on Reddit.
  • Competitor mentions — rival products named on Reddit. See Competitor mentions.
  • Self-promotions — people plugging their own product.

All 3 are ticked to start. Untick the ones you don't want, and only the ticked signals fire the webhook.

What each send contains

Each send is one POST with a JSON body: the signal, the Reddit post it came from, and — for a buyer pain — the theme it was grouped into.

{
  "type": "signal.created",
  "project_id": "prj_9f2a",
  "signal": {
    "id": "sig_7Qd1",
    "kind": "pain",
    "quote": "I keep losing track of which subreddit a lead came from.",
    "author": "some_redditor"
  },
  "post": {
    "id": "post_3xB8",
    "permalink": "https://reddit.com/r/…",
    "title": "How do you track where leads come from?"
  },
  "sov": {
    "id": "sov_5kR2",
    "title": "Tracking where leads come from",
    "summary": "People struggle to trace which subreddit a lead started in."
  }
}

post.permalink links back to the original Reddit thread. Only buyer pains carry the sov theme — pains grouped under the same theme share one sov.id, so related pains land together on your side. Competitor mentions and self-promotions omit it.

How you know a send is really from dist0

Every send is signed. The signing secret dist0 showed you when you saved your URL is a secret code only you and dist0 know. Your tool uses it to confirm each send genuinely came from dist0 and wasn't changed on the way — so nobody can feed fake signals into your tools.

When a send doesn't go through

If your tool is down or slow to answer, dist0 tries again a few times with growing gaps before it gives up. Settings → Developer → Webhook shows a Recent failed sends list with the time and the reason for each one, so you can spot a broken endpoint and fix it.

FAQ

  • Do I need to be technical to use a webhook?

    No, not on the no-code route. Point dist0 at a tool like Zapier or Make and it takes the signals from there — no code, and no need to check the signature yourself. Wiring the webhook into your own app is the part that takes a developer.

  • Where can I send the signals?

    Anywhere your no-code tool can reach — a spreadsheet, a Slack channel, a task list, a CRM — or your own app. dist0 just delivers each signal to the URL you give it; what happens next is up to the tool on the other end. The GitHub guide walks through one full example.

  • What if I lose the signing secret?

    Open Settings → Developer → Webhook and click Roll secret to generate a new one. The old secret stops working right away, so update it in the tool that checks it.