Start free
ActionCopperUpdated June 2026

How do I list Copper leads?

Short answer: You can list leads in Copper by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Copper List Leads action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Leads in Copper — start free All 6 Copper actions
List Leads in Copper — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Page Size
page_size
numberOptionalPage 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.

Triggered by

Apps that pair well as the trigger for List Leads.

Any of these apps can fire this action as part of a workflow.

Gmail → Copper
1 Gmail triggers
Slack → Copper
13 Slack triggers
Google Sheets → Copper
2 Google Sheets triggers
HubSpot → Copper
18 HubSpot triggers
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. TinyCommand handles Copper's rate limits automatically so you don't have to throttle manually.
More actions

Other Copper actions.

Action
Create Opportunity
Creates a sales opportunity tied to a person and/or company with value, pipeline, stage, owner. For "form said they want to buy → auto-create opportunity for the AE" workflows.
Action
Create Person
Inserts a new person with email, name, phone, optional company link, custom fields. Copper dedupes on primary email; existing emails error rather than upserting (wrap in search-first if uncertain).
Action
Get Person
Returns a person by ID or email with all standard and custom fields plus related company and recent activities. The standard lookup before update workflows.
Action
List People
Paginated people with filters by company, owner, custom-field values. For warehouse syncs use the modified-since filter to incrementally pull only touched records.
Action
Update Person
Partial update — only passed fields change. For "Clearbit enrichment ran → write firmographic data back to Copper" or "support ticket categorized → add tag to person" augmentation workflows.
List Leads in Copper — start free