Inmobalia CRM icon

Inmobalia CRM

Interact with Inmobalia CRM API
Join our community

Actions47

Overview

This node interacts with the Inmobalia CRM API to list bookings associated with a specific contact. It is useful in scenarios where you want to retrieve all or a subset of booking records linked to a particular contact ID, such as for customer management, reporting, or integration workflows.

For example, a real estate agent could use this node to fetch all property bookings made by a client to review their history or follow up on pending transactions.

Properties

Name Meaning
Contact ID The unique identifier (number) of the contact whose bookings you want to list. This is required.
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 Optional filters to refine the results:
- Page Page number for paginated results (minimum 0).
- Size Number of results per page (minimum 1, maximum 200).
- Sort Sorting criteria in the format `"property,(asc

Output

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

If multiple bookings are found, each will be a separate JSON object in the output array.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Inmobalia CRM API.
  • Requires an API authentication token configured via OAuth2 credentials in n8n.
  • No additional environment variables are needed beyond standard n8n credential setup.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Contact ID will result in no bookings being returned or an error from the API.
    • Exceeding API rate limits may cause errors; ensure your API usage complies with Inmobalia CRM's limits.
    • Incorrect sorting syntax in the "Sort" filter can lead to API errors.

  • Error messages:

    • Unsupported operation: listByContact — indicates the operation name was misspelled or not supported.
    • API errors wrapped as NodeApiError may indicate connectivity issues, invalid credentials, or malformed requests.

  • Resolutions:

    • Verify the Contact ID exists in the CRM.
    • Check and correct the "Sort" parameter format.
    • Ensure OAuth2 credentials are valid and have necessary permissions.
    • Handle pagination properly when retrieving large datasets.

Links and References

Discussion