Copper connector
Back to the connector overview, authentication methods, and actions.
25 Aug 2026
breaking-change bug-fix docsRemoved schema fields that Copper’s API rejects with 422 — socials.category “klout”, create_activity type.category “system”, related_resource on update_project/task, company_id/company_name on update_person, status_ids on list_projects, priority_ids on list_opportunities. Added missing custom_fields item properties (custom_field_definition_id required, value) on create_task/update_task and made custom_fields[].value polymorphic (string/number/boolean/number[]) across leads/people/companies/opportunities/projects/tasks to match Copper’s data_type-dependent value shape. Documented custom_fields silent-drop and list_people.name exact-match behavior; enhanced relate_record_to_entity description as the sole cross-record link tool. Trimmed connection testActions to fetch_api_user.