Short answer: Drop the "Salesforce → List Salesforce Records" 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 |
|---|---|---|---|
Object Type sobject | options | Required | Object Type. Options: Lead, Contact, Account, Opportunity, Case, Task |
Fields fields | string | Optional | Comma-separated field names to retrieve |
WHERE Clause where_clause | string | Optional | Optional SOQL WHERE clause to filter results (without the WHERE keyword) |
Order By order_by | string | Optional | Field name and direction to sort results |
Limit limit | string | Optional | Maximum number of records to return |
{"sobject": "{{trigger.sobject}}","fields": "e.g. Id,Name,Email,CreatedDate","where_clause": "e.g. CreatedDate = THIS_MONTH AND Status = 'Open'","order_by": "e.g. CreatedDate DESC","limit": "e.g. 50"}
{"done": true,"records": [{"Id": "001Dn00000XXXXX","Name": "Acme Inc","CreatedDate": "2025-01-15T12:00:00.000Z"}],"totalSize": 5}
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.