ActionCopperUpdated September 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 All 6 Copper actions

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.

Field	Type	Required	Description
Opportunity Name name	string	Required	Opportunity Name. Example: Enterprise Deal
Value monetary_value	string	Optional	Value. Example: 10000
Pipeline ID pipeline_id	string	Required	Pipeline ID. Example: 1
Stage ID pipeline_stage_id	string	Required	Stage ID. Example: 1
Primary Contact ID primary_contact_id	string	Optional	Primary Contact ID. Example: 123
Close Date close_date	string	Optional	MM/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.

Google Sheets → Copper

2 Google Sheets triggers

HubSpot → Copper

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Copper returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Opportunity support batch operations?

Run Create Opportunity inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Copper's rate limits.

More actions