01
Add a Webhooks by Zapier action
Choose the 'Custom Request' event so you can set the method, URL, headers, and body for a Crawlora endpoint.
Developer guides
Call Crawlora's structured web data APIs from Zapier's Webhooks by Zapier action — no custom code — and automate search, maps, e-commerce, and finance Zaps.
Verified HTTP pattern
POST /google/search
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
Zapier is a no-code automation platform that connects thousands of apps. Crawlora does not ship a dedicated Zapier app, but the built-in Webhooks by Zapier action calls any Crawlora endpoint directly. Webhooks by Zapier requires a paid Zapier plan.
Developer workflow
Zapier connects services without code. Crawlora returns normalized JSON from supported public platforms, so you can fetch data with Webhooks by Zapier and route it to Google Sheets, Airtable, a database, or Slack without maintaining parsers. The same agent-native structured data also backs Crawlora's hosted MCP tools when you move from Zaps to agents.
Developer workflow
01
Choose the 'Custom Request' event so you can set the method, URL, headers, and body for a Crawlora endpoint.
02
Use POST and a Crawlora endpoint URL, for example https://api.crawlora.net/api/v1/google/map/search.
03
Add an x-api-key header with your Crawlora API key. Store it in a Zapier Storage or account field rather than pasting it into every Zap step where possible.
04
Set the Data Pass-Through to false and provide JSON data such as query and limit, with the Content-Type header set to application/json.
Developer workflow
Developer workflow
Webhooks by Zapier sends this request; map the response fields into downstream steps.
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.
Not a dedicated app. Use the built-in Webhooks by Zapier action with the Custom Request event to call any Crawlora endpoint.
Webhooks by Zapier requires a paid Zapier plan. Confirm your plan supports webhook actions before building the Zap.
Send your Crawlora API key as an x-api-key header in the Webhooks by Zapier action. Keep it in Zapier Storage or a secure field rather than pasting it everywhere.
Yes. Use Zapier's Schedule trigger to run collection on an interval, then call Crawlora with Webhooks by Zapier.
Yes. Because responses are normalized JSON, you can map fields directly into Zapier's Google Sheets, Airtable, database, or Slack steps.
Add a Delay or filter step, keep result counts bounded, and avoid aggressive retry loops on 429 responses.
Check the API docs and test the endpoint in the Playground, then copy the parameters into the Webhooks by Zapier JSON body.
Add a Webhooks by Zapier action, set your API key header, and point it at the endpoint you need.