ActionCopperUpdated June 2026

How do I create a Copper opportunity?

Short answer: You can create opportunity in Copper by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Copper Create Opportunity action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Opportunity in Copper — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Opportunity Name
name
stringRequiredOpportunity Name. Example: Enterprise Deal
Value
monetary_value
stringOptionalValue. Example: 10000
Pipeline ID
pipeline_id
stringRequiredPipeline ID. Example: 1
Stage ID
pipeline_stage_id
stringRequiredStage ID. Example: 1
Primary Contact ID
primary_contact_id
stringOptionalPrimary Contact ID. Example: 123
Close Date
close_date
stringOptionalMM/DD/YYYY format
Sample request
{
"name": "e.g. Enterprise Deal",
"monetary_value": "e.g. 10000",
"pipeline_id": "e.g. 1",
"pipeline_stage_id": "e.g. 1",
"primary_contact_id": "e.g. 123"
}
Returns
{
"id": 456,
"name": "Enterprise Deal",
"pipeline_id": 1,
"monetary_value": 10000
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Opportunity.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create Opportunity.

What does the Create Opportunity action do in Copper?
Creates a sales opportunity tied to a person and/or company with value, pipeline, stage, owner. For "form said they want to buy → auto-create opportunity for the AE" workflows.
What inputs does Create Opportunity require?
Required: Opportunity Name, Pipeline ID, Stage ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Copper returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Create Opportunity support batch operations?
Yes. Run Create Opportunity inside a Loop node to process arrays. TinyCommand handles Copper's rate limits automatically so you don't have to throttle manually.
More actions

Other Copper actions.

Action
Create Person
Inserts a new person with email, name, phone, optional company link, custom fields. Copper dedupes on primary email; existing emails error rather than upserting (wrap in search-first if uncertain).
Action
Get Person
Returns a person by ID or email with all standard and custom fields plus related company and recent activities. The standard lookup before update workflows.
Action
List Leads
Paginated leads with filters by status, source, owner, modified date. For sync workflows to a warehouse or for "leads stale 30+ days, send re-engagement" lifecycle automation.
Action
List People
Paginated people with filters by company, owner, custom-field values. For warehouse syncs use the modified-since filter to incrementally pull only touched records.
Action
Update Person
Partial update — only passed fields change. For "Clearbit enrichment ran → write firmographic data back to Copper" or "support ticket categorized → add tag to person" augmentation workflows.
Create Opportunity in Copper — start free