Ploomes CRM icon

Ploomes CRM

Interact with the Ploomes CRM API with full OData support

Actions126

Account → Get Many

AI-generated

Summary

Retrieve multiple Account records from Ploomes CRM using customizable OData query parameters with optional caching.

Inputs

  • Cache Strategy — Strategy to use in-memory cache for GET requests (Disabled, Cache First, Fallback Only). Cache persists while n8n is running.
  • Cache TTL (Seconds) — Time-to-live for cached responses in seconds, applicable if caching is enabled.
  • $top (Limit) — Maximum number of Account records to return, default is 1.
  • $skip (Offset) — Number of records to skip for pagination, default is 0.
  • $select (Fields) — Comma-separated list of Account fields to return; defaults to "Id" for optimized queries.
  • $orderby (Sort) — Field to sort the returned records by, with optional direction; defaults to "Id".
  • Use Filter Builder — Whether to use the visual filter builder or provide a raw OData $filter string.
  • $filter (Raw) — Raw OData $filter expression when not using the filter builder.
  • Filter Conditions — Visual builder to specify OData $filter conditions with fields, operators, values, and logical operators.
  • Custom Property Filters — Filter by custom field values on Account's OtherProperties; combined with AND logic to main filter.
  • Navigation Property Filters — Filter based on navigation properties, either as a collection with any() or direct navigation.
  • Use Expand Builder — Whether to use the visual expand builder or provide a raw OData $expand string.
  • $expand (Raw) — Raw OData $expand expression when not using the expand builder.
  • Expand Relations — Visual builder for expanding related entities of Account with optional nested selections, filters, and expansions.
  • Expand Nested Filters — Visual filter builder for nested $filter conditions inside expanded relations.

Output shape

a list of Account records as JSON objects, each representing one Account; includes metadata fields such as _fromCache or _fallback if caching was applied

Supports OData options for pagination, sorting, filtering, and expanding related entities. Caching behavior depends on the Cache Strategy and Cache TTL settings. Returns multiple records wrapped as individual items in the node output.

Examples

Example 1: Retrieve up to 10 Account records, selecting Id and Name, filtering for active accounts, sorted by Name ascending.

Set $top to 10, $select to "Id,Name", build filter condition for status active, and set $orderby to "Name asc".

Links

Discussion