Home · Integrations · n8n
In progress
Use FoxAPIs from n8n today, with the dedicated node coming.
A purpose-built FoxAPIs node is being built in a sibling repo. While that's in flight, the generic HTTP Request node connects you to every FoxAPIs tool today via JSON-RPC. Same endpoint. Same auth. About 30 seconds to wire up.
Honest status: dedicated node in progress, ETA tracking weekly. The HTTP Request approach below is fully supported and stable.
Step-by-step install (HTTP Request route)
- In your n8n workflow, add an HTTP Request node.
- Method: POST. URL: https://www.mentionfox.com/mcp.
- Authentication: Header Auth. Header name: Authorization. Value: Bearer {{$credentials.foxapisKey}}.
- Body type: JSON. Paste the JSON-RPC envelope (template below) and substitute the tool name and arguments for the call you want.
- Connect upstream nodes' data into the arguments object as needed.
JSON-RPC envelope template
{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "vet_person", "arguments": { "name": "{{$json.lead_name}}" } } }
Three worked examples
Example 1 — Daily lead-finder workflow
Schedule trigger (daily) → HTTP Request scan_mentions → HTTP Request score_intent → Slack message of top 10. The whole flow runs in under 8 seconds.
Example 2 — Inbox enrichment
Email trigger → HTTP Request find_contact with the sender's name → HTTP Request enrich_person → write back to your CRM via the appropriate node.
Example 3 — Weekly GEO digest
Schedule trigger (weekly) → HTTP Request get_geo_score → HTTP Request get_geofixer_top_actions → format → email to stakeholders.
Common errors & fixes
401 unauthorisedHeader name must be Authorization, not authorization on some n8n versions.JSON parseBody has unescaped quotes from a previous node. Use the n8n expression editor's JSON-stringify helper.422 from upstreamArguments object is missing a required field. Check the tool page schema.timeout on dossierIncrease the HTTP Request node timeout to 30 seconds for get_dossier deep mode.