List Opportunities: 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
Limit limit	string	Optional	—
Stage Filter stage_filter	string	Optional	Optional — exact stage name to filter (e.g. 'Prospecting'). Leave blank for all.

Sample request

{
  "limit": "{{trigger.limit}}",
  "stage_filter": "{{trigger.stage_filter}}"
}

Returns

{
  "done": true,
  "records": [
    {
      "Id": "006...",
      "Name": "Big Deal",
      "Amount": 50000,
      "AccountId": "001...",
      "CloseDate": "2026-06-30",
      "StageName": "Prospecting",
      "Probability": 10
    }
  ],
  "totalSize": 1
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Opportunities.

What does the List Opportunities action do in Salesforce?

Lists Salesforce Opportunities, most recently modified first. For complex filters use a SOQL query instead; this action is the simple paginated read.

What inputs does List Opportunities require?

List Opportunities has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Opportunities support batch operations?

Yes. Run List Opportunities 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