Actions12
Overview
This node integrates with the Bookla API to retrieve booking information. Specifically, the "Booking" resource with the "Get" operation allows users to fetch details of a single booking by its unique identifier within a specified company.
Common scenarios for this node include:
- Retrieving detailed information about a specific booking for confirmation or review.
- Integrating booking data into workflows such as notifications, reporting, or CRM updates.
- Automating follow-up actions based on booking status or details.
For example, a user might use this node to get booking details after a customer schedules an appointment, then send a confirmation email with the retrieved data.
Properties
| Name | Meaning |
|---|---|
| Server | Select which Bookla server to connect to. Options: US Server, EU Server |
| Company ID | The unique identifier of the company owning the booking. |
| Booking ID | The unique identifier of the booking to retrieve. |
Output
The node outputs JSON data representing the booking details fetched from the Bookla API. This typically includes all relevant booking information such as booking time, client info, service details, status, and any other metadata associated with the booking.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Bookla API.
- The node dynamically constructs the base URL depending on the selected server (US or EU).
- Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Missing or invalid Company ID or Booking ID: The node requires these IDs to be provided; missing or incorrect values will cause errors.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Server selection mismatch: Selecting the wrong server (US vs EU) may lead to failed requests if the booking does not exist on that server.
- API rate limits or downtime: If the Bookla API is unavailable or rate-limited, requests will fail; retry later or check API status.
Common error messages:
- 404 Not Found: The booking ID or company ID does not exist on the selected server.
- 401 Unauthorized: Invalid or missing API authentication token.
- 400 Bad Request: Malformed request parameters.
Resolving these usually involves verifying input parameters, credentials, and server selection.
Links and References
- Bookla API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding API calls
- RFC3339 date-time format reference: https://www.rfc-editor.org/rfc/rfc3339.html