Create Opportunity

copper.create_opportunity
ActionCRM & salesconnection required

Calls the Copper API with the connection's credentials.

Create an Opportunity (a deal) in Copper on a pipeline stage, with its value, close date and primary contact.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Copper
Secret shape
the API key, or {"api_key": "…"}
Config it needs
user_email, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

15 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
name
The name of the deal.
stringYes——Acme renewal
primary_contact_id
The Copper Person who is the primary contact. Copper's Opportunity property table marks this required, so set it unless your account allows otherwise.
stringNo———
company_id
The Copper Company the deal belongs to.
stringNo———
pipeline_id
A pipeline id from copper.list_pipelines.
stringNo———
pipeline_stage_id
A stage id from copper.list_pipelines or copper.list_pipeline_stages.
stringNo———
monetary_value
The value of the deal in the account currency.
numberNo—≥ 0—
close_date
The expected close date, in MM/DD/YYYY or DD/MM/YYYY as the account is set up.
stringNo——12/31/2026
customer_source_id
A customer source id from copper.list_customer_sources.
stringNo———
priority
The deal priority, from Copper's fixed set.
stringNo—one of "None", "Low", "Medium", "High"—
status
The deal status, from Copper's fixed set.
stringNoOpenone of "Open", "Won", "Lost", "Abandoned"—
win_probability
The chance of winning the deal, as a percentage.
numberNo—0–100—
details
A description stored on the record.
stringNo———
assignee_id
The Copper user who should own this record.
stringNo———
tags
Tags to set on the record, as a JSON array of strings or a comma-separated list.
arrayNo—array of string—
fields
Any further Copper fields, as a JSON object of Copper field names (custom_fields, address, websites, socials …). These are merged over the fields named above, so this node can set anything the API accepts.
objectNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "close_date": "12/31/2026",
  "name": "Acme renewal",
  "status": "Open"
}

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

See Create Opportunity run in a workflow.

In a technical demo we add the Copper connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.