01
Install n8n-nodes-crawlora
In n8n, open Settings, then Community Nodes, choose Install, and enter n8n-nodes-crawlora.
Developer guides
Call Crawlora's structured web data APIs from n8n with the n8n-nodes-crawlora community node or the built-in HTTP Request node — no custom code — and automate search, maps, e-commerce, and finance workflows.
Verified HTTP pattern
GET /bing/search
Request
GET https://api.crawlora.net/api/v1/bing/search?q=best+CRM+software&country=us&count=10
x-api-key: $CRAWLORA_API_KEYBase URL
https://api.crawlora.net/api/v1
Auth header
x-api-key
Example endpoint
GET /bing/search
n8n is an open-source workflow automation tool. Crawlora publishes a community node, n8n-nodes-crawlora, that exposes a curated set of sources as n8n resources and operations and can be used as a tool by the AI Agent node. n8n's built-in HTTP Request node calls any Crawlora endpoint directly, and this guide includes a ready-to-import workflow template for it.
Developer workflow
n8n connects services without code. Crawlora returns normalized JSON from supported public platforms, so you can fetch data with the HTTP Request node and pass it to spreadsheets, databases, Slack, or AI nodes without maintaining parsers. The same agent-native structured data also backs Crawlora's hosted MCP tools when you move from automations to agents.
Developer workflow
The n8n-nodes-crawlora community node covers the most-used sources: web page content, search engines, maps, finance, e-commerce, social platforms, app stores, and reviews. For an endpoint the node does not list, use the HTTP Request node below.
Package page with the current version and install name.
Open repoSupported resources, credentials, and development notes.
Open repo01
In n8n, open Settings, then Community Nodes, choose Install, and enter n8n-nodes-crawlora.
02
Paste your API key into a Crawlora API credential. The node sends it as the x-api-key header on every request.
03
Add the Crawlora node to a workflow, choose the data source as the resource and the endpoint as the operation, fill in the fields, and run it.
Developer workflow
01
Set the method and URL to a Crawlora endpoint, for example POST https://api.crawlora.net/api/v1/google/map/search.
02
Send an x-api-key header. Store the key in an n8n credential or environment variable (for example {{ $env.CRAWLORA_API_KEY }}) rather than hardcoding it in the node.
03
Set 'Send Body' to JSON and provide the request parameters, such as query and limit for Google Maps search.
Developer workflow
Download the template and import it in n8n via Workflows then Import from File. It wires a manual trigger to a Crawlora Google Maps search call and splits the results into individual place items.
Developer workflow
The HTTP Request node sends this request; map the fields into your downstream nodes.
curl -X POST https://api.crawlora.net/api/v1/google/map/search \
-H "x-api-key: $CRAWLORA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "coffee shops in Austin, TX", "limit": 20}'Developer workflow
Developer workflow
Use Crawlora for structured public web data workflows. Customers are responsible for compliance with applicable laws, third-party rights, platform rules, and Crawlora terms. Keep API keys server-side, validate inputs, and avoid collecting or storing unnecessary sensitive data.
Read Crawlora termsDeveloper workflow
Use these pages to move between endpoint discovery, examples, pricing, and responsible-use guidance.
Developer workflow
Common questions for this Crawlora developer integration path.
Yes. Install the n8n-nodes-crawlora community node from Settings, then Community Nodes. It covers a curated set of sources; for any other endpoint, use n8n's built-in HTTP Request node, for which this guide includes a ready-to-import workflow template.
With the community node, paste your key into a Crawlora API credential. With the HTTP Request node, send it as an x-api-key header and store it in an n8n credential or environment variable rather than hardcoding it in the node.
Yes. Replace the manual trigger with the Schedule (Cron) trigger to run collection on an interval.
Yes. Because responses are normalized JSON, you can map fields directly into n8n's Google Sheets, database, or Slack nodes.
Back off on 429 responses with a Wait node or retry settings, and keep result counts and concurrency bounded.
Check the API docs and test the endpoint in the Playground, then copy the parameters into the HTTP Request node's JSON body.
Import the workflow template, add your API key, and point the HTTP Request node at the endpoint you need.