CRM
Copper Integration
Create people in Copper CRM automatically from ad leads -- with email, phone, company, and custom fields mapped to keep your Google Workspace CRM up to date.
Create people in Copper CRM automatically from ad leads -- with email, phone, company, and custom fields mapped to keep your Google Workspace CRM up to date.
Connect Copper with 4 lead sources
Copper organises CRM data around four core record types -- Person (an individual contact), Lead (an unqualified inquiry), Opportunity (a deal in your Pipeline), and Activity (a logged interaction). LeadSync writes incoming Facebook, Google, LinkedIn, and TikTok leads as Person records via the Copper REST API at api.copper.com/developer_api/v1/people, which is the right model when the lead represents a real human you want to convert into a deal downstream.
Setup takes two values from your Copper account: the API Key (Settings › Integrations › API Keys) and the email address the API key was generated under -- both are required headers on every Copper request (X-PW-AccessToken and X-PW-UserEmail). Paste both into LeadSync as a semicolon-delimited string and the connection is live.
Copper's Person record stores email and phone as arrays of structured objects, not single strings -- each entry has a value and a category ("work", "home", "mobile", "other"). LeadSync defaults the email category to work and the phone category to work, which is what most CRM workflows assume for an inbound paid-social lead. The structured shape means filters like "all People with a work phone number" continue to work.
Beyond email and phone, the standard mapping screen exposes name, company, title, website, address, and details (the description field). Map any lead form question to whichever standard field your sales team uses for that data point, and the value flows through on every new lead.
Copper supports custom field definitions at the account level, with each field flagged for which record types it's available on (Person, Lead, Opportunity, Company, Project). LeadSync calls GET /custom_field_definitions when you open the field mapping screen and filters to fields with person in their available_on array -- so every Person-applicable custom field appears in the dropdown alongside the standard fields.
Map a lead form question to a custom field once and every lead from that connection populates the field. Custom fields work in Copper Workflows, custom views, and the Pipeline filter system, so once mapped they're immediately useful for routing, segmentation, and reporting -- not just stored data.
Set up your Copper integration in under 60 seconds. Free 14-day trial, no credit card required.
Start Your Free Trial