Actions38
- Bookings Actions
- Customers Actions
- Agents Actions
- Services Actions
- Payments Actions
- Orders Actions
- Coupons Actions
- Locations Actions
- Availability Actions
Orders → Get All
AI-generatedSummary
Retrieves orders from the LatePoint REST API (GET /orders), with optional filtering, sorting, and either single-page or automatic multi-page retrieval.
Inputs
- Use Filters — Toggle that reveals the predefined Filters collection. Off by default. When off, only Additional Filters (JSON) is applied.
- Filters — Collection of optional filters, sent as query parameters: customer_id, status (open/completed/cancelled), payment_status, fulfillment_status, total_min, total_max, created_date_from, created_date_to, coupon_code, search, sort (id/total/created_at/status), order (asc/desc), include_meta, meta_key, meta_value. Empty values are skipped. For orders, the created_date_from and created_date_to keys are renamed to created_after and created_before in the request.
- Additional Filters (JSON) — JSON object of extra query parameters, merged over the other parameters, so its keys override duplicates. Works whether or not Use Filters is on. Invalid JSON is silently ignored.
- Return All — If true, fetches every page and returns one n8n item per order. If false, fetches a single page.
- Max Pages — Shown when Return All is true. Caps the number of pages fetched. 0 means unlimited.
- Limit — Shown when Return All is false. Orders per page, sent as per_page (1–100, default 10).
- Page — Shown when Return All is false. Page number to fetch (default 1).
- Description — Free-text note describing the intent for AI use. It is not sent to the API.
Output shape
With Return All off: one item containing the raw API response, typically a data array of orders plus a pagination object. With Return All on: one item per order, taken from each page's data array.
Return All keeps requesting pages while pagination.has_next_page is true, or until Max Pages is reached. The pagination object is not included in this mode. On error, the node throws, or with Continue On Fail it returns an item with an error message. Authentication uses a Bearer API key from the credentials.
Examples
Example 1: List unpaid open orders for a customer
Use Filters on; Filters: customer_id=42, status=open, payment_status=not_paid; Return All off, Limit 50.
Example 2: Export all orders created in a date range
Use Filters on; created_date_from=2024-01-01, created_date_to=2024-01-31; Return All on, Max Pages 0.
Example 3: Pass a filter not in the UI
Additional Filters (JSON): {"customer_id": 5}; Use Filters off; Return All off.