Copper n8n integrationAutomate Copper with n8n.

Adds a company to Copper and passes the created record to the next node.

• Name: the only required field, the company name as it should read in the CRM. Map it from an earlier node with an expression like {{ $json.field }}.
• Additional Fields: an optional block carrying Email Domain, Details, Address and Phone Numbers. The last two open as sub-blocks you fill line by line, via Add Address Fields and Add Phone Number.

Removes a company from Copper for good. Treat it as the end of a branch, not a step in the middle of one.

• Company ID: required, and it is the Copper identifier, not the company name. If the workflow only knows the name, run Get Many with the Name filter first and pass the identifier along.

Reads a single company and returns its record, which is how a workflow gets the current state of an account instead of the state it had when the trigger fired.

• Company ID: required. Coming out of the Copper Trigger or a previous read, it is usually mapped as an expression rather than typed in.

Lists companies in bulk, which is the operation behind exports, audits and any recurring account review.

• Return All: on, n8n chains the API pages and brings back every company. Off, Limit sets how many records come back, which keeps test runs short.
• Filters: Country picks the company country from a list of codes, and Name narrows to a company name.

Edits an existing company record. Only the fields you fill are sent, so the rest of the record stays untouched.

• Company ID: required, and it says which record gets edited.
• Update Fields: the optional block holding Name, Details, Address and Phone Numbers. Note that Email Domain is not part of this block, unlike the create side.

Returns the customer sources configured in Copper, the labels that record where a deal came from. It is the lookup you run before writing anything on an opportunity.

• Return All: on, the full list comes back, which is usually what you want since there are rarely many. Off, Limit caps the number returned.

Writes a lead into Copper, the stage before a contact has been qualified into a person and a company.

• Name: required. Anything else is optional, so an incomplete form can still land rather than being dropped.
• Additional Fields: carries Email, Phone Numbers and Address, each opened through its own Add button.

Erases a lead from Copper. Useful precisely because leads pile up faster than any other object in a CRM.

• Lead ID: required. The identifier, not the lead name, so a cleanup workflow reads before it deletes.

Fetches one lead and hands its record to the next node. The read you place between a trigger and a decision.

• Lead ID: required. Typically an expression such as {{ $json.field }} carrying the identifier from whatever ran before.

Pulls leads in batches, filtered or not. This is the reading half of every lead scoring or nurturing workflow.

• Return All: on for a complete export, off to stop at Limit.
• Filters: here Country is a plain text field, the country name, not a code list like on companies. Name filters on the lead name.

Changes a lead already in Copper, field by field, without rewriting the whole record.

• Lead ID: required, the record to edit.
• Update Fields: the widest of the lead blocks, with Name, Details, Email, Phone Numbers and Address. Details is where a scoring note or a call summary fits.

Opens a deal in Copper and returns it, which is how a qualified conversation becomes a line in the pipeline.

• Name: required, the deal name.
• Primary Contact ID: optional, the identifier of the primary company attached to the deal.
• Customer Source ID: optional, the identifier of the source that generated the opportunity. Read it first with Get Many on customer sources rather than hardcoding it.

Drops a deal from Copper. Rarely automated on its own, often the last step of a cleanup branch.

• Opportunity ID: required. Get it from a previous read or from the trigger, never from the deal name.

Loads one deal and returns its current record, including whatever has changed since the workflow last looked.

• Opportunity ID: required, mapped from the trigger or from an earlier list operation.

Returns deals in bulk. Pipeline reporting in n8n starts here, and so does anything that needs to look at more than one deal at a time.

• Return All: on to walk every page of the pipeline, off to stop at Limit.
• Filters: Company IDs and Customer Source IDs both take comma separated identifiers, so several accounts or several sources fit in one call.

Edits a deal in place, which is what moves a workflow from reading the pipeline to actually maintaining it.

• Opportunity ID: required, the deal to edit.
• Update Fields: Name, Primary Contact ID and Customer Source ID. The two identifiers let a workflow reattach a deal to another company or another source without anyone opening Copper.

Adds a contact to Copper. The most used write of the whole node, and the one most workflows end on.

• Name: required, the contact name.
• Additional Fields: the richest optional block of the node, with Emails, Phone Numbers, Address, Email Domain and Details. Emails and Phone Numbers accept several entries through Add Email and Add Phone Number.

Removes a contact from Copper permanently. No confirmation step, so gate it behind a condition in the workflow.

• Person ID: required, the Copper identifier of the contact.

Reads one contact and returns the record, which makes it the natural first step after any trigger that only hands over an identifier.

• Person ID: required. An expression like {{ $json.field }} is the usual way to pass it from the node before.

Lists contacts, the read behind every synchronization between Copper and a mailing tool or a spreadsheet.

• Return All: on, every contact comes back page after page. Off, Limit decides how many, which matters on a contact book that has grown for years.
• Filters: a single Name filter, so narrowing happens on the contact name and nothing else.

Rewrites the fields you choose on an existing contact and leaves the others alone.

• Person ID: required, the contact to edit.
• Update Fields: the largest block in the node, with Name, Emails, Phone Numbers, Address, Email Domain and Details. Sending an empty block does nothing, which is a safe default when a branch is unsure.

Copper gets a new project record built from data already moving through the workflow, so a signed deal turns into a delivery folder without anyone retyping it.

• Name: required, the name the project is created with. Pull it from the incoming item with an expression such as {{ $json.field }} when it comes from a form or a spreadsheet row.
• Additional Fields: optional extras applied at creation. Assignee ID is the ID of the user who will own the project, Details carries the description, and Status accepts Open or Completed.

Cleanup runs through this one: it removes a single project from Copper, which keeps test records and duplicated folders out of everyone's view.

• Project ID: required, the ID of the project to delete. Copper expects the identifier here, not the project name, so read it from a previous step instead of typing a label.

When a workflow only carries an identifier, this operation reads the matching project back from Copper so the next steps have something to work with.

• Project ID: required, the ID of the project to retrieve. It usually arrives from the trigger, the node that starts the workflow, or from a lookup run a step earlier.

Reporting starts here. The operation lists the projects held in Copper, either the full set or a capped batch, and hands them to the rest of the workflow one item at a time.

• Return All: switched on, n8n chains through the API pages until every project has come back; switched off, Limit sets the maximum number of projects returned.
• Filters: the Name filter narrows the list to projects matching that name, which beats pulling everything and sorting it downstream.

A project lives for weeks and its details move. This operation writes onto a project that already exists in Copper, so the CRM follows the delivery instead of describing its first day.

• Project ID: required, the ID of the project to update.
• Update Fields: only what you fill in gets written. Name renames the project, Details replaces the description, Assignee ID hands ownership to another user, and Status moves it between Open and Completed.

Follow-up work lands in the CRM instead of somebody's inbox: the operation adds a task to Copper from whatever the workflow just produced.

• Name: required, the text of the task itself. Keep it readable, it is what the assignee sees in Copper.
• Additional Fields: Assignee ID for the user who will own the task, Details for the longer description, Priority set to High or None, and Status set to Open or Completed.

A task leaves Copper here, one call per identifier, which is what an automated tidy-up needs when two workflows fire on the same event and both create the same reminder.

• Task ID: required, the ID of the task to delete. Feed it from the step that found the task, since Copper matches on the identifier and not on the task name.

Reading a single task back is useful before deciding anything: the operation returns the task matching the identifier it is given.

• Task ID: required, the ID of the task to retrieve, usually carried over from the trigger output or from a list step run just before.

Batches of tasks come out of Copper through this operation, which is how workload reviews and daily digests get their raw material.

• Return All: on, n8n keeps requesting pages until the whole task list is returned; off, Limit caps how many tasks come back in one run.
• Filters: Assignee IDs and Project IDs both take comma-separated identifiers, so a single node can cover one team or one delivery project.

Reassignment, renaming and status changes all go through this operation, which edits a task already stored in Copper.

• Task ID: required, the ID of the task to update.
• Update Fields: Assignee ID moves ownership to another user, Name and Details rewrite the task text and its description, Priority takes High or None, and Status takes Open or Completed.

The people side of the account shows up here: the operation lists the users of the Copper account the credential opens, a credential being the saved connection you create once in n8n.

• Return All: on, every user comes back; off, Limit decides how many the node returns in one execution.