No-code
Web scraping in Make with Piloterr
Add an HTTP module to any Make scenario and call Piloterr APIs. Structured JSON flows into Google Sheets, Slack, Airtable, and 1,500+ apps, no SDK install.
- Native HTTP module with x-api-key header auth
- Use soft_fail=true for resilient error handling
- Visual scenario builder for complex pipelines
- Same REST API as Python and Node.js
At a glance
HTTP
REST module
soft_fail
error resilience
400+
API endpoints
JSON
structured output
Why connect Make
HTTP module integration
Configure URL, method, headers, and JSON body in Make's HTTP module. Authenticate with x-api-key in the header.
soft_fail for Make scenarios
Append soft_fail=true to API calls so Make continues when an endpoint returns 404 or 500, handle errors in downstream modules.
Visual orchestration
Branch, filter, and iterate over JSON arrays without writing code.
Anti-bot included
Make's HTTP module alone can't bypass WAFs. Piloterr returns clean JSON so your scenario never stops at a challenge page.
Every Piloterr API inside Make
One HTTP connection, all scraping capabilities.
Scraper APIs
400+ endpoints for e-commerce, SERP, social, and B2B data.
Iterator modules
Split JSON arrays and process each item in parallel branches.
Error handling
Route soft failures to notification modules instead of stopping the scenario.
Scheduling
Run scenarios on intervals for monitoring and competitive intelligence.
Why hand-rolled scrapers fail in Make
| Approach | DIY | Piloterr |
|---|---|---|
| HTTP module alone | Blocked at TLS or WAF | Managed bypass |
| Headless browser add-on | Fingerprint leaks | Stealth Chrome server-side |
| Custom code step | Breaks on vendor updates | Stable JSON schemas |
| Error handling | Scenario stops on 404 | soft_fail keeps flows running |
Scrape from Make in four steps
Step 1
Create a Make account
Sign up at make.com and create a new scenario.
Step 2
Add an HTTP module
Choose Make a request. Set method to POST or GET and paste your Piloterr endpoint URL.
Step 3
Configure authentication
Add header x-api-key with your API key. Set Content-Type to application/json for POST bodies.
Step 4
Map JSON to downstream apps
Connect Google Sheets, Slack, or Airtable modules and map response fields.
Workflow recipes
Daily scrape → AI summary → Slack
Schedule → Piloterr scrape → AI module → Slack post.
Sheet row → scrape → append row
Google Sheets watch rows → HTTP scrape → write JSON back.
Monitor competitor → email on change
Hourly scrape → compare hash → send email when content changes.
Webhook → scrape → CRM update
HTTP webhook receives a URL, Piloterr scrape runs, and CRM deal fields refresh automatically.
When to pick Make vs SDK
Scenario
Visual pipelines with SaaS triggers
Recommendation: Make
Scenario
High-volume crawling loops
Recommendation: Python SDK
Scenario
Make stops on HTTP errors
Recommendation: Use soft_fail=true
Scenario
Self-hosted automation
Recommendation: n8n
HTTP request your Make module sends
Configure your Make HTTP module to match this request.
curl --location --request POST 'https://api.piloterr.com/v2/google/news?soft_fail=true' \
--header 'Content-Type: application/json' \
--header 'x-api-key: YOUR_API_KEY' \
--data '{"query": "stocks", "location": "Paris, FR", "page": 1}'
Zapier
n8n
Google Apps Script
LangChainTransparent credit pricing
Pay only for successful requests. Start with +500 credits, then scale with plans from $49/mo.
Premium
$49/mo
18,000 credits
Premium+
$99/mo
40,000 credits
Startup
$249/mo
110,000 credits