Copper
CRM & salesAPI keyConnection test available
People, companies, leads, opportunities, projects and tasks in Copper CRM.
OCNORA ships 47 typed Copper operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.copper.com/developer_api/v1 through the HTTP node with the same credential.
Before you connect Copper
- Authentication
- API key
- Credential
- the Copper API keythe API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The connection's user_email is required — Copper rejects every call without the X-PW-UserEmail header. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to an https URL: Copper only accepts https:// notification endpoints.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Copper
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Read and search 24
Delete and cancel 6
Other operations 5
A sample Copper workflow
- 1Record Eventtrigger.copper_eventStart a run when a Copper CRM record is created, updated or deleted.
- 2Find Person by Emailcopper.fetch_person_by_emailLook a Person up by email address, which Copper treats as the unique key for People records.
- 3Bulk Create Leadscopper.bulk_create_leadsCreate up to ten Leads in one Copper call and report which of them were created and which Copper rejected, with its per-record error.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Triggers 1
Operations 47
- Bulk Create LeadsCreate up to ten Leads in one Copper call and report which of them were created and which Copper rejected, with its per-record error.copper.bulk_create_leads
- Convert LeadConvert a Lead into a Person, and optionally a Company and an Opportunity. Copper deletes the Lead once the conversion succeeds.copper.convert_lead
- Log ActivityLog an activity or note against a Copper record, using an activity type id from copper.list_activity_types.copper.create_activity
- Create CompanyCreate a Company in Copper. Copper requires only a name; every other field on the form is optional.copper.create_company
- Create LeadCreate a Lead in Copper. Copper requires only a name, and a Lead holds a single email address rather than a list.copper.create_lead
- Create OpportunityCreate an Opportunity (a deal) in Copper on a pipeline stage, with its value, close date and primary contact.copper.create_opportunity
- Create PersonCreate a Person (contact) in Copper. Copper requires only a name; everything else on the form is optional.copper.create_person
- Create ProjectCreate a Project in Copper. Copper requires only a name; status is either Open or Completed.copper.create_project
- Create TaskCreate a Task in Copper, optionally attached to a record and due on a date, and assign it to a user.copper.create_task
- Delete CompanyPermanently delete one Company from Copper and report the id and deletion flag the API confirms.copper.delete_company
- Delete LeadPermanently delete one Lead from Copper and report the id and deletion flag the API confirms.copper.delete_lead
- Delete OpportunityPermanently delete one Opportunity from Copper and report the id and deletion flag the API confirms.copper.delete_opportunity
- Delete PersonPermanently delete one Person from Copper and report the id and deletion flag the API confirms.copper.delete_person
- Delete ProjectPermanently delete one Project from Copper and report the id and deletion flag the API confirms.copper.delete_project
- Delete TaskPermanently delete one Task from Copper and report the id and deletion flag the API confirms.copper.delete_task
- Find Person by EmailLook a Person up by email address, which Copper treats as the unique key for People records.copper.fetch_person_by_email
- Get AccountRead the Copper account the connection's API key belongs to.copper.get_account
- Get CompanyFetch one Company from Copper by its id and return the record exactly as the API sends it, custom fields included.copper.get_company
- Get LeadFetch one Lead from Copper by its id and return the record exactly as the API sends it, custom fields included.copper.get_lead
- Get OpportunityFetch one Opportunity from Copper by its id and return the record exactly as the API sends it, custom fields included.copper.get_opportunity
- Get PersonFetch one Person from Copper by its id and return the record exactly as the API sends it, custom fields included.copper.get_person
- Get ProjectFetch one Project from Copper by its id and return the record exactly as the API sends it, custom fields included.copper.get_project
- Get TaskFetch one Task from Copper by its id and return the record exactly as the API sends it, custom fields included.copper.get_task
- List Activity TypesList the activity types available for logging, split into the account's own user types and Copper's system types.copper.list_activity_types
- List Contact TypesList the contact types Copper People and Companies can be classified with.copper.list_contact_types
- List Customer SourcesList the customer sources that say where a Lead or Opportunity came from.copper.list_customer_sources
- List Lead StatusesList the Lead statuses configured on the Copper account.copper.list_lead_statuses
- List Loss ReasonsList the loss reasons a lost Copper Opportunity can be given.copper.list_loss_reasons
- List Pipeline StagesList every pipeline stage on the Copper account, across all pipelines.copper.list_pipeline_stages
- List PipelinesList the Copper pipelines and the stages inside each of them.copper.list_pipelines
- List Related RecordsList every record related to one Copper record, as the id and type pairs the API returns.copper.list_related
- List UsersList the users on the Copper account so a workflow can turn a name into the assignee_id the write nodes need.copper.list_users
- Relate RecordsLink an existing Copper record to another record as a related item.copper.relate_record
- Search ActivitiesList or search activities logged in Copper, one page at a time.copper.search_activities
- Search CompaniesList or search Company records in Copper, one page at a time, using the search criteria the API documents.copper.search_companies
- Search LeadsList or search Lead records in Copper, one page at a time, using the search criteria the API documents.copper.search_leads
- Search OpportunitiesList or search Opportunity records in Copper, one page at a time, using the search criteria the API documents.copper.search_opportunities
- Search PeopleList or search Person records in Copper, one page at a time, using the search criteria the API documents.copper.search_people
- Search ProjectsList or search Project records in Copper, one page at a time, using the search criteria the API documents.copper.search_projects
- Search TasksList or search Task records in Copper, one page at a time, using the search criteria the API documents.copper.search_tasks
- Unrelate RecordsRemove the relationship between one Copper record and another.copper.unrelate_record
- Update CompanyUpdate one Company in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.copper.update_company
- Update LeadUpdate one Lead in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.copper.update_lead
- Update OpportunityUpdate one Opportunity in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.copper.update_opportunity
- Update PersonUpdate one Person in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.copper.update_person
- Update ProjectUpdate one Project in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.copper.update_project
- Update TaskUpdate one Task in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.copper.update_task
Copper questions
- How does OCNORA authenticate with Copper?
- With a stored API key credential, shaped the Copper API key or the API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Copper?
- 47 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Copper operation I need is not listed?
- Call https://api.copper.com/developer_api/v1 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Copper?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Copper calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Copper workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.