Update 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
Full Name name	string	Optional	Full Name
Email email	string	Optional	The email address. Used as the recipient or identifier depending on context.
Phone phone_number	string	Optional	Phone number in E.164 format (with country code, no spaces).
Company company_name	string	Optional	Company

Sample request

{
  "person_id": "e.g. 123",
  "name": "{{trigger.name}}",
  "email": "e.g. user@example.com",
  "phone_number": "e.g. +14155551234",
  "company_name": "{{trigger.company_name}}"
}

Returns

{
  "id": 123,
  "name": "John Doe"
}

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

FAQ

Questions about Update Person.

What does the Update Person action do in Copper?

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.

What inputs does Update 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 Update Person support batch operations?

Yes. Run Update 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