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
Order → Get Many
AI-generatedSummary
Retrieve multiple Order records from Ploomes CRM using OData query options, with optional caching.
Inputs
- Main — Each incoming item triggers a separate request; if no items are provided, the node runs once.
Output shape
array per branch
The node returns three output arrays: Success, Error, and Timeout. Each array element is an object with a
jsonfield containing the result data.
Examples
Example 1: Fetch the first 10 Orders, selecting only Id and Name, sorted by Name ascending.
resource: Order, operation: Get Many, top: 10, skip: 0, select: Id,Name, orderby: Name asc
Example 2: Retrieve Orders created after a given date using a raw $filter.
resource: Order, operation: Get Many, useFilterBuilder: false, filterRaw: CreatedDate gt 2024-01-01