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 web leads. It retrieves a collection of web lead records from the CRM system, optionally filtered and sorted according to user-defined criteria. This operation is useful for scenarios where you want to fetch multiple web lead entries for further processing, reporting, or integration with other systems.

Practical examples include:

  • Extracting all pending web leads created within a specific date range.
  • Retrieving a limited number of processed web leads sorted by creation date.
  • Paginating through web leads in batches for bulk data synchronization.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit (boolean).
Limit Maximum number of results to return when "Return All" is false (number, minimum 1).
Filters Collection of optional filters to refine the list of web leads:
- From Date Start date/time to filter web leads created after this timestamp.
- To Date End date/time to filter web leads created before this timestamp.
- Page Page number for pagination (starting at 0).
- Size Number of results per page (minimum 1, maximum 200).
- Sort Sorting criteria as a string in the format `"property,(asc
- Status Filter by status of the web lead; options are "Pending" or "Processed".

Output

The output is an array of JSON objects, each representing a web lead record retrieved from the Inmobalia CRM. Each item contains the full details of a single web lead as returned by the API.

The structure of each web lead JSON object depends on the CRM's API response but typically includes fields such as identifiers, contact information, status, timestamps, and any custom data associated with the lead.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Inmobalia CRM API using OAuth2 authentication.
  • The node expects valid credentials configured in n8n to authenticate API requests.
  • Network connectivity to the Inmobalia CRM service endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or expired API tokens.
    • Exceeding API rate limits imposed by the CRM service.
    • Providing invalid filter values, such as incorrect date formats or out-of-range pagination parameters.
    • Requesting more results than allowed by the API (e.g., size > 200).

  • Error Messages:

    • Unsupported operation or Unsupported resource: Indicates that the selected operation or resource is not implemented or recognized by the node.
    • API errors wrapped as NodeApiError: These usually contain the original error message from the CRM API, which can indicate issues like permission denied, invalid parameters, or server errors.

  • Resolutions:

    • Verify and refresh API credentials if authentication errors occur.
    • Adjust filter parameters to comply with API constraints.
    • Use pagination properly to avoid requesting too many records at once.
    • Check the node configuration to ensure the correct resource ("Web Lead") and operation ("List") are selected.

Links and References

Discussion