Bookla icon

Bookla

Get data from Bookla's API

Actions12

Overview

The node integrates with the Bookla API to update a service entity within a specified company. It allows users to modify attributes of a service such as its name, color, and metadata. This is useful in scenarios where service details need to be changed dynamically, for example updating the service's display name or adjusting metadata that controls service behavior or categorization.

Practical examples include:

  • Renaming a service after rebranding.
  • Changing the color code used in a booking calendar UI.
  • Updating nested metadata fields to reflect new business rules or configurations.

Properties

Name Meaning
Server Select which Bookla server to connect to. Options: "US Server" or "EU Server".
Company ID The unique identifier of the company owning the service. Required to specify the context of the update.
Service ID The unique identifier of the service to update. Required to target the specific service.
Name New name for the service. Optional; if not provided, the name remains unchanged.
Color New color value for the service, typically used for UI representation. Optional.
Meta Data Object to update nested metadata fields of the service. Includes:
   Expected Version Number indicating the expected version of the metadata for concurrency control.
   Path String path specifying which part of the metadata object to update.
   Value JSON value to set at the specified metadata path. Can be any valid JSON structure.

Output

The node outputs the JSON response from the Bookla API representing the updated service object. This typically includes all current properties of the service after the update, such as its ID, name, color, metadata, and other relevant details.

No binary data output is involved.

Dependencies

  • Requires an API authentication token credential configured in n8n to authorize requests to the Bookla API.
  • The node dynamically constructs the base URL based on the selected server (US or EU).
  • The API expects JSON content type and returns JSON responses.

Troubleshooting

  • Invalid Company or Service ID: If the IDs are incorrect or do not exist, the API will return an error. Verify the IDs before running the node.
  • Metadata Update Errors: Providing an invalid JSON string in the metadata value or incorrect path may cause the update to fail. Ensure the JSON is well-formed and the path exists.
  • Version Conflicts: The expectedVersion field in metadata updates is used for optimistic concurrency control. If the version does not match the current metadata version, the update may be rejected. Retrieve the latest version before updating.
  • Authentication Failures: Missing or invalid API credentials will result in authorization errors. Confirm the API key/token is correctly set up in n8n.
  • Server Selection: Selecting the wrong server (US vs EU) can lead to connection issues or data inconsistency. Choose the correct server based on your account location.

Links and References

Discussion