Bookla icon

Bookla

Get data from Bookla's API
Join our community

Actions12

Overview

The node integrates with the Bookla API to retrieve available booking times for a specific service within a company. It is designed to query time slots that can be booked, considering various constraints such as date range, duration, number of spots, resources involved, and ticket quantities.

This node is beneficial in scenarios where you want to automate or integrate booking availability checks into workflows, such as:

  • Displaying available appointment times on a website or app.
  • Automating scheduling processes by checking open slots before creating bookings.
  • Integrating with calendar systems to sync available service times.

For example, you could use this node to fetch all available times for a yoga class service between two dates, specifying the number of spots needed and filtering by particular instructors (resources).

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 in Bookla under which the service exists. Required.
Service ID The unique identifier of the service for which to get available times. Required.
From Start of the time range to check availability, in RFC3339 datetime format. Required.
To End of the time range to check availability, in RFC3339 datetime format. Required.
Duration Duration of the desired booking slot in ISO8601 duration format (e.g., PT1H for one hour). Required for flexible services that allow variable durations.
Spots Number of spots to book simultaneously. Required for group services where multiple spots can be reserved at once. Defaults to 1.
Resource IDs List of resource IDs to filter availability by specific resources (e.g., staff members or rooms). Multiple values allowed.
Tickets Key-value pairs representing ticket IDs and their quantities. Required for services that require tickets. Allows specifying multiple tickets with their respective quantities.

Output

The node outputs JSON data containing the available times for the specified service within the given parameters. The structure typically includes an array of available time slots, each describing start and end times and possibly additional metadata about availability.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Bookla API.
  • Needs network access to the selected Bookla server endpoint (us.bookla.com or eu.bookla.com).
  • The node uses HTTP POST requests to the Bookla API's /v1/companies/{company_id}/services/{service_id}/times endpoint.

Troubleshooting

  • Missing or invalid Company ID or Service ID: The API will fail if these identifiers are incorrect or missing. Ensure they are correctly set.
  • Invalid date formats: The From and To properties must be valid RFC3339 datetime strings. Incorrect formatting may cause errors.
  • Duration required for flexible services: If the service supports flexible durations, omitting the Duration property may result in errors or empty results.
  • Insufficient spots or tickets: For group or ticket-based services, ensure the Spots and Tickets fields are correctly populated; otherwise, availability might not be returned.
  • API authentication errors: Verify that the API key credential is valid and has necessary permissions.
  • Server selection mismatch: Choose the correct server region matching your company's location to avoid connectivity issues.

Links and References

Discussion