Start free
ActionCopperUpdated June 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.

Use this actionAll 6 Copper actions
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Person ID
person_id
stringRequiredPerson ID. Example: 123
Full Name
name
stringOptionalFull Name
Email
email
stringOptionalThe email address. Used as the recipient or identifier depending on context.
Phone
phone_number
stringOptionalPhone number in E.164 format (with country code, no spaces).
Company
company_name
stringOptionalCompany
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.

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 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. 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 Leads
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.
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.