Bookla icon

Bookla

Get data from Bookla's API

Actions12

Overview

This node integrates with the Bookla API to retrieve and manage data related to various entities such as services, resources, bookings, and clients within a company. Specifically, for the Resource - Get operation, it fetches detailed information about a single resource identified by its Resource ID within a specified company.

Typical use cases include:

  • Retrieving details of a specific resource (e.g., a room, equipment, or staff member) to display or process in workflows.
  • Integrating resource data into scheduling, booking, or reporting automations.
  • Synchronizing resource information between Bookla and other systems.

Example: A workflow that triggers when a new booking is made might use this node to get detailed info about the booked resource to send customized notifications or update calendars.

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 resource data you want to access.
Resource ID The unique identifier of the resource to retrieve information for.

Output

The node outputs JSON data representing the resource's details as returned by the Bookla API. This typically includes fields such as resource name, color, metadata, and other attributes defined in Bookla for that resource.

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 based on the selected server (US or EU).
  • Proper configuration of the "Server" property is necessary to target the correct regional API endpoint.

Troubleshooting

  • Missing or invalid Company ID or Resource ID: The API call will fail if these required parameters are empty or incorrect. Ensure they are correctly set.
  • Authentication errors: If the API key credential is missing or invalid, the request will be unauthorized. Verify the API key setup.
  • Incorrect server selection: Selecting the wrong server (US vs EU) may cause connection issues or data not found errors. Confirm the server matches your Bookla account region.
  • API rate limits or downtime: Temporary failures may occur due to API limits or service outages. Retry after some time or check Bookla status.

Common error messages:

  • 404 Not Found: The specified resource or company does not exist or the IDs are incorrect.
  • 401 Unauthorized: Authentication failed due to missing or invalid API credentials.
  • 400 Bad Request: Invalid parameter format or missing required parameters.

Links and References

Discussion