List People: Copper action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Page Size page_size	string	Optional	Page Size. e.g. "20"
Page Number page_number	string	Optional	Page Number. e.g. "1"

Sample request

{
  "page_size": "20",
  "page_number": "1"
}

Returns

[
  {
    "id": 123,
    "name": "John Doe",
    "emails": [
      {
        "email": "john@example.com"
      }
    ]
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List People.

What does the List People action do in Copper?

Paginated people with filters by company, owner, custom-field values. For warehouse syncs use the modified-since filter to incrementally pull only touched records.

What inputs does List People require?

List People has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Copper returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List People support batch operations?

Yes. Run List People inside a Loop node to process arrays. Tiny Command handles Copper's rate limits automatically so you don't have to throttle manually.

More actions