May 5th, 2026
New Feature
Improved
A round of improvements landed this week. Various improvements to our signals UX, the ability to add new competitors and ICPs with one click through Genie, UI for editing and re-ordering your Intel data, improved reply drafts, and more.
Want more control over the data you add or change? We’ve added a complete brand new UI for editing, deleting, and organizing all of your data on the Intel page. This applies to every single data point in the Intel, including USPs, KSPs, ICPs, Competitors, and Sub-reddits.


You can now chat with our AI agent, Genie, and ask it to add a specific competitor or ICP to your Intel data with a single prompt.
For example: “add competitor Vanta”. Genie will do its magic, automatically researching and adding competitor data without any manual input from you. Instead of spending 30 minutes researching and filling in competitor fields, you can now expand your data in seconds.
We’ve added AI Anti-slop Rules. The reply prompt now actively avoids the patterns that make AI-generated comments easy to spot: generic openers, em-dashes, "in today's fast-paced world" energy, throat-clearing intros, lazy closers, hedge phrases like "honestly" or "to be fair", and the "not just X, it's Y" structure. The goal is replies that read like a human in the thread.
When you remove a relevancy rule, every thread previously scored in the last seven days against it is automatically re-scored. Before, old threads kept their original score, and you had to wait for new signals to come through to feel the change. Now the inbox reflects your current rules, not the rules you had last week.
Better Keyword matching – fixes a class of false positives. For example, if you add the competitor name “Vanta” you will not get signals mentioning “advantage”.
Inbox search fixed – better ranking, highlighting, and navigation.
Fixed: Project Creation Rescue Flow – If the project setup encounters an error, you now get diagnostics and a guided path to recovery instead of a stuck state.
April 28th, 2026
The signal inbox categories have been renamed from "Hot Leads," "High Intent," "Trust Builders," and "Inspiration" to score ranges:
85%+
75-85%
65-75%
50-65%

The old names implied a sales funnel lens that didn't always fit. A signal scoring 85%+ isn't always a sales lead - it could be a Reddit thread worth being cited in for AEO, for example. The score reflects both relevance and buying intent, but a high score doesn't mean the signal is only useful for sales.
"Hot Leads" also implied recency, but recency isn't part of the scoring formula. For that, there's the time range filter and the most recent sorting option.
The percentage ranges map directly to how Signal Score works: each signal is scored from 50% to 100% using a proprietary formula that factors in relevance and buying intent. The category names now reflect that scale as-is, without adding a layer of interpretation on top.
April 15th, 2026
New Feature

Sensorhub now sends signals to any tool that accepts webhooks - Clay, Make.com, Zapier, n8n, or your own endpoint.
Available on Pro (up to 3 webhooks) and Enterprise (up to 10).
Go to your project's Settings and click "Add Webhook”:

Paste the destination URL, and give it a name so you can tell your webhooks apart inside Sensorhub:

Hit "Test" to send a sample event and confirm the receiving app picked it up:

Here's what data we send on every signal:
{
"event": "signal.created",
"timestamp": "2026-04-15T09:13:53.310Z",
"webhook_id": "cmnztujs40001s57wffv4rx2n",
"signal_id": "test_signal_001",
"product_id": "test_product_001",
"product_name": "Sensorhub",
"product_url": "https://example.com",
"post_title": "[TEST] Looking for a tool to automate outreach",
"post_body": "This is a test webhook payload. We are looking for a solution to help our team automate cold outreach and follow-ups.",
"post_url": "https://reddit.com/r/SaaS/comments/test123",
"post_author": "u/test_user",
"post_source": "REDDIT",
"post_subreddit": "SaaS",
"post_created_at": "2026-04-15T09:13:53.310Z",
"score": 0.92,
"category": "hot_leads",
"category_label": "Hot Leads",
"reasoning": "TEST: User is actively seeking a solution matching your product."
}Make sure you receive the data successfully in your external app. Here’s an example from Encharge:

Once your webhook is live, the delivery log tracks every event with success and failure rates, so you can spot broken integrations before they cost you leads:

We are super excited to see what you make with this integration and what playbooks you implement with all the hundreds of signals!