Bookla icon

Bookla

Get data from Bookla's API

Actions12

Overview

This node integrates with the Bookla API to retrieve booking data from a specified company on either the US or EU Bookla server. The "Get Many" operation under the "Booking" resource fetches a list of bookings filtered by various criteria such as date range, resource IDs, service IDs, and client ID. This is useful for scenarios where you want to analyze, report, or synchronize multiple booking records from Bookla into your workflow.

Practical examples include:

  • Retrieving all bookings within a specific date range to generate daily or weekly reports.
  • Filtering bookings by particular resources or services to monitor utilization.
  • Fetching bookings associated with a specific client for customer management or follow-up.

Properties

Name Meaning
Server Select which Bookla server to connect to: US Server or EU Server
Company ID Identifier of the company whose bookings are being retrieved (required)
From Date Start date and time (RFC3339 format) to filter bookings from
To Date End date and time (RFC3339 format) to filter bookings up to
Limit Maximum number of booking results to return (pagination limit)
Offset Number of bookings to skip before starting to collect results (pagination offset)
Resource IDs Filter bookings by one or more resource IDs
Service IDs Filter bookings by one or more service IDs
Client ID Filter bookings by a specific client ID

Output

The node outputs JSON data representing an array of booking objects retrieved from the Bookla API. Each booking object contains details about individual bookings such as booking identifiers, times, associated resources, services, clients, status, and other metadata as provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Bookla API.
  • The node dynamically constructs the base URL depending on the selected server (US or EU).
  • Proper configuration of the "Company ID" is mandatory to target the correct company data in Bookla.

Troubleshooting

  • Missing or invalid Company ID: The API will fail if the company identifier is not provided or incorrect. Ensure the Company ID is accurate and corresponds to your Bookla account.
  • Invalid date formats: The "From Date" and "To Date" must be valid RFC3339 datetime strings. Incorrect formatting may cause request failures.
  • Pagination issues: Setting very high limits or offsets beyond available data may result in empty responses.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Filtering parameters: If filters like Resource IDs, Service IDs, or Client ID do not match any records, the response will be empty but not necessarily an error.

Links and References

Discussion