Actions47
- Booking Actions
- Contact Actions
- Enquiry Actions
- Event Actions
- Location Actions
- Property Actions
- Sale Actions
- User Actions
- Web Lead Actions
Overview
The node interacts with the Inmobalia CRM API to list booking records. It allows users to retrieve multiple bookings based on various filtering and sorting criteria. This is useful for scenarios such as generating reports, synchronizing booking data with other systems, or monitoring recent booking activity.
For example, a user might want to:
- Retrieve all bookings created within a specific date range.
- Fetch a limited number of recent bookings sorted by creation date.
- Paginate through bookings in batches for processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching booking results or only up to a specified limit. If set to true, all results are returned regardless of count. |
| Limit | The maximum number of booking results to return when "Return All" is false. Must be at least 1. |
| Filters | A collection of optional filters to refine the booking list: |
| - From Date Created | Start datetime filter for the booking creation date. Only bookings created on or after this date will be included. |
| - To Date Created | End datetime filter for the booking creation date. Only bookings created on or before this date will be included. |
| - From Date Modified | Start datetime filter for the last modification date of bookings. |
| - To Date Modified | End datetime filter for the last modification date of bookings. |
| - From Date Start | Start date filter for the booking start date (date part only). Bookings starting on or after this date are included. |
| - To Date Start | End date filter for the booking start date (date part only). Bookings starting on or before this date are included. |
| - From Date End | Start date filter for the booking end date (date part only). Bookings ending on or after this date are included. |
| - To Date End | End date filter for the booking end date (date part only). Bookings ending on or before this date are included. |
| - Page | Pagination page number (starting from 0). Used to fetch subsequent pages of results. |
| - Size | Number of results per page. Must be between 1 and 200. |
| - Sort | Sorting criteria in the format `"property,(asc |
Output
The output is an array of JSON objects, each representing a booking record retrieved from the Inmobalia CRM system. Each object contains detailed booking information as provided by the API, such as booking identifiers, dates, status, related property or contact references, and other relevant booking metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Inmobalia CRM API using OAuth2 authentication.
- The node depends on the n8n credential configured with appropriate API access rights.
- No additional external services or environment variables are required beyond the API credentials.
Troubleshooting
Common Issues:
- Incorrect or expired API credentials may cause authentication failures.
- Providing invalid date formats in filters can lead to API errors.
- Requesting too many results without pagination may result in timeouts or rate limiting.
Error Messages:
Unsupported operation— indicates that the selected operation is not implemented; ensure "List" is chosen under the Booking resource.- API errors wrapped as
NodeApiErrormay include messages about invalid parameters or permission issues; verify input values and API permissions.
Resolutions:
- Verify and refresh API credentials if authentication fails.
- Use valid ISO 8601 date-time strings for date filters.
- Use pagination (
PageandSize) or enableReturn Allcarefully to manage large datasets.
Links and References
- Inmobalia CRM API Documentation (example placeholder link)
- n8n OAuth2 Credential Setup Guide
- Working with Dates in APIs