Crawlora
ProductPlatformsUse CasesDocsPricingCompareContact
Sign inTry Playground Console
Crawlora

Structured public web data APIs for search, maps, geocoding, streaming, travel, real estate, marketplaces, apps, social, audio, crypto, finance, and AI workflows with managed execution and credit-based usage.

Product

Web Scraping APIFeaturesPlatformsTravel APIsReal Estate APIsPricing

Platforms

Google SearchGoogle MapsGoogle TrendsAmazonZillowTripAdvisorShopifyAll platforms

Developers

DocsGetting StartedAPI ExamplesPlaygroundSDKsChangelogBlogGitHub

Use cases

SERP MonitoringGoogle Maps LeadsProperty Market IntelligenceAmazon Product MonitoringCrypto Market ResearchAI Agent Web DataAll use cases

Legal

ContactTermsPrivacy
Product
Web Scraping APIFeaturesPlatformsTravel APIsReal Estate APIsPricing
Platforms
Google SearchGoogle MapsGoogle TrendsAmazonZillowTripAdvisorShopifyAll platforms
Developers
DocsGetting StartedAPI ExamplesPlaygroundSDKsChangelogBlogGitHub
Use cases
SERP MonitoringGoogle Maps LeadsProperty Market IntelligenceAmazon Product MonitoringCrypto Market ResearchAI Agent Web DataAll use cases
Legal
ContactTermsPrivacy
© 2026 Crawlora. All rights reserved.·Built by Tony Wang
System statusCrawlora API status
  1. Home
  2. /Integrations
  3. /Make Integration Guide

Developer guides

Make Integration Guide

Call Crawlora's structured web data APIs from Make's HTTP module — no custom code — and automate search, maps, e-commerce, and finance scenarios.

HTTP moduleNo-code automationScheduled scenariosWebhooks
Browse APIs Try PlaygroundExplore Integrations

Verified HTTP pattern

POST /google/search

Normalized JSON

Request

POST https://api.crawlora.net/api/v1/google/search
x-api-key: $CRAWLORA_API_KEY
Content-Type: application/json

{
  "country": "us",
  "keyword": "best CRM software",
  "language": "en",
  "limit": 10,
  "page": 1
}

Base URL

https://api.crawlora.net/api/v1

Auth header

x-api-key

Example endpoint

POST /google/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

Why use Crawlora with Make?

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

Set up the HTTP module

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.

02

Add your API key as a header

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

Send a JSON body for POST endpoints

Set the body type to JSON (Raw) and provide the request parameters, such as query and limit.

Developer workflow

Map and route results

  • Parse the JSON response with Make's built-in JSON handling.
  • Iterate arrays to create one bundle per record.
  • Route to Google Sheets, a database, Slack, or another module.

Developer workflow

Example request

The HTTP module sends this request; map the fields into downstream modules.

Equivalent request · bash

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

Use cases

  • Local lead lists into Google Sheets.
  • Price and availability monitoring into a database.
  • Scheduled SERP snapshots for rank tracking.
  • Slack alerts on new Product Hunt launches.
  • Review and reputation monitoring digests.

Developer workflow

Production tips

  • Keep the API key in a Make connection or data store, not in the module.
  • Bound result counts with the endpoint's limit parameter.
  • Add error handling and a delay/retry on 429 responses.
  • Schedule scenarios on an interval for recurring collection.
  • Avoid sending unnecessary personal data into downstream modules.

Responsible public web data workflows

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 terms

Developer workflow

Related developer links

Use these pages to move between endpoint discovery, examples, pricing, and responsible-use guidance.

n8n

LangChain

MCP

Browse APIs

Google Maps

Amazon

Developer workflow

FAQ

Common questions for this Crawlora developer integration path.

Does Crawlora have a Make app?

Not a dedicated app. Use Make's built-in HTTP module to call any Crawlora endpoint and parse the JSON response.

How do I authenticate from Make?

Send your Crawlora API key as an x-api-key header, stored in a Make connection or data store rather than hardcoded.

Can I schedule scenarios?

Yes. Make scenarios can run on a schedule, so you can collect data on an interval.

Can I send results to Sheets, a database, or Slack?

Yes. Because responses are normalized JSON, you can map fields directly into Make's Google Sheets, database, or Slack modules.

How should I handle rate limits?

Add error handling and a delay or retry on 429 responses, and keep result counts bounded.

Where do I find the request parameters?

Check the API docs and test the endpoint in the Playground, then copy the parameters into the HTTP module's JSON body.

Automate a Crawlora endpoint in Make

Add an HTTP module, set your API key, and point it at the endpoint you need.

Browse APIsTry Playground