Get Person: 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
Person ID person_id	string	Required	Person ID. Example: 123

Sample request

{
  "person_id": "e.g. 123"
}

Returns

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

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

FAQ

Questions about Get Person.

What does the Get Person action do in Copper?

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.

What inputs does Get Person require?

Required: Person ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Person support batch operations?

Yes. Run Get Person 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