Actions62
- Lead Actions
- Account Actions
- Agenda Actions
- Contact Actions
- Contrato Actions
- Documento Actions
- Evento Actions
- Financeiro Actions
- Imovel Actions
- Integracao Actions
- Locacao Actions
- Tarefa Actions
- Usuario Actions
Overview
This node integrates with the Imobzi API to manage "Usuario" (User) resources, specifically supporting the "Get Many" operation. It allows users to retrieve multiple user records from Imobzi with flexible filtering, ordering, pagination, and offset options.
Common scenarios where this node is beneficial include:
- Fetching a list of users matching specific criteria for reporting or synchronization.
- Retrieving paginated user data to process in batches.
- Filtering users by various fields such as name, ID, or other user attributes.
For example, you can use this node to get all users whose names start with "Jo", order them by creation date, limit results to 100, and skip the first 50 entries.
Properties
| Name | Meaning |
|---|---|
| Filtros | A collection of filter conditions to narrow down the user list. Each condition includes: - Campo Name or ID: The user field to filter on (loaded dynamically). - Operador: Comparison operator: • Começa Com (starts_with) • Contém (contains) • Diferente (neq) • Igual (eq) • Maior Ou Igual (gte) • Maior Que (gt) • Menor Ou Igual (lte) • Menor Que (lt) • Não Contém (not_contains) • Termina Com (ends_with) - Valor: The value to compare against. Multiple filters can be added. |
| Order By | Field name to order the results by. |
| Limit | Maximum number of user records to return. Minimum value is 1. Default is 50. |
| Offset | Number of user records to skip before starting to collect the result set. Minimum value is 0. Default is 0. |
Output
The node outputs an array of JSON objects under the json property, each representing a user record retrieved from the Imobzi API. The structure of each user object corresponds directly to the fields provided by the Imobzi "users" endpoint.
Example output snippet:
[
{
"json": {
"id": 123,
"name": "John Doe",
"email": "john.doe@example.com",
"created_at": "2023-01-01T12:00:00Z",
...
}
},
{
"json": {
"id": 124,
"name": "Jane Smith",
"email": "jane.smith@example.com",
"created_at": "2023-01-02T08:30:00Z",
...
}
}
]
No binary data is output by this node.
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 beyond the configured API authentication.
Troubleshooting
- Unsupported Resource Error: If the resource parameter is not "usuario" or another supported resource, the node will throw an error indicating the resource is unsupported. Ensure the resource is correctly set to "usuario".
- Operation Not Supported: If an unsupported operation is selected, the node throws an error. For "usuario", only supported operations should be used.
- API Authentication Failures: Errors related to authentication usually indicate missing or invalid API credentials. Verify that the API key credential is properly configured and has necessary permissions.
- Invalid Filter Fields: Using a filter field that does not exist on the user resource may cause the API to return errors or empty results. Use the dynamic field loader to select valid fields.
- Rate Limits or Network Issues: If the API returns rate limit errors or network timeouts, consider adding retry logic or increasing limits in your workflow.
Links and References
- Imobzi API Documentation (official API docs for reference)
- n8n Expressions Documentation (for using expressions in property values)
- n8n Credential Setup (how to configure API credentials in n8n)