Short answer: You can salesforce sosl search in Salesforce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Salesforce Salesforce SOSL Search action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Search Term search_term | string | Required | The text to search for across Salesforce records |
Objects to Search objects | string | Optional | Comma-separated object names with optional field lists in parentheses |
WHERE Clause where_clause | string | Optional | Optional WHERE clause to filter results (without WHERE keyword) |
{"search_term": "e.g. Acme","objects": "e.g. Lead(Id,Name,Email), Contact(Id,Name,Email), Account(Id,Name)","where_clause": "e.g. Name != 'Test'"}
{"searchRecords": [{"Id": "003Dn00000XXXXX","Name": "John Doe","attributes": {"url": "/services/data/v59.0/sobjects/Contact/003Dn00000XXXXX","type": "Contact"}},{"Id": "001Dn00000XXXXX","Name": "Acme Inc","attributes": {"url": "/services/data/v59.0/sobjects/Account/001Dn00000XXXXX","type": "Account"}}]}
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.