Actions8
- Page Actions
- Recipe Actions
- URL Actions
Recipe → Get Results by ID
AI-generatedSummary
Fetch the results of a Simplescraper run by its results_id via GET /v1/results/{resultsId}, returning one n8n item per scraped row with optional pagination.
Inputs
- Results ID (required) — The results_id of the run to fetch. Comes from an async Run a Recipe call or the New Results trigger. Inserted into the URL path.
- Limit — Max number of results to return (minimum 1, default 50). Sent as the
limitquery parameter. - Cursor — Pagination cursor from a previous request. Sent as
cursoronly when non-empty. - Request Options — Node-level HTTP settings: batching (items per batch, interval), ignore SSL issues, proxy, and timeout (default 10000 ms).
Output shape
One item per scraped row in the response data array. Each item's JSON merges the run-level fields (everything in the response except data and screenshots) with the row's fields. If data is empty, a single item containing only the run-level fields is returned.
If the run has screenshots, each row gets a
screenshotfield matched byurl_uid(null if there is no match). Pagination is manual: the node doesn't auto-page, so pass the cursor returned in a previous response (it appears in the run-level fields, if the API returns one) to get further results. Requires Simplescraper API credentials.
Examples
Example 1: Retrieve data after an async recipe run finishes
Resource: Recipe, Operation: Get Results by ID, Results ID: {{ $json.results_id }} from the earlier Run node, Limit: 50.
Example 2: Process a New Results trigger event
Set Results ID to the results_id emitted by the Simplescraper trigger and raise Limit to 200 to get more rows per call.
Example 3: Page through a large result set
Set Results ID, Limit 100, and set Cursor to the cursor value from the previous response. Repeat until no cursor is returned.