List Leads: 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	number	Optional	Page Size

Sample request

{
  "page_size": "{{trigger.page_size}}"
}

Returns

[
  {
    "id": 123,
    "name": "John Doe",
    "email": {
      "email": "john@example.com"
    },
    "status": "New",
    "company_name": "Acme Inc"
  }
]

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

FAQ

Questions about List Leads.

What does the List Leads action do in Copper?

Paginated leads with filters by status, source, owner, modified date. For sync workflows to a warehouse or for "leads stale 30+ days, send re-engagement" lifecycle automation.

What inputs does List Leads require?

List Leads 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 Leads support batch operations?

Yes. Run List Leads 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