Reddit webhooks: every keyword hit, as JSON.
Point subding at a webhook and every keyword match arrives as tidy JSON, ready to drop into Zapier, Make, n8n or your own stack.
{
"event": "keyword.match",
"keyword": "notion alternative",
"match_type": "comment",
"subreddit": "r/productivity",
"author": "example_user",
"permalink": "https://www.reddit.com/r/productivity/comments/1a2b3c/comment/kd9f0x1/",
"excerpt": "honestly after a simpler notion alternative, the workspace got out of hand",
"created_utc": 1752744060,
"matched_at": "2026-07-18T09:21:03Z"
}What the webhook gives you
Every alert is the same flat object. No proprietary envelope, nothing to decode, just the nine fields your automation reads to route it and act.
| Field | What it is |
|---|---|
event | What fired. Always keyword.match for now. |
keyword | The phrase you asked us to watch, exactly as it turned up. |
match_type | Whether it hit a post or a comment. |
subreddit | The corner of Reddit it appeared in. |
author | The username who wrote it, so you can link back and credit the source on Reddit. |
permalink | A direct link to the exact post or comment on Reddit. |
excerpt | The sentence around your keyword, for context at a glance. |
created_utc | When the post or comment went live. |
matched_at | When we caught it and sent the alert. |
How the webhook behaves
One POST per match
No batching, no nightly roll-up. It fires on the next 5-minute check.
Retries when you blink
Endpoint down? We back off and try again, never dropping the alert.
Signed, so you can trust it
A secret you set, sent over HTTPS. Verify it before you act on the body.
On all three plans
From the smallest plan up. Your tier changes the keyword count, not this.
See the comment you would have scrolled past
The line worth acting on is usually a reply buried a few deep, not the original post. We catch it, wrap the excerpt around your matched keyword, and hand your endpoint the exact JSON above.
- Excerpt included. You read the sentence, not just a bare link.
- Permalink to the exact comment. One click back to the source.
- Prefer a channel to code? The same match lands in Slack alerts too.
"honestly after a simpler notion alternative, the workspace got out of hand and half the team stopped opening it"
→ Routed to your endpoint
Route the mention before the AI does
Those “best tool for X” answers from ChatGPT, Claude and Perplexity are stitched together from Reddit threads. Get the match into your stack the moment it lands and you can be in the conversation while it is still warm and getting indexed.
How Reddit shapes AI answers →
Webhook questions, answered straight
What sits inside the payload?
A flat JSON object: the event, the keyword that matched, whether it was a post or comment, the subreddit, the author, a permalink to the exact thread, an excerpt around the match, and two timestamps. Everything you need to route it without a second lookup.
How do I check a request is genuinely from us?
Each webhook carries a signing secret you set when you create it. Verify that secret on your end before you trust the body, and because it all travels over HTTPS, nothing leaves in the clear.
What if my endpoint is having a moment?
We retry with a back-off instead of binning the alert. A short outage means the delivery waits and comes back around, so you keep the mention rather than losing it to a blip.
What actually triggers a webhook?
A single keyword match. The moment your phrase lands in a Reddit post or comment, one POST goes out for it, and match_type in the body tells you which of the two it was.
How quickly does it land?
We look at Reddit every 5 minutes, so a match at 9:02 is at your endpoint by roughly 9:07. Near real-time watching, not a digest you read the next morning.
Could a broad keyword flood my endpoint?
One POST per match, sent steadily rather than in a burst, with anything you reject retried. A noisy keyword means more of them, so if the volume climbs, tighten the phrase and it settles down.
Do I have to write code for this?
Not unless you want to. Point the webhook at a no-code catch hook and wire up the rest with clicks, or send it to your own server if you would sooner own the logic. Either route reads the same JSON.
Is a webhook a scraper or an auto-poster?
Neither. subding is read-and-notify: we watch Reddit and tell your stack when your keyword comes up. A webhook is only the outbound ping, and we never post, reply or DM on your behalf.
Wire it up once, then leave it running
Add a keyword, paste your webhook URL, and let the JSON come to you. Every plan includes webhooks, from $19 a month.
7-day free trial. No card. Cancel anytime.