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 node provides integration with the LatePoint REST API, specifically enabling management of booking-related data. The "Get" operation under the "Bookings" resource allows users to retrieve detailed information about a specific booking by its unique identifier.
This node is beneficial in scenarios where you need to fetch booking details for processing, reporting, or automation workflows. For example, you might use it to:
- Retrieve a customer's appointment details before sending a reminder.
- Fetch booking information to update related records in another system.
- Access booking status and metadata for analytics or customer service purposes.
Properties
| Name | Meaning |
|---|---|
| Description | Provide a description or prompt for the AI to understand the context and purpose of this API operation. This helps clarify what the API call aims to achieve. |
| ID | The unique identifier of the booking to retrieve. This is required to specify which booking's details should be fetched. |
Output
The output is a JSON object representing the booking details retrieved from the LatePoint API. This typically includes all relevant fields of the booking such as:
- Booking ID
- Customer information
- Service details
- Agent/staff member assigned
- Start date and time
- Status (e.g., approved, pending)
- Notes and metadata if included
If multiple bookings were returned (not applicable for the "Get" operation but for "Get All"), the output would be an array of such objects. There is no binary data output for this operation.
Dependencies
- Requires configuration of an API key credential for authenticating with the LatePoint REST API.
- The base URL for the LatePoint API must be set in the 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 that credentials are missing. Ensure that a valid API key and base URL are set up in the node credentials.
- Invalid ID: Providing an invalid or non-existent booking ID will likely result in an API error or empty response. Verify the booking ID before making the request.
- Invalid JSON Body (for other operations): Although not applicable for "Get", other operations that accept JSON bodies may throw errors if the JSON is malformed.
- API Rate Limits or Connectivity Issues: Network problems or API rate limits can cause request failures. Check connectivity and API usage quotas.