You do not need a social-listening stack to find out when someone wants to replace a tool you compete with.
If the author already posted it in public — "looking for an alternative to X", "need to switch before renewal" — you can poll a scored feed, keep only the rows that name that tool, and push a Slack message with the original thread link. The script at the heart of this is 20 lines of Python. The rest of the article is the request shape, the response shape, and how not to waste quota or annoy people.
The feed I will use is B2B Buying Intent Signals on RapidAPI. It scans public posts on Reddit, Hacker News, Lobsters, Dev.to, and Stack Exchange Software Recommendations every six hours, scores buying intent from 1 to 10, and keeps the high-intent ones (score 7+ by default). At the time of writing the live feed holds ~100 high-intent B2B signals. The tools that show up most often today are Shopify, then Supabase, then ecommerce and payments tools such as Veeqo, Vesyl and Stripe, and hosting/dev tools such as Railway, Lovable, Bolt and GitHub.
What you need
- A RapidAPI account and a subscription to the API. The BASIC plan is free (200 calls/month).
- Your
X-RapidAPI-Keyfrom the API playground. Also copy theX-RapidAPI-Hostvalue shown there; it is typicallyb2b-buying-intent-signals.p.rapidapi.com. - A Slack Incoming Webhook for the channel that should receive alerts.
- Python 3 and
requests(pip install requests).
Set two environment variables and, optionally, the tool name (the default below is Shopify, currently the most-mentioned tool in the feed — change it to the product you actually care about):
export RAPIDAPI_KEY="your-rapidapi-key" export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..." export TOOL="Shopify" The endpoint
GET https://b2b-buying-intent-signals.p.rapidapi.com/api/v1/signals Query parameters, all optional:
| Parameter | Default | Notes |
|---|---|---|
tool | (none) | Case-insensitive exact match on a mentioned_tools entry. tool=shopify matches "Shopify", but not "Shopify Plus" unless that exact string is in the list. Max 80 characters. |
min_score | 7 | Integer 1–10. 7–8 is a clear need; 9–10 is urgent (budget, deadline, "need this now"). |
urgency | (none) | low, medium, or high. |
category | (none) | ai_tools, saas_alternative, automation, dev_tools, or marketing_growth. |
platform | (none) | reddit, hackernews, lobsters, devto, or stackexchange. |
limit | 20 | Maximum 50. |
Authenticate with both headers, and go through RapidAPI — do not call the origin server directly:
X-RapidAPI-Key: YOUR_RAPIDAPI_KEY X-RapidAPI-Host: b2b-buying-intent-signals.p.rapidapi.com A successful body always looks like { "success": true, "count": <n>, "data": [ ... ] }. The script below calls GET /api/v1/signals?tool=shopify&min_score=7. I am showing a real public signal from the same endpoint with tool=veeqo (Veeqo and Vesyl both appear in the current feed), so every field is one you can actually get back. The author has been anonymized.
{ "success": true, "count": 1, "data": [ { "id": "16430170-0028-4416-8c4a-96e3699d9f7d", "platform": "reddit", "source_url": "https://www.reddit.com/r/ecommerce/comments/1y0su3v/veeqo_alternatives_that_arent_tied_to_amazon/", "title": "Veeqo alternatives that arent tied to Amazon?", "author": "user_820ea5", "intent_score": 8, "category": "saas_alternative", "problem_summary": "Ecommerce seller using Amazon-owned Veeqo wants a carrier- and channel-neutral order routing/shipping alternative because Amazon is only 20% of sales and they are uneasy routing order data through a competitor.", "mentioned_tools": ["Veeqo", "Vesyl"], "urgency": "medium", "created_at": "2026-11-20T07:23:19.512Z" } ] } created_at is UTC, and the list is newest first. Dedup on id, not on the title. Other tool values that currently return rows include shopify, supabase, stripe and railway.
If something is wrong you get { "success": false, "error": "..." }. Typical cases:
-
401— missing or invalid RapidAPI key, or the request did not go through the RapidAPI gateway -
400— invalidcategory,platform,urgency,min_score,limit, ortool
The 20-line script
Save this as slack_intent_alert.py.
import json, os, pathlib, requests TOOL, SEEN = os.environ.get("TOOL", "Shopify"), pathlib.Path("seen_ids.json") seen = set(json.loads(SEEN.read_text())) if SEEN.exists() else set() host = "b2b-buying-intent-signals.p.rapidapi.com" res = requests.get(f"https://{host}/api/v1/signals", timeout=20, headers={"X-RapidAPI-Key": os.environ["RAPIDAPI_KEY"], "X-RapidAPI-Host": host}, params={"tool": TOOL, "min_score": 7, "limit": 20}) res.raise_for_status() body = res.json() assert body.get("success"), body.get("error", "API error") fresh = [s for s in body.get("data", []) if s["id"] not in seen] for s in fresh: tools = ", ".join(s.get("mentioned_tools") or []) text = (f"*Buying intent {s['intent_score']}/10 · {s['urgency']} · {s['platform']}*\n" f"{s['title']}\n{s['problem_summary']}\n" f"Tools: {tools or 'n/a'} · <{s['source_url']}|Open thread>") requests.post(os.environ["SLACK_WEBHOOK_URL"], json={"text": text}, timeout=20).raise_for_status() seen.add(s["id"]) SEEN.write_text(json.dumps(sorted(seen))) print(f"Posted {len(fresh)} alert(s) for tool={TOOL}") Run it once:
python slack_intent_alert.py The first run may post several messages if the feed already has matching signals. After that, seen_ids.json keeps it quiet unless a new id appears. If you only want the urgent ones, add "urgency": "high" to params.
A Slack message from the example payload above looks like this:
Buying intent 8/10 · medium · reddit
Veeqo alternatives that arent tied to Amazon?
Ecommerce seller using Amazon-owned Veeqo wants a carrier- and channel-neutral order routing/shipping alternative because Amazon is only 20% of sales and they are uneasy routing order data through a competitor.
Tools: Veeqo, Vesyl · Open thread
The script defaults to TOOL=Shopify. Use the same file with TOOL=Veeqo, TOOL=Stripe, TOOL=Supabase or TOOL=Railway if that is the market you sell into.
Put it on a schedule (and do not over-poll)
New signals are collected every six hours, so polling faster than that mostly burns quota. Four runs a day is about 120 calls a month, which fits in the 200-call free plan and leaves room to try filters in the playground.
A cron line that trails the collector slightly:
25 */6 * * * RAPIDAPI_KEY=... SLACK_WEBHOOK_URL=... TOOL=Shopify /usr/bin/python3 /path/to/slack_intent_alert.py On GitHub Actions, a scheduled workflow with those values in Actions secrets is the same idea. Use a persistent seen_ids.json (a repo-untracked file on a small VM, or an artifact / a tiny database). If the seen-id file resets, you will re-alert on old rows.
/api/v1/stats is there if you want a weekly pulse rather than a per-tool alert. It returns 7-day volume and average intent score, overall and by category. The shape is:
{ "success": true, "data": { "period": { "days": 7, "from": "<ISO-8601 UTC start>", "to": "<ISO-8601 UTC end>" }, "total_signals": "<integer>", "avg_intent_score": "<number, rounded to 2 decimals>", "by_category": [ { "category": "saas_alternative", "count": "<integer>", "avg_intent_score": "<number>" }, { "category": "ai_tools", "count": "<integer>", "avg_intent_score": "<number>" }, { "category": "automation", "count": "<integer>", "avg_intent_score": "<number>" }, { "category": "dev_tools", "count": "<integer>", "avg_intent_score": "<number>" }, { "category": "marketing_growth", "count": "<integer>", "avg_intent_score": "<number>" } ] } } Those five categories are always present in by_category, including when a count is zero. I am showing the schema only — not a live snapshot, because the numbers change as the feed does.
A few sharp edges worth knowing
-
toolis exact, not a substring. That is deliberate:tool=metashould not match a tool whose name merely contains "meta".tool=shopifymatches"Shopify", but if the model stored"Shopify Plus", that filter will not hit it. When in doubt, pull a page withouttooland look atmentioned_tools. -
mentioned_toolscan be empty. The scorer only lists names that were explicitly cited. Your Slack line should tolerate an empty list. - Authors are whatever the source published. Some platforms have a public username, some do not, and deleted authors come through as
null. Do not make the Slack message depend onauthor. - Read the thread before you talk to anyone. The valuable field is
source_url. Join the public conversation, or write a note that refers to the actual problem. A generic "saw you were looking for a tool" email is how this kind of feed gets a bad name.
If you outgrow a webhook, the same loop can post to a CRM, a sequencer, or a Slack bot via chat.postMessage. The API part does not change: poll /api/v1/signals, filter, remember id.
