No-code recipes
Call the API from n8n, Make or Zapier with each tool's generic HTTP step. Native integrations are on the roadmap.
Before you start
You need an API key from API keys. Every recipe sends the same request:
| Setting | Value |
|---|---|
| Method | POST |
| URL | https://livewebdata.com/api/v1/contents |
| Header | Authorization: Bearer YOUR_KEY |
| Body (JSON) | {"urls": ["https://example.com/article"], "countryCode": "us"} |
The response is JSON: page content in results[0].markdown, the outcome in statuses[0].status and statuses[0].error.tag.
n8n
Native integration coming soon. Use the built-in HTTP Request node for now.
| Field (HTTP Request node) | Value |
|---|---|
| Method | POST |
| URL | https://livewebdata.com/api/v1/contents |
| Authentication | Generic Credential Type → Bearer Auth (token = your key) — or Header Auth with Name Authorization, Value Bearer YOUR_KEY |
| Send Body | on |
| Body Content Type | JSON |
| Specify Body | Using JSON → {"urls": ["{{ $json.url }}"]} |
| Options → Response → Response Format | JSON (default: autodetect) |
URL lists: feed one item per URL into the node. Use the node's Options → Batching (Items per Batch = your rate limit, Batch Interval (ms) = 1000) — or a Loop Over Items node plus a Wait node (1 second) to stay within your rate limit.
Make
Native integration coming soon. Use the HTTP app's Make a request module for now.
| Field (HTTP → Make a request) | Value |
|---|---|
| Authentication type | API key (stores the key in a keychain) — or No authentication plus the header below |
| URL | https://livewebdata.com/api/v1/contents |
| Method | POST |
| Headers | Authorization = Bearer YOUR_KEY |
| Body content type | application/JSON |
| Body input method | JSON string |
| Body content | {"urls": ["https://example.com/article"]} |
| Parse response | Yes |
URL lists: use an Iterator over your URLs before the HTTP module and set the scenario's scheduling so the number of operations per second stays within your rate limit.
Zapier
Native integration coming soon. Use Webhooks by Zapier → Custom Request for now (not available on the Free plan).
| Field (Custom Request) | Value |
|---|---|
| Method | POST |
| URL | https://livewebdata.com/api/v1/contents |
| Data Pass-Through? | False |
| Data | {"urls": ["https://example.com/article"]} |
| Headers | Authorization = Bearer YOUR_KEY, Content-Type = application/json |
The JSON response is available as fields in later steps.
Tips
- Failed pages return HTTP 200 with
statuses[0].status = "error"— add a filter/router on that field. - Keep the key in the tool's credential store, not in plain step fields, wherever possible.