Actions12
Overview
This node integrates with the Bookla API to retrieve and manipulate data related to various business entities such as services, resources, bookings, and clients. Specifically, for the Service - Get operation, it fetches detailed information about a single service offered by a company on the Bookla platform.
Typical use cases include:
- Retrieving detailed information about a specific service to display or process in workflows.
- Integrating service data into other systems for reporting or automation.
- Validating service details before creating bookings or managing resources.
For example, a user might want to get the details of a haircut service (service ID) from their US-based Bookla account (company ID) to show availability or pricing in a custom booking system.
Properties
| Name | Meaning |
|---|---|
| Server | Select which Bookla server to connect to. Options: "US Server", "EU Server". |
| Company ID | The unique identifier of the company in Bookla whose service data is being accessed. |
| Service ID | The unique identifier of the specific service to retrieve information for. |
Output
The node outputs JSON data representing the service details retrieved from the Bookla API. This typically includes all relevant fields describing the service such as its name, description, pricing, duration, metadata, and any other attributes provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to 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 within n8n is necessary for successful communication.
Troubleshooting
Common issues:
- Invalid or missing Company ID or Service ID will result in errors or empty responses.
- Incorrect API credentials or expired tokens will cause authentication failures.
- Selecting the wrong server region may lead to connection errors or data not found.
Error messages:
- 401 Unauthorized: Check that the API key credential is correctly configured and valid.
- 404 Not Found: Verify that the Company ID and Service ID are correct and exist on the selected server.
- Network errors: Ensure network connectivity and that the Bookla API endpoint is reachable.
Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming server selection.
Links and References
- Bookla API Documentation (hypothetical link for reference)
- n8n documentation on API Credentials