Actions40
- Bookings Actions
- Customers Actions
- Agents Actions
- Services Actions
- Payments Actions
- Orders Actions
- Coupons Actions
- Locations Actions
- Availability Actions
- System Info Actions
- Test Actions
Overview
The "Get Order" operation of this LatePoint API node allows you to retrieve detailed information about a specific order by its unique identifier. This is useful in scenarios where you need to fetch the current status, payment details, fulfillment state, or any other metadata related to an individual order within your booking and customer management workflows.
Practical examples include:
- Fetching order details to display in a customer support dashboard.
- Retrieving order information before updating or processing payments.
- Integrating order data into external systems for reporting or analytics.
Properties
| Name | Meaning |
|---|---|
| Description | Provide a description or prompt for the AI to understand the context and purpose of this API operation. |
| ID | The unique identifier of the order to retrieve. This is required to specify which order to get. |
Output
The node outputs the retrieved order data as JSON in the json field of the output item. The structure corresponds to the order object returned by the LatePoint REST API, typically including fields such as order ID, customer ID, order status, payment status, fulfillment status, total amounts, coupon codes, creation date, and optionally metadata if requested.
No binary data output is produced by this operation.
Dependencies
- Requires configuration of an API key credential for authenticating with the LatePoint REST API.
- The base URL and API key must be set in the node credentials.
- Network access to the LatePoint API endpoint is necessary.
Troubleshooting
- Missing Credentials Error: If no API credentials are configured, the node will throw an error indicating missing credentials. Ensure that a valid API key credential is set up.
- Invalid ID: Providing an invalid or non-existent order ID may result in an error or empty response. Verify the correctness of the order ID.
- API Request Failures: Network issues or incorrect API keys can cause request failures. Check connectivity and credential validity.
- JSON Parsing Errors: Not applicable for this operation since it does not accept JSON body input.