Overview
Copper is a CRM built for Google Workspace users. Teams use Copper for pipeline management, contact tracking, and sales automation.
Persona’s Copper integration lets a Workflow create, retrieve, update, and list people, which are the contact records in Copper. At this time, the integration supports people records only.
For example, a Workflow can create or update a contact after a Persona verification. A Workflow can also look up an existing person before it creates one, to prevent duplicates. You can record a verification outcome in the person’s Details, Tags, or a custom field.
Integration features
- Create person: Add a person to Copper.
- Retrieve person: Get one person by Person ID.
- Update person: Change a person by Person ID.
- List people: Search for people with optional filters.
Prerequisites
Before you configure the integration, you need:
- A Copper account.
- A Copper user who has permission to generate API keys in Copper.
Set up Copper credentials
- In the Copper web app, go to Settings > API Keys.
- Click Generate API Key and enter a label for the key.
- Copy the API key.
- In the Persona Dashboard, go to Integrations > Marketplace and select Copper.
- Click Add Credential and enter a nickname for the credential.
- In Access Token, paste the Copper API key.
- In User Email, enter the email address of the Copper user who generated the API key.
- Save the credential.
Both fields are required. The integration automatically sends the application header that Copper requires. The integration uses the API key, not Copper’s OAuth.
Actions run with the permissions of the Copper user who generated the API key.
Use Copper in a Workflow
- Create a Workflow, or open the Workflow you want to update.
- Add an Action step and select Integrations.
- Select Copper, choose the saved credential, and select an action.
- Map Persona data to the action’s input fields.
- Save and publish the Workflow.
Copper actions
- Create person: Creates a person. The fields are Name, Prefix, First Name, Middle Name, Last Name, Suffix, Address (street, city, state, postal code, and country), Assignee ID, Company ID, Company Name, Contact Type ID, Details, Emails (email and category), Phone Numbers, Socials, Tags, Title, Websites, and Custom Fields (custom field definition ID and value).
- Retrieve person: Returns one person. Requires Person ID.
- Update person: Changes a person. Requires Person ID. Uses the same fields as Create person.
- List people: Returns people. Optional filters: IDs, Name, Phone Number, Emails, Contact Type IDs, Assignee IDs, Company IDs, Opportunity IDs, City, State, Postal Code, Country, Tags, Socials, Followed, Age, minimum and maximum created date, minimum and maximum interaction date, and minimum and maximum interaction count. You can also set Page Number, Page Size, Sort By, and Sort Direction.
Emails, Phone Numbers, and Tags are list fields. Before you update a list field, check how Copper applies the values that you send, so that you keep the values you need.
FAQs
Why is my Copper credential failing?
Make sure that User Email is the email address of the Copper user who generated the API key. Also make sure that both Access Token and User Email are saved. A credential that was saved before both fields were collected can be missing the User Email. If so, edit the credential and add the User Email.
How do I prevent duplicate people?
Before you create a person, use List people with a filter such as Emails to look for an existing person. If the person exists, use Update person instead.
Can I manage companies or opportunities?
No. At this time, the integration supports people records only.
Plans Explained
Copper Integration by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Copper Integration | Not Available | Not Available | Limited | Available |