Add live web search to n8n, Make, or Zapier workflows
n8n users: install the native Superhighway community node — one install, five operations (search, news, images, read page, research), no manual HTTP wiring. Make/Zapier users: one HTTP call with a Bearer key.
n8n — community node (recommended)
The n8n-nodes-superhighway package adds a native Superhighway node to your n8n instance — no HTTP Request wiring needed.
- Go to Settings → Community Nodes → Install.
- Enter:
n8n-nodes-superhighwayand click Install. - Go to Credentials → New → Superhighway API, paste your API key from /pricing (free, 1,000 calls/month).
- Add a Superhighway node to any workflow. Choose an operation: Web Search, News Search, Image Search, Read Page, or Research. Enter a query (or use an expression like
{{ $json.topic }}). Execute.
The node outputs parsed JSON — wire results[0].title, results[0].url, etc. into the next step. Pair with a Code node to format as Markdown:
const results = $input.first().json.results;
const md = results.map(r => `- [${r.title}](${r.url})\n ${r.description}`).join("\n");
return [{ json: { markdown: md } }];
n8n — HTTP Request node (manual)
If you prefer not to install a community node, the HTTP Request approach works too:
- Add an HTTP Request node.
- Method:
GET· URL:https://superhighway.walls.sh/search - Query Parameters: add
q→ your search term,limit→5 - Authentication: Generic Credential Type → Header Auth · Name:
Authorization· Value:Bearer YOUR_API_KEY
Same pattern works for /news, /images, /scrape, and /research.
Make (Integromat)
- Add an HTTP → Make a request module.
- URL:
https://superhighway.walls.sh/search?q={{ your_variable }}&limit=5 - Method:
GET - Headers: add
Authorization→Bearer YOUR_API_KEY - Parse response: enable Parse response. The
resultsarray is available in subsequent modules.
Zapier
- Add a Webhooks by Zapier → GET action (or use the built-in Code by Zapier step).
- URL:
https://superhighway.walls.sh/search?q=SEARCH_TERM&limit=5 - Headers:
Authorization: Bearer YOUR_API_KEY - Zapier parses the JSON response — map
results__0__title,results__0__url, etc. to the next step.
Common automation use cases
| Workflow | Endpoint | Trigger |
|---|---|---|
| Daily news digest → email / Slack | /news?q=topic | Schedule (daily) |
| Research a new lead before CRM entry | /research?q=company+name | New row in Google Sheets |
| Price / product monitoring | /search?q=product+name+price | Schedule (hourly) |
| Pull page content into Notion | /scrape?url=PAGE_URL | New bookmark / URL |
| Image lookup for content creation | /images?q=keyword | Webhook from CMS |
Getting your API key
Go to /pricing, enter your email, and get an API key instantly — 1,000 calls/month free, no credit card. Paid plans start at $9/month (50,000 calls). The key works in any HTTP tool as Authorization: Bearer YOUR_KEY.
Prefer autonomous agents or wallets instead of API keys? See the x402 pay-per-call guide.