- Integrations
- /
- Copper
- /
- Actions
- /
- Create Person
ActionCopperUpdated May 2026
How do I add a person to Copper?
Short answer: Drop the "Copper → Create Person" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Full Name name | string | Required | Full Name. Example: John Doe |
Email email | string | Optional | Email. e.g. "john@example.com" |
Phone phone_number | string | Optional | Phone. e.g. "+15551234567" |
Company company_name | string | Optional | Company. Example: Acme Inc |
Sample request
{"name": "e.g. John Doe","email": "john@example.com","phone_number": "+15551234567","company_name": "e.g. Acme Inc"}
Returns
{"id": 123,"name": "John Doe","emails": [{"email": "john@example.com"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Create Person.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Person.
What does the Create Person action do in Copper?
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).
What inputs does Create Person require?
Required: Full Name. 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 Create Person support batch operations?
Yes. Run Create 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
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.
ActionGet 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.
ActionList 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.
ActionList 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.
ActionUpdate 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.
Send create person from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.