Add List Members

hubspot.add_list_members
ActionCRM & salesconnection required

Calls the HubSpot API with the connection's credentials.

Add records to a manual list with PUT /crm/v3/lists/{listId}/memberships/add. Records already in the list are left alone, so the call is safe to repeat.

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

2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
list_id
The HubSpot record id of the list to add to.
stringYes——101
record_ids
Record ids to add, as a JSON array of strings.
arrayYes—array of string["101","202"]

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "list_id": "101",
  "record_ids": [
    "101",
    "202"
  ]
}

Output

One shape.

result

FieldTypeExample
ok
True once HubSpot accepted the change.
boolean—
recordsIdsAdded
The record ids HubSpot actually added — spelled with that extra "s" because that is the field name HubSpot returns.
array—
recordIdsRemoved
The record ids HubSpot actually removed.
array—
recordIdsMissing
Ids HubSpot could not find, so neither added nor removed. A call that changed nothing still succeeds; this is where it says so.
array—
count
How many ids were sent.
number—
{
  "count": 0,
  "ok": false,
  "recordIdsMissing": [],
  "recordIdsRemoved": [],
  "recordsIdsAdded": []
}

Notes

  • Only a MANUAL list takes members this way; a dynamic (filter-driven) list computes its own membership and refuses the call.

See Add 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.