Turn your Reddit buyer pains into GitHub issues

Get every recurring buyer pain dist0 finds into GitHub as a tracked issue — one issue per theme, and every new Reddit post about that theme lands as a comment on the same issue. The backlog stays free of duplicates: a pain people keep raising is one item with the threads stacking underneath it, not ten near-identical issues.

How it fits together

dist0 groups the Reddit posts it reads into buyer-pain themes — one theme per recurring problem. Each time a new post joins a theme, dist0 can push it to a URL you choose (a webhook). You point that URL at a no-code tool, and the tool does 2 things with it:

1. Find or create the GitHub issue for that theme — matched by the theme's id, so the first post creates the issue and every post after finds the same one.
2. Add a comment to that issue with the new Reddit quote and a link to the post.

We'll use Zapier to connect the two. Make and n8n work the same way — see the note at the end. If you'd rather script it, there's a native GitHub API version at the bottom too.

What dist0 sends

Every time a new buyer pain is found, dist0 sends one POST to your URL with a JSON body. The parts you'll use:

Step 1 — Make the trigger in Zapier

1. Create a new Zap and pick Webhooks by Zapier as the trigger.
2. Choose the Catch Hook event.
3. Zapier shows you a Custom Webhook URL. Copy it.

Step 2 — Point dist0 at that URL

1. Open Settings → Webhook in your dist0 dashboard.
2. Paste the Zapier URL into the URL field.
3. Under What to send, tick Buyer pains and untick the rest.
4. Click Save.

Back in Zapier, click Test trigger. Zapier listens on the Catch Hook and captures the next buyer pain dist0 sends, then uses it as the sample for the GitHub steps below. It has to wait for the next new pain, so if none arrives yet you can still build the steps and type the field names by hand — they're all in What dist0 sends above.

The full webhook setup — the signing secret, retries, and how to verify a send really came from us — is covered in the Webhooks guide. Zapier's Catch Hook doesn't need the signature check, so you can skip it here.

Step 3 — Find or create the issue

Add a GitHub action step and pick Find Issue. This is the step that keeps one issue per pain instead of a pile of duplicates.

1. Turn on Create GitHub Issue if it doesn't exist yet (a checkbox on the Find Issue step).

2. In the search query, match on a unique token built from the theme id — for example:

   [dist0:{{sov.id}}] in:title

   Copy

3. For the issue it creates, set:

   • Title — {{sov.title}} [dist0:{{sov.id}}]. The [dist0:…] token at the end is what the search matches on, so the same theme always resolves to the same issue.
   • Body — {{sov.summary}}.
   • Label (optional) — from-reddit, so these issues stay easy to filter.

The first post of a theme creates the issue; every post after finds it and moves on to the comment.

Step 4 — Add the Reddit post as a comment

Add one more GitHub action step and pick Create Comment. Point it at the issue the previous step found or created, and set the comment body to:

New Reddit post about this pain: "{{signal.quote}}" — {{post.permalink}}

Turn the Zap on. From now on, each new Reddit post about a pain becomes a comment, and a brand-new pain opens a fresh issue — no duplicates, no copy-paste.

Good to know

• One issue per theme, comments stack. This is the whole point: a recurring pain stays one tracked item, unlike a per-post feed that files a fresh row for every thread.
• A brand-new theme with several posts at once. When a new theme forms from a few posts in the same run, the first post creates the issue and the next ones should find it. GitHub's issue search can lag a few seconds, so once in a while two posts of a new theme both create an issue before the first one is searchable. It's rare and easy to spot — merge the pair by hand. To avoid it entirely, add a short Delay step in Zapier before the Find Issue step.

Other ways to run it

• Make or n8n. Same 3 pieces: a custom-webhook trigger, a GitHub search / create issue module keyed on the [dist0:{{sov.id}}] title token, and a GitHub create comment module. Wire them in that order.
• Native GitHub API. If you'd rather script it, each webhook is a small find-or-create: search issues for the [dist0:<sov.id>] marker in the title, then create the issue or add a comment depending on whether one came back. That's about 3 REST calls, and you can run it free on a schedule with GitHub Actions.