Actions126
- Account Actions
- City Actions
- Contact Actions
- Contact Line of Business Actions
- Contact Number of Employees Actions
- Contact Origin Actions
- Contact Product Actions
- Contact Relationship Actions
- Contact Status Actions
- Contact Type Actions
- Country Actions
- Currency Actions
- Deal Actions
- Deal Loss Reason Actions
- Deal Pipeline Actions
- Deal Stage Actions
- Deal Status Actions
- Department Actions
- Document Actions
- Document Template Actions
- Field Actions
- Field Entity Actions
- Field Options Table Actions
- Field Options Table Option Actions
- Field Type Actions
- Interaction Record Actions
- Operation Actions
- Order Actions
- Order Stage Actions
- Phone Type Actions
- Product Actions
- Product Family Actions
- Product Group Actions
- Product Part Actions
- Quote Actions
- Quote Approval Status Actions
- Relative Date Actions
- Role Actions
- State Actions
- Tag Actions
- Task Actions
- Task Email Reminder Actions
- Task Repeat Interval Unit Actions
- Task Type Actions
- Team Actions
- User Actions
- User Profile Actions
- Webhook Actions
- Webhook Action Actions
Contact Status → Get Many
AI-generatedSummary
Retrieve contact status records from Ploomes CRM using GET /Contacts@Status, with optional OData filtering, sorting, field selection, and relation expansion. By default, return at most one record containing only its Id.
Inputs
- cacheStrategy — Choose disabled (default), cacheFirst, or fallbackOnly. Cache First uses a valid cached response before requesting the API; Fallback Only requests the API and uses valid cache if the request fails. Cache is held in memory while n8n runs.
- cacheTtl — Set cache validity in seconds when caching is enabled; defaults to 300.
- top — Maximum records to request through $top; defaults to 1.
- skip — Number of records to skip for manual pagination; defaults to 0.
- select — Comma-separated fields to return; defaults to Id. An empty value omits $select.
- orderby — OData sort fields with optional asc/desc directions; defaults to Id. An empty value omits $orderby.
- useFilterBuilder — Use visual filter collections (default true) or a raw OData filter.
- filterRaw — Optional raw $filter expression, used when Use Filter Builder is disabled.
- filterConditions — Optional visual conditions specifying field, operator, value, value type, and AND/OR connector. Supports comparisons and contains/startswith/endswith. Auto detects unsigned numbers; other values are quoted.
- customPropertyFilters — Optional OtherProperties/any filters specifying custom field ID, value property, comparison operator, value, and whether to leave the value unquoted. Combined with AND when the filter builder is enabled.
- collectionFilters — Optional navigation filters specifying collection-any or direct navigation, property name, field, operator, value, and AND/OR connector. Appended to other builder filters with AND.
- useExpandBuilder — Use visual relation expansions (default true) or a raw OData expansion.
- expandRaw — Optional raw $expand expression, used when Use Expand Builder is disabled.
- expandRelations — Optional relations to expand, each with a property name and optional nested field selection, enabled raw filter, and enabled nested expansion. Available relations depend on the API.
- expandNestedFilters — Optional visual filters targeting property names listed in Expand Relations. Specify field, operator, value, numeric flag, and AND/OR connector; combined with any raw filter for the same expansion using AND.
Output shape
Three output branches: Success, Error, and Timeout. Success normally contains one n8n JSON item per contact status record in the response's value array.
Runs once per incoming item and does not automatically fetch additional pages; use top and skip for pagination. Returned fields depend on select and expand settings. An empty value array produces no success items; a response without a value array is returned as one item, and an empty body produces a success marker. Cached items include _fromCache: true; fallback items also include _fallback: true. HTTP 408/504 errors go to Timeout. Other errors go to Error when Continue On Fail is enabled; otherwise execution throws. Error payloads contain error, statusCode, isTimeout, resource, operation, and timestamp.
