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 events stored in the system. It retrieves multiple event records based on user-defined filters and pagination options. This operation is useful for workflows that need to process or analyze event data, such as generating reports, syncing events with other systems, or triggering actions based on event attributes.

For example, a user might want to fetch all events within a specific date range or sort them by creation date to display recent activities in a dashboard.

Properties

Name Meaning
Return All Whether to return all matching event results or limit the number of returned items.
Limit Maximum number of event results to return when "Return All" is false (minimum 1).
Filters Collection of optional filters to refine the event list:
- From End Filter events starting from this end datetime.
- From Start Filter events starting from this start datetime.
- 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
- To End Filter events up to this end datetime.
- To Start Filter events up to this start datetime.

Output

The output is an array of JSON objects, each representing an event retrieved from the Inmobalia CRM. Each object contains the event's data fields as provided by the API. The exact structure depends on the CRM's event schema but typically includes identifiers, timestamps, descriptions, and related metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Inmobalia CRM API using an OAuth2-based API key credential.
  • The node depends on the createClient function to instantiate the API client.
  • Proper configuration of the API credentials in n8n is necessary for authentication.

Troubleshooting

  • Unsupported Operation Error: If an unsupported operation is selected, the node throws an error indicating the operation is not supported. Ensure "List" is selected under the "Event" resource.
  • API Authentication Errors: Failure to authenticate with the CRM API will result in errors. Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid Filter Values: Providing invalid dates or out-of-range pagination values may cause the API to reject the request. Double-check filter inputs for correctness.
  • Rate Limits or Network Issues: Temporary network failures or API rate limits can cause errors. Retry after some time or check network connectivity.

Links and References

Discussion