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.
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 |
{"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"}
{"id": 456,"name": "Enterprise Deal","pipeline_id": 1,"monetary_value": 10000}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.