ActionCopperUpdated September 2026

How do I update a Copper person?

Short answer: You can update person in Copper by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Copper Update Person action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Person in Copper — start free All 6 Copper actions

Update Person 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.

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.

Triggered by

Apps that pair well as the trigger for Update Person.

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

Google Sheets → Copper

2 Google Sheets triggers

HubSpot → Copper

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Copper returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Person support batch operations?

Run Update Person inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Copper's rate limits.

More actions