01
Add an HTTP module
Use 'Make a request' and set the method and URL to a Crawlora endpoint, for example POST https://api.crawlora.net/api/v1/google/map/search.
Developer guides
Call Crawlora's structured web data APIs from Make's HTTP module — no custom code — and automate search, maps, e-commerce, and finance scenarios.
Verified HTTP pattern
POST /google/map/search
Request
POST https://api.crawlora.net/api/v1/google/map/search
x-api-key: $CRAWLORA_API_KEY
Content-Type: application/json
{
"keyword": "coffee shops in Austin, TX",
"language": "en",
"country": "us"
}Base URL
https://api.crawlora.net/api/v1
Auth header
x-api-key
Example endpoint
POST /google/map/search
Make (formerly Integromat) is a no-code automation platform. Crawlora does not ship a dedicated Make app, but Make's built-in HTTP module calls any Crawlora endpoint directly.
Developer workflow
Make connects services without code. Crawlora returns normalized JSON from supported public platforms, so you can fetch data with the HTTP module and route it to spreadsheets, databases, or Slack without maintaining parsers. The same agent-native structured data also backs Crawlora's hosted MCP tools when you move from scenarios to agents.
Developer workflow
01
Use 'Make a request' and 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 a Make connection or a data store rather than hardcoding it in the module.
03
Set the body type to JSON (Raw). For Google Maps search, send keyword, language, and country at the top level — do not nest them under another object.
Developer workflow
Google Maps search returns its records in the top-level `data` array. Put Make's Iterator after the HTTP module and map `data` as its source. The Iterator emits one bundle per place; add a Router after it when different records need different downstream paths.
Developer workflow
The HTTP module sends this request; map the fields into downstream modules.
Check the exact POST body and response schema used in this guide.
Open guideRun the same endpoint before copying it into Make.
Open guidecurl -X POST https://api.crawlora.net/api/v1/google/map/search \
-H "x-api-key: $CRAWLORA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keyword": "coffee shops in Austin, TX", "language": "en", "country": "us"}'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.
Not a dedicated app. Use Make's built-in HTTP module to call any Crawlora endpoint and parse the JSON response.
Send your Crawlora API key as an x-api-key header, stored in a Make connection or data store rather than hardcoded.
Yes. Make scenarios can run on a schedule, so you can collect data on an interval.
Yes. Because responses are normalized JSON, you can map fields directly into Make's Google Sheets, database, or Slack modules.
Enable incomplete executions so Make can retry transient connection and rate-limit errors. Use a Retry error handler when a failed downstream module needs recovery, and send invalid endpoint parameters to a separate review path instead of retrying the same request.
For the Google Maps search example, map the response's top-level `data` array into Make's Iterator. Each place becomes its own bundle, which a Router can filter into different downstream modules.
Check the API docs and test the endpoint in the Playground, then copy the parameters into the HTTP module's JSON body.
Add an HTTP module, set your API key, and point it at the endpoint you need.