Create opportunity
Identifier and availability
- Type:
action - Stable identifier:
opportunity:create - Status: Selectable — available in the new-node selector and importable.
Purpose
Creates an opportunity for the current contact.
Prerequisites and context
Required configuration: pipeline, pipeline_status, settings. Runtime requires a contact in context.
Parameters
| JSON path | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
pipeline |
pipeline_reference | Yes | — | — | Exact Pipeline name in the importing tenant. |
pipeline_status |
pipeline_status_reference | Yes | — | — | Exact Pipeline Status name within the selected Pipeline. |
settings |
object | Yes | — | — | Node-specific settings. Unknown keys are rejected. |
settings.name |
string | No | — | — | Opportunity name (leave blank to use contact name) |
settings.value |
numeric_or_template | No | — | — | Optional non-negative projected value with at most 13 integer and 2 decimal digits, or a documented full numeric variable token. |
Unknown parameter and settings keys are rejected. Resource references use names, emails, document keys, or endpoints rather than database IDs.
Inputs and available variables
Context exposed on following path: opportunity.
Templated strings use double braces, for example {{contact.first_name}}. Availability in the editor does not create runtime context; the trigger and preceding branch still need to provide it.
Connections and branches
This is a sequential action with no branch ports. A root placement uses from set to null and branch set to actions; a branch placement uses the branching action key and branch token. Use a 1-based order within that path.
Connection fragment:
{
"from": null,
"to": "action_opportunity_create",
"branch": "actions",
"order": 1
}
Valid JSON node example
{
"key": "action_opportunity_create",
"type": "action",
"name": "opportunity:create",
"display_name": null,
"parameters": {
"pipeline": {
"name": "Sales"
},
"pipeline_status": {
"name": "New Lead"
},
"settings": {
"name": "{{contact.full_name}} opportunity",
"value": "2500"
}
}
}
Validation and runtime caveats
Projected value must be a non-negative decimal with at most 13 integer and 2 fractional digits, or a documented full variable that resolves to that shape.
See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.