Copper Integration
Copper API key connection, Person/Company sync, meeting notes, tasks, and call logging.
Copper Connection
Copper uses API key authentication. You will need your Copper API key and the email address associated with your Copper account.
- Navigate to Settings → Integrations
- Find "Copper" in the integrations list
- Click Connect
- Enter your Copper API key
- Enter the email address associated with your Copper account
- Click Authenticate to verify your credentials
- A setup wizard will open — walk through the steps to configure sync settings and meeting filters
- The integration status will show as "Connected"
Note: You can find your API key in Copper under Settings → Integrations → API Keys. The email address must match the Copper user account associated with the API key. This account determines the permissions for reading and writing data — make sure it has access to People, Activities, and Tasks.
Setup Wizard
After authenticating, a guided setup wizard walks you through six steps:
- Authentication — Confirms your API key connection is active
- Test Record — EffiClose creates a test Person, Note, and Task in your Copper account to verify that permissions are configured correctly. These test records are cleaned up automatically.
- Sync Settings — Choose which objects to sync and how fields are mapped
- Meeting Filters — Configure which meetings should trigger CRM updates
- Visibility — Control who on your team can see the integration and its synced data
- Review & Activate — Review your configuration and activate the integration
Important: If the test record step fails, check that your Copper API key has create permissions for People, Activities, and Tasks. You may need to generate a new API key with the correct access level.
Data Synchronization
Data syncs between the platform and Copper automatically every 2 hours.
Imported Objects:
We import the following Copper objects, automatically resolving relationships between them:
- Person: Syncs persons matched by meeting participant email addresses, including name, email, phone number, and job title
- Company: Imports companies associated with your synced persons, including company name and address
Note: Persons are imported based on meeting participant emails, so only persons relevant to your meetings are synced — not your entire Copper database.
What You Can Do After Setup
Once connected, EffiClose automatically enriches your Copper CRM with meeting intelligence:
- Person matching: Meeting participants are automatically matched to existing Copper Persons by email. If no match is found, a new Person can be created with name, email, phone number, company, and job title.
- Meeting notes: After each meeting, a summary note is created as an Activity and attached to the relevant Person. The note includes key discussion points, action items, and a link to the full transcript.
- Action items as tasks: Action items identified during meetings are created as Copper Tasks with due dates, linked to the relevant Person.
- Call logging: Meetings are logged as Activities (Phone Call type) in Copper with title, summary, and recording link, associated to participant Persons.
- Re-sync past meetings: You can re-sync previously processed meetings to update Copper with the latest data.
Note: Copper uses Persons instead of Contacts and does not have separate Lead, Deal, or Opportunity objects. All meeting participants are matched or created as Person records.
Troubleshooting
Connection issues:
- Try disconnecting and reconnecting the integration
- Verify that your API key is still valid and has not been revoked in Copper
- Ensure the email address matches the Copper user account associated with the API key
- If the API key was regenerated in Copper, you will need to reconnect with the new key
Sync errors:
- Disconnect and reconnect the integration
- Verify the API key account has proper permissions for the synced objects
- Review error messages in the integration status page
Permission issues:
- Ensure the Copper account has access to People, Activities, and Tasks
- Check Copper user role and permission settings
- If the setup wizard test record step fails, the API key may lack create permissions