Inmobalia CRM icon

Inmobalia CRM

Interact with Inmobalia CRM API
Join our community

Actions47

Overview

The node interacts with the Inmobalia CRM API to list bookings associated with a specific property. It retrieves booking records filtered by the given property ID, optionally supporting pagination, sorting, and limiting the number of results returned.

This operation is useful in scenarios where you want to fetch all or a subset of bookings related to a particular property, for example:

  • Displaying upcoming or past bookings for a rental property.
  • Generating reports on bookings per property.
  • Integrating booking data into other workflows or systems based on property.

Properties

Name Meaning
Property ID The unique identifier (number) of the property for which to list bookings.
Return All Boolean flag indicating whether to return all matching bookings or limit the number of results returned.
Limit Maximum number of booking records to return if "Return All" is false. Minimum value is 1.
Filters Additional filtering options including:
  Page Page number for paginated results (minimum 0).
  Size Number of results per page (minimum 1, maximum 200).
  Sort Sorting criteria as a string, e.g., "createdDate,desc" to sort by creation date descending.

Output

The output is an array of JSON objects, each representing a booking record associated with the specified property. Each item contains detailed booking information as returned by the Inmobalia CRM API.

If the node supports binary data output for bookings (not indicated here), it would typically represent files or attachments related to bookings, but this operation focuses on JSON data only.

Dependencies

  • Requires an active connection to the Inmobalia CRM API via an OAuth2 API credential configured in n8n.
  • The node depends on the internal client library (createClient) to communicate with the API.
  • No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

  • Common Issues:

    • Missing or invalid Property ID will cause the API call to fail or return no results.
    • Exceeding API limits on page size or total results may result in errors or truncated data.
    • Incorrect sorting string format can lead to unexpected ordering or API errors.

  • Error Messages:

    • Unsupported operation: listByProperty — indicates the operation name was misspelled or not supported.
    • API errors wrapped as NodeApiError may indicate connectivity issues, invalid credentials, or request parameter problems.

  • Resolutions:

    • Ensure the Property ID is correctly provided and corresponds to an existing property.
    • Use valid pagination and sorting parameters within allowed ranges.
    • Verify that the API credentials are properly set up and have sufficient permissions.

Links and References

Discussion