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 sales records. It allows users to retrieve multiple sales entries based on various filtering and sorting criteria. This operation is useful for scenarios where you want to analyze, report, or process sales data from the CRM system in bulk.

Practical examples include:

  • Fetching all sales currently marked as "In Progress" to monitor ongoing deals.
  • Retrieving a limited number of recent sales filtered by creation or modification dates.
  • Sorting sales by creation date in descending order to get the latest sales first.

Properties

Name Meaning
Return All Whether to return all matching sales results or limit the output to a specified maximum number.
Limit The maximum number of sales records to return when not returning all.
Filters A collection of optional filters to refine the sales list:
- From Date Created Start date to filter sales created on or after this date.
- To Date Created End date to filter sales created on or before this date.
- From Date Modified Start date to filter sales modified on or after this date.
- To Date Modified End date to filter sales modified on or before this date.
- Page The page number for paginated results (starting at 0).
- Size Number of results per page (max 200).
- Sort Sorting criteria in the format `property,(asc
- Status Filter sales by status; options are: "In Progress", "Lost", or "Won".

Output

The node outputs an array of JSON objects, each representing a sale record retrieved from the Inmobalia CRM. Each object contains the full details of a sale as provided by the API.

If binary data were involved, it would be summarized here, but this operation only returns JSON data representing sales.

Dependencies

  • Requires an active connection to the Inmobalia CRM API using an OAuth2-based API key credential.
  • The node depends on the Inmobalia CRM API being accessible and properly authenticated.
  • No additional environment variables or external services are required beyond the configured API credentials.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or expired API credentials.
    • Request limits exceeded if too many records are requested without pagination.
    • Incorrect filter formats causing API errors.

  • Error messages:

    • "Unsupported operation: list" or "Unsupported resource: sales" indicate misconfiguration of the resource or operation parameters.
    • API errors returned by the CRM will be wrapped and surfaced as node errors; check the error message for details such as invalid filters or permission issues.

  • Resolutions:

    • Verify that the API credentials are valid and have necessary permissions.
    • Use pagination and limit settings to avoid large data requests.
    • Ensure filter values conform to expected formats (e.g., ISO date strings).

Links and References

Discussion