Imobzi icon

Imobzi

Interagir com a API da Imobzi
Join our community

Actions62

Overview

This node interacts with the Imobzi API to retrieve multiple contact records based on specified filters, ordering, limits, and offsets. It is useful for scenarios where you need to fetch a list of contacts from your Imobzi account, optionally filtered by certain fields and sorted or paginated.

Practical examples include:

  • Retrieving all contacts whose name starts with "John".
  • Fetching a limited number of contacts ordered by creation date.
  • Skipping a number of contacts to paginate through large datasets.

Properties

Name Meaning
Filtros A collection of filter conditions to apply when retrieving contacts. Each condition includes:
- Campo Name or ID: The contact field to filter by (loaded dynamically from available contact fields).
- Operador: Comparison operator such as "Starts With", "Contains", "Equals", "Not Equals", "Greater Than", etc.
- Valor: The value to compare the field against.
Order By Field name to order the results by.
Limit Maximum number of contact records to return. Minimum value is 1. Default is 50.
Offset Number of contact records to skip before starting to collect the result set. Useful for pagination. Minimum value is 0.

Output

The output is an array of JSON objects representing the retrieved contacts. Each object corresponds to one contact record as returned by the Imobzi API. The structure of each contact object depends on the fields defined in your Imobzi account.

Example output snippet:

[
  {
    "id": 123,
    "name": "John Doe",
    "email": "john.doe@example.com",
    "phone": "123456789"
    // other contact fields...
  },
  {
    "id": 124,
    "name": "Jane Smith",
    "email": "jane.smith@example.com",
    "phone": "987654321"
    // other contact fields...
  }
]

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Imobzi API via an API key credential configured in n8n.
  • The node uses authenticated HTTP requests to the Imobzi REST endpoints.
  • No additional external dependencies are required.

Troubleshooting

  • Error: Resource "contact" not supported!
    This indicates an invalid resource parameter. Ensure the resource is set exactly to "contact".

  • Error: Operation "getAll" not supported!
    Indicates an unsupported operation. Confirm that the operation is set to "Get Many" (internally "getAll").

  • API Authentication Errors
    If authentication fails, verify that the API key credential is correctly configured and has sufficient permissions.

  • Empty Results
    If no contacts are returned, check your filter conditions and ensure they match existing data.

  • Invalid Filter Fields or Operators
    Filters must use valid contact fields and supported operators. Use the dynamic options provided in the node UI to select valid fields.

Links and References

Discussion