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 enquiries. It retrieves a collection of enquiry records based on specified filters and pagination options. This operation is useful for users who want to fetch multiple enquiry entries from their CRM system, for example, to analyze customer interest, track sales leads, or integrate enquiry data into other workflows.

Practical examples include:

  • Fetching all enquiries created within a specific date range.
  • Retrieving enquiries filtered by status (e.g., Active, Lost, Won).
  • Sorting enquiries by creation date or modification date.
  • Limiting the number of enquiries returned for performance or display purposes.

Properties

Name Meaning
Return All Whether to return all matching enquiries or only up to a specified limit.
Limit The maximum number of enquiry results to return when "Return All" is set to false. Minimum value is 1.
Filters A collection of optional filters to refine the enquiry list:
- From Date Created Start date/time to filter enquiries created on or after this date.
- To Date Created End date/time to filter enquiries created on or before this date.
- From Date Modified Start date/time to filter enquiries modified on or after this date.
- To Date Modified End date/time to filter enquiries modified on or before this date.
- Page The page number of results to retrieve (zero-based). Useful for pagination. Minimum value is 0.
- Size Number of enquiries per page to retrieve. Must be between 1 and 200.
- Sort Sorting criteria in the format `"property,(asc
- Status Filter enquiries by one or more statuses. Options are: Active, Lost, Won.
- Transaction Type Filter enquiries by transaction type. Options are: Rent (Long Term), Rent (Short Term), Sale. Default is Sale.

Output

The output is an array of JSON objects, each representing an enquiry record retrieved from the Inmobalia CRM. Each object contains the full details of an enquiry as provided by the API, including fields such as enquiry ID, status, creation/modification dates, transaction type, and any other relevant enquiry information.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Inmobalia CRM API.
  • Requires an API authentication token configured via OAuth2 credentials in n8n.
  • No additional external dependencies beyond the Inmobalia CRM API client bundled with the node.

Troubleshooting

  • Unsupported Operation or Resource Errors: If you select an unsupported operation or resource, the node will throw an error indicating the unsupported action. Ensure that the resource is set to "Enquiry" and operation to "List".
  • API Authentication Failures: Errors related to authentication usually indicate missing or invalid API credentials. Verify that the OAuth2 credential is correctly configured and authorized.
  • Invalid Filter Values: Providing invalid dates, page numbers, or sizes outside allowed ranges may cause errors or unexpected results. Double-check input values conform to expected formats and limits.
  • Empty Results: If no enquiries match the filters, the output will be an empty array. Adjust filters or remove restrictive criteria to retrieve data.
  • Rate Limits or API Downtime: Temporary API issues can cause request failures. Retry after some time or check the Inmobalia CRM service status.

Links and References

Discussion