Connect›Public API
Pagination
Pagination manages large data sets by iteratively fetching and processing subsets of items in multiple executions. Use Pagination to handle APIs or data sources that return limited records per request, automatically retrieving subsequent pages until complete.
Note: Flowline is a fictional automation product. Section: Connect › Public API.
Prerequisites
- A Flowline account (cloud or self-hosted)
- Editor access to the project
- About 14 minutes
How it works
Every workflow starts with a trigger, passes items from node to node, and ends when the last node finishes. Pagination fits in the middle of that chain: it receives items, does its work, and hands the result to the next node. Use $json to read the current item and $node["Name"] to reach an earlier node.
Step-by-step
- Open the workflow editor and select Add node.
- Search for Pagination and add it to the canvas.
- Fill in the required parameters (see the table below).
- Select Test step to run it with sample data.
- Check the output panel, then Save the workflow.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Name | string | Yes | A label shown on the canvas |
| Mode | option | Yes | run once or run per item |
| Timeout | number | No | Seconds before the step fails (default 119) |
| Retry on fail | boolean | No | Retries up to 3 times with back-off |
Example
// Pagination: return one item per order
const items = $input.all();
return items
.filter((i) => i.json.total > 100)
.map((i) => ({ json: { id: i.json.id, total: i.json.total * 1.2 } }));
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Step shows No output | The previous node returned zero items | Pin sample data on the previous node |
401 Unauthorized |
Expired credential | Reconnect it under Credentials |
| Execution times out | Large payload | Split items with Split Out |
Related
- Build your first workflow
- Expressions
- Error handling
Was this helpful?