List List Members
hubspot.list_list_members
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
Page through the record ids in a list with GET /crm/v3/lists/{listId}/memberships, ordered by record id.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- HubSpot
- Secret shape
- the HubSpot private-app token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 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 |
|---|---|---|---|---|---|
list_id The HubSpot record id of the list whose members to page through. | string | Yes | — | — | 101 |
limit How many memberships to return per page; the Lists API caps a page at 250. | number | No | 100 | 1–250 | — |
after Paging cursor taken from the previous page's `after` output; blank starts at the first page. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"limit": 100,
"list_id": "101"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
results The memberships on this page, each `{recordId, membershipTimestamp}` — record ids, not the records; read those with hubspot.batch_read_contacts or a get node. | array | — |
count How many memberships this page carried. | number | — |
after Cursor to pass as the next call's `after`; empty when this was the last page. | string | — |
{
"after": "",
"count": 0,
"results": []
}See List List Members run in a workflow.
In a technical demo we add the HubSpot connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.