Query More
salesforce.query_more
ActionCRM & salesconnection required
Calls the Salesforce REST API at the connection's instance URL.
Fetch the next page of a SOQL query from its nextRecordsUrl.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Salesforce
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- login_url, api_version
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
next_records_url The next_records_url from the previous page, e.g. /services/data/v59.0/query/01g5e00000abcDEF-2000. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
records The records in this page. | array | — |
count How many records this page holds. | number | — |
total totalSize — how many records the query matches in all. | number | — |
done False when more pages remain. | boolean | — |
next_records_url Salesforce's nextRecordsUrl: feed it to salesforce.query_more. Null on the last page. | string | — |
{
"count": 0,
"done": false,
"next_records_url": "",
"records": [],
"total": 0
}Notes
- nextRecordsUrl is a full API path, not an opaque cursor token — pass it through unchanged.
Templates that use Salesforce
Solutions with Salesforce
See Query More run in a workflow.
In a technical demo we add the Salesforce connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.