Configure Squid Chain
Squid
Configure Squid Chain
Chain two crawlers together so results from one automatically feed into another
POST
Configure Squid Chain
Crawler chaining lets you connect two squids so that when a run on the source squid completes, its results are automatically extracted and queued as tasks on a target squid, triggering a new run downstream.
Example use case: Run a Google Maps Leads scrape to collect place URLs, then automatically pass those URLs into a Google Maps Reviews scrape — without any manual intervention.
Chains are limited to a maximum depth of 3 squids. A squid can only have one outgoing chain at a time.
How it works
- You configure a chain on a source squid, specifying the target crawler and a
field_map - When a run on the source squid completes with a status of
DONE, the scheduler extracts the mapped fields from its results - Those values are queued as tasks on the target squid (auto-created on first trigger if it doesn’t exist yet)
- If
autostartistrue, a new run starts immediately on the target squid
Path Parameters
Hash ID of the source squid. Example:
"e86b29c032024b66aff529e1d43c2bd7"Headers
Your API authentication token. Value:
Token YOUR_API_KEYMust be application/json. Value:
application/jsonRequest Body
Hash ID of the target crawler. Use
GET /v1/crawlers to find it. Example: "9a3f1c8b2e7d4a56f0e1b2c3d4e5f678"Maps a result field from the source crawler to an input parameter on the target crawler. Example:
{"url": "url"} — passes the url field from source results as the url input on the target.If
true, the downstream run starts automatically when tasks are queued. If false, tasks are queued and the run is created as paused for manual review. Defaults to true.Custom name for the auto-created target squid. If omitted, defaults to
"{Crawler Name} (N) (chained)".Concurrency to apply to the auto-created target squid. Defaults to
1.Response Fields
Unique chain config identifier.
Details of the target crawler.
The auto-created target squid.
null until the first chain trigger fires.The configured field mapping.
Whether the chain is currently active.
Whether downstream runs start automatically.
Configured name for the target squid.
Configured concurrency for the target squid.
ISO 8601 timestamp of when the chain was configured.
Code Examples
Response
201
400
409
422