Bookla icon

Bookla

Get data from Bookla's API
Join our community

Actions12

Overview

This node integrates with the Bookla API to retrieve and manipulate data related to various entities such as services, resources, bookings, and clients within a company. Specifically, for the Resource resource with the Get Many operation, it fetches a list of resources associated with a specified company.

Common scenarios where this node is beneficial include:

  • Retrieving all available resources (e.g., rooms, equipment, personnel) for scheduling or management purposes.
  • Synchronizing resource data from Bookla into other systems.
  • Displaying resource lists in dashboards or reports.

Practical example:

  • A business wants to display all their available resources on their internal booking platform. Using this node with the Resource/Get Many operation, they can pull the current list of resources directly from Bookla.

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 resources you want to retrieve. (Required)
Resource ID The unique identifier of a specific resource. Required for single resource operations but not for Get Many.

Note: For the Get Many operation on Resource, only Server and Company ID are required inputs.

Output

The node outputs JSON data representing the list of resources retrieved from the Bookla API for the specified company. Each resource object typically contains details such as resource ID, name, color, metadata, and other relevant attributes defined by Bookla.

No binary data output is involved in this operation.

Example output structure (simplified):

[
  {
    "id": "resource_123",
    "name": "Conference Room A",
    "color": "#FF0000",
    "metaData": { ... }
  },
  {
    "id": "resource_456",
    "name": "Projector",
    "color": "#00FF00",
    "metaData": { ... }
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Bookla API.
  • The node dynamically sets the base URL depending on the selected server (US or EU).
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Missing or invalid Company ID: The API will fail if the company ID is not provided or incorrect. Ensure the company ID is valid and correctly entered.
  • Authentication errors: If the API key credential is missing or invalid, the request will be unauthorized. Verify that the API key is correctly configured in n8n credentials.
  • Server selection mismatch: Selecting the wrong server (US vs EU) may cause connection issues or empty results if the company exists only on one server.
  • Empty results: If no resources are returned, confirm that the company has resources set up in Bookla and that the correct company ID and server are used.

Links and References

Discussion