Short answer: Drop the "Close → Create Opportunity" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Lead ID lead_id | string | Required | Lead ID. Example: lead_abc123 |
Note note | string | Optional | Note. Example: Interested in enterprise plan |
Value (cents) value | string | Optional | Opportunity value in cents |
Currency value_currency | string | Optional | Currency. e.g. "USD" |
Confidence % confidence | string | Optional | Win probability (0-100) |
Status ID status_id | string | Optional | Status ID. Example: stat_abc |
{"lead_id": "e.g. lead_abc123","note": "e.g. Interested in enterprise plan","value": "e.g. 1000000 for $10,000","value_currency": "USD","confidence": "e.g. 75"}
{"id": "oppo_abc","value": 1000000,"lead_id": "lead_abc123","confidence": 75}
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.
Triggered by anything in the catalog. Free tier available. No credit card.