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
This node interacts with the LatePoint REST API to retrieve booking data. Specifically, the "Get All" operation for the "Bookings" resource allows users to fetch multiple bookings from their LatePoint system, applying various filters and sorting options to tailor the results.
Common scenarios where this node is beneficial include:
- Retrieving a list of all upcoming or past bookings within a specific date range.
- Filtering bookings by status (e.g., approved, pending, cancelled) or payment status.
- Searching bookings by customer details, booking codes, or service-related criteria.
- Exporting booking data for reporting or integration with other systems.
Practical example: A business owner wants to get all approved bookings scheduled in the next week, sorted by start date descending, to prepare staff schedules.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down bookings. Options include: - Status: approved, pending, cancelled, completed, no show - Customer ID - Agent ID - Service ID - Location ID - Date From/To (YYYY-MM-DD) - Created Date From/To - Booking Code - Payment Status: not paid, paid, partially paid - Duration Min/Max (minutes) - Price Min/Max - Customer Email - Customer Phone - Search (across booking fields) - Sort By: id, start date, created date, customer name, service name, status - Sort Order: ascending, descending - Include Meta (boolean): whether to include booking metadata - Meta Key/Value: filter by specific metadata key/value |
| Description | Optional text description or prompt to provide context or purpose for the API call. |
| Return All | Boolean indicating whether to return all matching bookings or limit the number of results. |
| Limit | Maximum number of bookings to return if "Return All" is false. Value between 1 and 100. |
Output
The node outputs an array of JSON objects, each representing a booking record retrieved from the LatePoint API. Each booking object contains detailed booking information such as IDs, dates, customer and agent references, status, payment info, and optionally metadata if requested.
If metadata inclusion is enabled, additional custom fields related to each booking are included in the output.
The node does not output binary data.
Dependencies
- Requires connection to the LatePoint REST API.
- Requires configuration of an API key credential for authentication.
- The base URL and API key must be set in the node credentials before execution.
Troubleshooting
- No credentials configured!: This error occurs if the API key credential is missing or not set up correctly. Ensure you have configured the required API authentication token in n8n credentials.
- Invalid JSON in body: If using advanced features like bulk creation or custom JSON bodies, ensure that the JSON syntax is valid.
- Empty or incomplete results: Check your filter parameters; overly restrictive filters may return no data.
- API rate limits or connectivity issues: Network problems or API limits can cause failures. Verify network access and API usage quotas.