Bookla icon

Bookla

Get data from Bookla's API

Actions12

Overview

The node integrates with the Bookla API to retrieve multiple service records for a specified company. It is designed to fetch a list of services associated with a given company ID from either the US or EU Bookla server. This operation is useful when you want to display, process, or analyze all available services in a company’s account.

Common scenarios:

  • Synchronizing all services from Bookla into another system.
  • Displaying a catalog of services for booking or management purposes.
  • Automating workflows that require bulk access to service data.

Example use case:
A business wants to pull all their services from Bookla to update their internal CRM or website listings automatically. Using this node, they can fetch all services and then trigger further actions like filtering or updating other systems.

Properties

Name Meaning
Server Select which Bookla server to connect to. Options: "US Server", "EU Server".
Company ID The unique identifier of the company whose services you want to retrieve (required).

Output

The node outputs JSON data representing an array of service objects retrieved from the Bookla API for the specified company. Each item in the output corresponds to a service with its details as provided by the API.

  • The json output field contains the full response data of the services list.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Bookla API.
  • The node dynamically constructs the base URL based on the selected server (us.bookla.com or eu.bookla.com).
  • Proper configuration of the API key credential in n8n is necessary for successful API calls.

Troubleshooting

  • Missing or invalid Company ID: The node requires a valid company ID; ensure it is correctly set and not empty.
  • Authentication errors: If the API key credential is missing or incorrect, the API will reject requests. Verify the API key setup.
  • Server selection mismatch: Selecting the wrong server (US vs EU) may lead to no data or errors if the company exists only on one server.
  • API rate limits or downtime: The Bookla API might throttle requests or be temporarily unavailable; handle such errors gracefully.
  • Unexpected response structure: If the API changes, the node output might differ; verify API documentation for updates.

Links and References

Discussion