MentionFox
n8n integration

MentionFox for n8n

Watch brand and competitor mentions, enrich people into verified contacts, find work emails, vet inbound leads, and check whether AI assistants recommend you — all inside your n8n workflows. Twelve ready-to-run templates included, so you do not have to imagine the wiring.

How every template is shaped
How every template is shapedWorkflow node flow: Trigger (Trigger), then MentionFox / FoxAPIs (MentionFox), then Logic (Logic), then Destination (Destination)TriggerTRIGGERMentionFox /FoxAPIsMENTIONFOXLogicLOGICDestinationDESTINATION

What the node does

The MentionFox node package adds social listening and contact intelligence to n8n. Wire it to Slack, Discord, Gmail, Google Sheets, Airtable, a webhook, or your CRM, and turn raw conversations into routed, enriched, decision-ready work.

MentionFox Trigger

Fires on each new mention of a keyword, brand, or competitor across 50+ platforms (deduped). Also: high-intent leads, AI-visibility score drops, and crisis signals.

Lead Enricher

A name plus any hint → verified email, title, company, and social links.

Find Email

A company domain (plus an optional name) → a verified work email. Charges only on a real match.

Inbound Vetter

An email, domain, or name → person enrichment + company intel + a derived seniority and confidence read, before you reply.

AI Visibility Monitor

Is your brand recommended by AI assistants versus competitors? Per-assistant standing, share of voice, and the prompts you are missing from.

MentionFox node

On-demand mention scanning across 50+ platforms, plus subject vetting, dossiers, comparisons, and AI-visibility scoring.

Get your API key

The data nodes — Lead Enricher, Find Email, Inbound Vetter, and AI Visibility Monitor — authenticate with your FoxAPIs API key. It begins fxp_live_, you create it at foxapis.com/trial, and it spends FoxAPIs credits. The cross-platform mention scan uses your MentionFox connection token from mentionfox.com/connect. The two are separate credentials and are not interchangeable.

Get your free API key at foxapis.com/trial. The n8n node runs on FoxAPIs credits — billed per call and priced at foxapis.com/pricing. MentionFox subscription plans are a separate system.

Install & import — two minutes

  1. Install the node. In n8n: Settings → Community Nodes → Install, then enter n8n-nodes-mentionfox. On self-hosted n8n you can also run npm install n8n-nodes-mentionfox. Restart n8n.
  2. Add your credentials. Create a FoxAPIs API credential and paste your fxp_live_ key from foxapis.com. For mention-scan templates, also create a MentionFox API credential and paste your token from mentionfox.com/connect.
  3. Import a template. Pick one below, then in n8n use Workflows → Import from File (or paste the JSON). Open each node and select your saved credential wherever you see a REPLACE_WITH_… placeholder.
  4. Activate. Set the trigger cadence or webhook, point the destination nodes at your channel/sheet/base, and switch the workflow on.
No auto-send, ever. Every outreach or social step in these templates ends at a draft or a Slack/Discord approval. A human always reviews and sends.

The 12 ready-to-run templates

Each template imports as a complete workflow with a setup note and per-step notes built in. Want to grab the JSON directly? The visual template gallery has a Copy workflow JSON and Download .json button on every card — import into n8n in one move. Or jump to a support section below for prerequisites, step-by-step setup, credit cost, and troubleshooting.

Credit cost at a glance

Node stepWhat it costs
Mention scan3 credits per source scanned (List Recent is free)
Lead Enricher / Enrich Author100 (Light) / 150 (Deep)
Find Email100 on a match, 0 when no email is found
Inbound Vetter100 (person) + 30 (company intel, when a work domain is present)
AI Visibility — check30, plus 100 for share of voice when you add competitors

Full numbers, setup, and node lists for every template live in templates/TEMPLATES.md in the package. Credit packs are on the FoxAPIs pricing page.

Template support

Per-template prerequisites, setup, credit cost, and troubleshooting.

1 · Brand Mention → Slack Alert

Nodes: MentionFox Trigger → Slack
Brand Mention → Slack Alert — node flowWorkflow node flow: New Mention (MentionFox), then Post to Slack (Destination)New MentionMENTIONFOXPost to SlackDESTINATION

What it does: polls the web for fresh mentions of your brand or topic across 50+ platforms and posts each new one to a Slack channel, deduped so you never see the same mention twice.

Prerequisites: a MentionFox connection token (mentionfox.com/connect); a Slack credential.

Setup: 1) set the trigger Topic to your brand and choose a poll cadence in the trigger's Poll Times. 2) Pick the Slack channel. 3) Activate.

Credit cost: 3 credits per source scanned per poll. Narrow Sources (for example reddit,twitter,hackernews) to control spend.

Troubleshooting: no messages? Confirm the token tests green in the credential, widen the time window, and check the topic actually has recent chatter. Too noisy? Tighten the topic or reduce the source list.

2 · Mention → Enrich Author → Google Sheet

Nodes: MentionFox Trigger → Lead Enricher → Google Sheets
Mention → Enrich Author → Google Sheet Lead List — node flowWorkflow node flow: New Mention (MentionFox), then Enrich Author (FoxAPIs), then Append Lead Row (Destination)New MentionMENTIONFOXEnrich AuthorFOXAPISAppend LeadRowDESTINATION

What it does: every new mention's author is resolved to a real person — title, company, verified email, social links — and appended as a lead row.

Prerequisites: MentionFox connection token; FoxAPIs API key; a Google Sheet.

Setup: set the Topic; pick your FoxAPIs credential on the enricher; choose the Sheet and tab and map columns.

Credit cost: 3 credits per source plus 100 (Light) per enrich. Enrich returns a cheap "not found" when an author cannot be resolved.

Troubleshooting: blank rows usually mean the source did not expose an author handle — keep the source list to platforms with clear authors (Twitter, Reddit, forums).

3 · Inbound Lead Webhook → Find Email + Enrich → Airtable

Nodes: Webhook → Find Email → Lead Enricher → Airtable
Inbound Lead Webhook → Find Email + Enrich → Airtable — node flowWorkflow node flow: Lead Webhook (Trigger), then Find Email (FoxAPIs), then Enrich Person (FoxAPIs), then Upsert to Airtable (Destination)Lead WebhookTRIGGERFind EmailFOXAPISEnrich PersonFOXAPISUpsert toAirtableDESTINATION

What it does: a form, CRM, or site posts a lead (name + company website); the flow finds a verified work email, enriches the person, and writes one Airtable row.

Prerequisites: FoxAPIs API key; an Airtable base and table (a Google Sheet works the same way).

Setup: copy the webhook's Production URL into your form/CRM; it expects JSON { name, website }. Set the FoxAPIs credential on both data nodes; pick the Airtable base and table.

Credit cost: 100 on an email match (0 on a miss) plus 100 for enrichment — budget about 200 per fully-resolved lead.

Troubleshooting: no email found is normal for tiny or brand-new domains; the row still writes with the enriched profile. Make sure the posted website is the company domain, not a personal address.

4 · Daily AI-Visibility Check → Score-Drop Alert

Nodes: Schedule → AI Visibility Monitor → Compare → Slack
Daily AI-Visibility Check → Score-Drop Alert — node flowWorkflow node flow: Every Morning (Trigger), then Check AI Visibility (FoxAPIs), then Compare vs Last Run (Logic), then Score Dropped? (Logic), then Alert Slack (Destination)Every MorningTRIGGERCheck AIVisibilityFOXAPISCompare vsLast RunLOGICScoreDropped?LOGICAlert SlackDESTINATION

What it does: once a day it checks whether AI assistants recommend your brand versus competitors, compares the score to yesterday's run, and alerts Slack only on a drop (or when no assistant recommends you, or a competitor overtakes you).

Prerequisites: FoxAPIs API key; a Slack credential.

Setup: set your brand domain and a comma-separated competitor list; pick the Slack channel; adjust the schedule hour to your timezone.

Credit cost: 30 for the check plus 100 for share of voice when competitors are listed — about 130 per day.

Troubleshooting: the first run stores a baseline and will not alert; alerts begin from the second day. Want every run logged, not just drops? Add a Sheets node after the compare step.

5 · Competitor Mention → Vet Company → Slack Digest

Nodes: MentionFox Trigger → Inbound Vetter → Aggregate → Slack
Competitor Mention → Vet Company → Slack Digest — node flowWorkflow node flow: Competitor Mention (MentionFox), then Vet Author / Company (FoxAPIs), then Build Digest (Logic), then Post Digest (Destination)CompetitorMentionMENTIONFOXVet Author /CompanyFOXAPISBuild DigestLOGICPost DigestDESTINATION

What it does: watches for mentions of a competitor (people shopping around), vets the person and company behind each one, batches them, and posts a single Slack digest.

Prerequisites: MentionFox connection token; FoxAPIs API key.

Setup: set the Topic to a competitor name or handle; add a vetting-context line; pick the Slack channel.

Credit cost: 3 credits per source plus, per mention, 100 (enrich) and 30 (company intel, only when a work domain is present).

Troubleshooting: a quiet digest means low competitor chatter in the window — widen Hours Back or add sources.

6 · Mention → Draft Reply + Hashtags → Slack Approval

Nodes: MentionFox Trigger → Set → RiteKit Hashtags → Slack
Mention → Draft Reply + RiteKit Hashtags → Slack Approval — node flowWorkflow node flow: New Mention (MentionFox), then Draft Reply (Logic), then RiteKit Hashtags (Logic), then Compose Draft (Logic), then Send for Approval (Destination)New MentionMENTIONFOXDraft ReplyLOGICRiteKitHashtagsLOGICCompose DraftLOGICSend forApprovalDESTINATION

What it does: for each new mention it drafts a reply, fetches relevant hashtags, and posts the draft to Slack for a human to approve and post manually. Nothing is auto-posted.

Prerequisites: MentionFox connection token; a RiteKit client_id (used as a query-auth credential); a Slack credential.

Setup: set the Topic; add a Generic / Query Auth credential with name client_id and your RiteKit value; pick the Slack channel where your team approves drafts.

Credit cost: 3 credits per source for the scan. Hashtags are billed on your RiteKit plan, not FoxAPIs credits.

Troubleshooting: empty hashtags usually mean the query-auth credential is missing or the text field was blank — confirm both before re-running.

7 · High-Follower Author → Enrich → Priority Ping

Nodes: MentionFox Trigger → IF → Lead Enricher → Slack
High-Follower Author → Enrich → Priority Ping — node flowWorkflow node flow: New Mention (MentionFox), then Big Audience? (Logic), then Enrich Author (FoxAPIs), then Priority Ping (Destination)New MentionMENTIONFOXBig Audience?LOGICEnrich AuthorFOXAPISPriority PingDESTINATION

What it does: watches mentions but acts only when the author has a large audience; those get enriched and trigger a priority Slack ping so you respond to influential voices fast.

Prerequisites: MentionFox connection token; FoxAPIs API key; a high-priority Slack channel.

Setup: set the Topic; set the follower threshold in the IF node (default 5,000); pick the channel.

Credit cost: 3 credits per source per poll; enrichment (100/150) runs only for authors past the floor, keeping spend low.

Troubleshooting: nothing passing the filter? Some sources do not report follower counts — the IF reads several common fields, but a platform without that data will never pass. Lower the threshold or scope to platforms that expose audience size.

8 · Weekly Mentions Digest → Sheet + Email Draft

Nodes: Schedule → MentionFox (List Recent) → Sheets + Gmail draft
Weekly Mentions Digest → Sheet + Email Draft — node flowWorkflow node flow: Every Monday (Trigger), then List Recent Mentions (MentionFox), then Extract Mentions (Logic), then Log to Sheet (Destination), then Build Summary (Logic), then Weekly Email Draft (Destination)Every MondayTRIGGERList RecentMentionsMENTIONFOXExtractMentionsLOGICLog to SheetDESTINATIONBuild SummaryLOGICWeekly EmailDraftDESTINATION

What it does: once a week it pulls recent mention activity, logs every mention to a Sheet, and writes a summary Gmail draft for you to review and send. The email is a draft, never auto-sent.

Prerequisites: MentionFox connection token; a Google Sheet; a Gmail credential.

Setup: set the weekly schedule; choose the Sheet and tab; set the Gmail draft recipient and subject.

Credit cost: free — List Recent costs 0 credits.

Troubleshooting: empty digest? List Recent reflects your recent activity in the product; run a scan or two first so there is history to summarize.

9 · Mention → Enrich → Fit Score → Route Hot Leads

Nodes: MentionFox Trigger → Lead Enricher → Code → IF → Sheets (Hot / All)
Mention → Enrich → Fit Score → Route Hot Leads — node flowWorkflow node flow: New Mention (MentionFox), then Enrich Author (FoxAPIs), then Fit Score (Logic), then Hot Lead? (Logic), then Hot Leads (Destination), then All Leads (Destination)New MentionMENTIONFOXEnrich AuthorFOXAPISFit ScoreLOGICHot Lead?LOGICHot LeadsDESTINATIONAll LeadsDESTINATION

What it does: enriches each mention's author, scores fit from seniority, identity confidence, and a verified email, then routes hot leads to a Hot tab and everyone else to an All tab.

Prerequisites: MentionFox connection token; FoxAPIs API key; a Sheet with Hot and All tabs.

Setup: set the Topic; pick the FoxAPIs credential; point both Sheets nodes at your spreadsheet. Tune the score weights or the 60-point threshold in the Code node if you like.

Credit cost: 3 credits per source plus 100 (Light) per enrich.

Troubleshooting: everything landing in All? Lower the threshold, or check that enrichment is resolving titles — fit leans on seniority.

10 · Scheduled Multi-Keyword Scan → Dedupe → Airtable

Nodes: Schedule → Code → MentionFox (Scan) → Code → Airtable
Scheduled Multi-Keyword Scan → Dedupe → Airtable — node flowWorkflow node flow: Every Few Hours (Trigger), then Keywords (Logic), then Scan Keyword (MentionFox), then Flatten Mentions (Logic), then Dedupe (across runs) (Logic), then Save New to Airtable (Destination)Every FewHoursTRIGGERKeywordsLOGICScan KeywordMENTIONFOXFlattenMentionsLOGICDedupe(across runs)LOGICSave New toAirtableDESTINATION

What it does: on a schedule it scans several keywords in one run, flattens the results, drops anything already seen (deduped across runs), and writes new mentions to Airtable.

Prerequisites: MentionFox connection token; an Airtable base and table.

Setup: edit the keyword list in the first Code node; narrow Sources; set the cadence; pick the base and table.

Credit cost: 3 credits per source per keyword. Three keywords across four sources is about 36 credits per run.

Troubleshooting: duplicates slipping through? The dedupe keys on the post URL — a source without a stable URL falls back to a content fingerprint, which is less precise. Keep to URL-bearing sources for clean dedupe.

11 · Crisis Signal → Immediate Slack + Discord Page

Nodes: MentionFox Trigger (crisis) → Slack + Discord
Crisis Signal → Immediate Slack + Discord Page — node flowWorkflow node flow: Crisis Watch (MentionFox), then Page Slack (Destination), then Page Discord (Destination)Crisis WatchMENTIONFOXPage SlackDESTINATIONPage DiscordDESTINATION

What it does: polls on a fast cadence and fires the moment a mention contains a crisis keyword (lawsuit, outage, breach, scandal, layoff, bankruptcy), paging both Slack and Discord.

Prerequisites: MentionFox connection token; a Slack credential; a Discord channel webhook.

Setup: set the Topic and edit the crisis keyword list; set a short poll interval; point Slack at a channel and Discord at a webhook.

Credit cost: 3 credits per source per poll — scope sources tightly on a fast cadence.

Troubleshooting: false pages? Trim the keyword list to terms that are unambiguous for your brand. Missing pages? Shorten the poll interval and confirm the keywords match how people actually phrase incidents.

12 · Inbound Applicant/Lead Vetter → Slack Approval Card

Nodes: Form Trigger → Inbound Vetter → IF → Slack (approve / review)
Inbound Applicant/Lead Vetter → Slack Approval Card — node flowWorkflow node flow: Inbound Form (Trigger), then Vet Inbound (FoxAPIs), then Strong Fit? (Logic), then Approval Card (Destination), then Review Card (Destination)Inbound FormTRIGGERVet InboundFOXAPISStrong Fit?LOGICApproval CardDESTINATIONReview CardDESTINATION

What it does: an inbound form submits name and email; the flow vets the person and their company and posts a Slack approval card with a derived seniority and confidence read plus a recommended action. A human decides — nothing is auto-replied.

Prerequisites: FoxAPIs API key; a Slack credential.

Setup: share the form URL (or swap in a Webhook from your ATS/CRM); set the FoxAPIs credential and a vetting-context line; pick the Slack channel.

Credit cost: 100 (enrich) plus 30 (company intel) when a work-email domain is present; free-webmail addresses skip the company leg.

Troubleshooting: low confidence on real people is common for those with little public footprint — the card still posts to the review lane so a human can decide.

Ship a workflow today

Install n8n-nodes-mentionfox, grab your free key at foxapis.com/trial, and import a template. Credits are pay-as-you-go.

See FoxAPIs credit pricing

Related reading