Update Opportunity: Salesforce action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Update Opportunity support batch operations?

Yes. Run Update Opportunity inside a Loop node to process arrays. Tiny Command handles Salesforce's rate limits automatically so you don't have to throttle manually.

More actions