Actions134
- Activity Actions
- Activity Type Actions
- Call Actions
- Call Outcome Actions
- Comment Actions
- Company Actions
- Contact Actions
- Country Actions
- Currency Actions
- Deal Actions
- Document Actions
- Document Type Actions
- Industry Actions
- Note Actions
- Pipeline Actions
- Pipeline Stage Actions
- Product Actions
- Role Actions
- Source Actions
- Team Actions
- Timezone Actions
- Trashed Record Actions
- User Actions
Call Outcome → Search
AI-generatedSummary
Searches LLW CRM call outcomes by a query string, calling GET /call-outcomes/search with the query as q. It returns matching records, either all pages or up to a limit.
Inputs
- Search Query (required) — Search string, sent as the
qquery parameter. - Return All — If true, follows pagination (page=1,2,…) until no more pages and returns every match. Default false.
- Limit — Shown when Return All is off. Max results, sent as
per_page(1–250, default 50). - Additional Fields — Optional extras passed straight through as query parameters: Fields (comma-separated fields to return), Sort By (
order_by), Sort Direction (order_dir, asc or desc).
Output shape
One n8n item per matching call outcome, with the API record as the item JSON. Each item is paired to its input item.
When Return All is off, only a single page is requested. The node uses the response's
dataarray if present, otherwise the raw response. Returned fields depend on the CRM API, typically id and name. With Continue On Fail enabled, a failed item yields an item with anerrormessage instead of stopping the workflow. The node runs once per input item.
Examples
Example 1: Find call outcomes whose name contains "voicemail"
Resource: Call Outcome; Operation: Search; Search Query: voicemail; Return All: off; Limit: 50
Example 2: Export all matching outcomes sorted by name
Search Query: "no answer"; Return All: on; Additional Fields: Sort By = name, Sort Direction = Ascending