ActionCloseUpdated September 2026
How do I create a Close opportunity?
Short answer: You can create opportunity in Close by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Close 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.
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 |
|---|---|---|---|
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 |
Sample request
{"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"}
Returns
{"id": "oppo_abc","value": 1000000,"lead_id": "lead_abc123","confidence": 75}
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 Close?
Creates a sales opportunity tied to a lead with value, expected close date, status, pipeline. Useful for "auto-create opportunity when lead reaches qualification score" workflows.
What inputs does Create Opportunity require?
Required: Lead 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 Close returns an error?
The run history shows the failed step with its input and the error message Close 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 Close's rate limits.
More actions
Other Close actions.
Action
Create Lead
Creates a new lead (company-level record) in Close CRM with contacts, addresses, custom fields. Close's lead-first model means each company is one lead, with multiple contacts nested. The standard hook for "B2B form submission → push to Close" sync workflows.
ActionCreate Task
Creates a follow-up task for a sales rep tied to a lead with due date and notes. Useful for "deal stagnant for N days → create follow-up task for the AE" hygiene automation.
ActionDelete Lead
Hard-deletes a lead and all associated contacts, activities, opportunities. Irreversible. For GDPR right-to-erasure compliance workflows; for soft removal that preserves activity history, change the lead status to "Archived" instead.
ActionGet Lead
Returns a lead by ID with contacts, custom fields, opportunities, and recent activities. The standard lookup for enrichment workflows or for round-trip operations that need the current lead state.
ActionList Leads
Paginated leads with filters by status, custom fields, recently updated. For sync workflows that mirror Close into a warehouse or BI dashboard, paginate with the date_updated filter for incremental pulls.
ActionLog Activity
Logs a custom activity (call, email, note, meeting) on a lead's timeline. Useful for "AI-summarised post-call notes from Gong/Fireflies → log on the matching Close lead" workflows that keep the rep's history complete.