ActionSalesforceUpdated September 2026
How do I update a Salesforce Opportunity?
Short answer: You can update opportunity in Salesforce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Salesforce Update 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 |
|---|---|---|---|
Opportunity ID opportunity_id | string | Required | – |
Stage StageName | string | Optional | – |
Amount Amount | string | Optional | – |
Close Date CloseDate | string | Optional | – |
Probability Probability | string | Optional | – |
Description Description | string | Optional | – |
Sample request
{"opportunity_id": "{{trigger.opportunity_id}}","StageName": "{{trigger.StageName}}","Amount": "{{trigger.Amount}}","CloseDate": "{{trigger.CloseDate}}","Probability": "{{trigger.Probability}}"}
Returns
{"id": "{{inputs.opportunity_id}}"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Opportunity.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Opportunity.
What does the Update Opportunity action do in Salesforce?
Updates Salesforce Opportunity fields, including stage transitions, amount, close date, and forecast category. The standard write for keeping pipeline state in sync from external sources.
What inputs does Update Opportunity require?
Required: Opportunity 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 Salesforce returns an error?
The run history shows the failed step with its input and the error message Salesforce 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 Update Opportunity support batch operations?
Run Update 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 Salesforce's rate limits.
More actions
Other Salesforce actions.
Action
Convert Lead
Converts a Salesforce Lead into an Account, Contact, and (optionally) Opportunity, following standard SFDC lead-conversion rules. Used at the SQL/handoff step in your funnel automation.
ActionCreate Account
Creates a new Account (company) record in Salesforce with name, website, industry, owner, and any custom fields. Used to mirror your CRM's source-of-truth accounts into SFDC.
ActionCreate Contact
Creates a new Contact record in Salesforce with name, email, phone, account, owner, and any custom fields. The default write action for piping inbound leads into SFDC.
ActionCreate Note
Creates a Note linked to a parent Salesforce record (Account, Contact, Lead, Opportunity, etc.) with title and body. Used for AI summary notes or pulling context from external systems.
ActionFind Contact by Email
Convenience search that finds a Salesforce Contact by exact email match. The standard upsert lookup before deciding to create or update.
ActionGet Account
Retrieves a Salesforce Account by ID with all of its standard and custom fields. The standard read after a trigger fires with an account ID.