How to track competitor mentions with n8n

Competitor chatter is a buying signal

Your own brand mentions tell you how you are perceived. Your competitors' mentions tell you who is in market right now. The two are not the same, and the second is often more valuable for a sales-minded team. A person asking "is there a better option than [competitor]?" or complaining that a competitor lacks a feature is mid-decision. They have named the category, named a pain, and made it public. That is a warmer starting point than any cold list, because the intent is self-declared and the timing is current.

The catch is that competitor chatter is noisy and constant, and most of it is not a lead. Employees, fans, and journalists all mention competitors without any buying intent. So the goal is not to capture every mention — it is to capture them, judge who is behind each one, and surface only the people worth a look, in a form you will actually read.

n8n is the right tool because it can do the catching, the judging, and the surfacing in one flow, then drop the result wherever your team already works.

Three failure modes to design around

Teams that try to track competitors by hand or with a naive automation hit predictable problems:

• Single-platform blindness. Watching one network misses the forum threads, community posts, and comparison discussions where buyers actually deliberate. Coverage has to be broad.
• Raw-hit overload. A firehose of every competitor mention is unreadable, so it gets ignored. The output needs to be batched and triaged, not streamed.
• No idea who said it. A mention without context on the author is just a quote. You need at least a read on who they are — seniority, company, whether they look like a buyer — before it is worth anyone's time.

A good competitor tracker is designed against all three from the start.

The workflow shape

Here is the pattern that handles those failure modes:

1. A mention trigger pointed at a competitor. Set the topic to the competitor's name or handle. The trigger scans many platforms, dedupes, and emits each new mention. You can run one workflow per competitor or widen the topic to a category term.
2. A vetting step. For each mention, vet the person and, where a work domain is available, the company behind it. This is what turns a raw quote into "a director-level person at a mid-size company, medium confidence, worth a look." Vetting that returns a seniority read and a confidence score is what makes the digest triage-able.
3. An aggregate, then a digest. Combine the poll's vetted mentions into one item and post a single Slack digest — one line per person with their seniority, confidence, and a recommended action. One readable message beats twenty pings.

Because everything arrives as structured data, you can tighten the funnel however you like: only digest mentions where the vetting confidence clears a bar, or where the person reads as a decision-maker, or where the language signals frustration rather than praise.

Vet before you act — and never auto-reach

The temptation with a warm competitor signal is to fire off outreach automatically. Resist it. Two reasons. First, automated outreach on a half-understood signal is how you embarrass your brand — reaching out to a competitor's own employee, or to someone praising the competitor, reads as careless. Second, the highest-converting response to a competitor mention is a thoughtful, human reply that references the person's actual words. That is a human's job, informed by good vetting, not a bot's.

So the right shape ends at a digest or an approval, never an auto-send. The workflow does the tedious part — catching the mention, vetting the person, summarizing — and a human makes the call on who, if anyone, to engage. That division of labor is both safer and more effective.

What it costs

Two cost levers matter here. The scan costs a few credits per source per poll, so scope the source list to where competitor deliberation actually happens. Vetting costs more per person because it does real resolution, so vet only the mentions worth it — gate on relevance or recency before the vetting node, and let the company-intel leg run only when a work domain is present. Used this way, a competitor tracker stays inexpensive while still surfacing the handful of genuinely warm signals each day.

Turning a digest into a habit

The quiet advantage of a batched digest over a stream of pings is that it becomes a ritual rather than an interruption. A single message that arrives a few times a day, each line a vetted person with a seniority read and a recommended action, is something a salesperson will actually open and scan. A firehose of raw mentions is something they will mute by Friday. Design for the habit: keep the digest short, lead with the highest-confidence people, and make every line scannable in a second. Over a few weeks the pattern compounds — your team builds an instinct for which competitor signals are worth a reply, the vetting confidence calibrates which names deserve attention, and the whole motion shifts from reactive monitoring to a steady, low-effort source of warm conversations. The pipeline does the catching and judging; the human keeps the relationship-building, which is the part that does not automate well anyway.

On credits: the MentionFox n8n node runs on FoxAPIs credits — priced at foxapis.com/pricing and separate from MentionFox subscription plans. Get your free API key at foxapis.com/trial.

Questions, answered