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 perform various operations on different resources within the Imobzi platform. Specifically, for the Integracao resource with the Get Many operation, it retrieves multiple integration records from Imobzi. Users can apply filters, sorting, pagination (limit and offset) to customize the data retrieval.
Typical use cases include:
- Fetching a list of integrations configured in Imobzi for reporting or synchronization.
- Filtering integrations by specific fields such as name or ID.
- Paginating through large sets of integration data.
- Ordering results by a chosen field.
For example, you might use this node to get all integrations whose names start with "Sales" and limit the result to 20 items, ordered by creation date.
Properties
| Name | Meaning |
|---|---|
| Filtros | A collection of filter conditions to narrow down the returned integrations. Each filter includes: - Campo Name or ID: The field to filter by (loaded dynamically from integration fields). - Operador: Comparison operator, options are: "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. |
| Order By | Field name to order the results by. |
| Limit | Maximum number of results to return. Minimum is 1. Default is 50. |
| Offset | Number of items to skip before starting to collect the result set. Minimum is 0. Default is 0. |
Output
The output is an array of JSON objects representing the retrieved integration records. Each item corresponds to one integration entry as returned by the Imobzi API under the /integrations endpoint.
- The
jsonproperty contains the integration data fields. - No binary data output is produced by this operation.
Example output snippet (simplified):
[
{
"json": {
"id": 123,
"name": "Integration Example",
"description": "Description of the integration",
...
}
},
...
]
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 beyond the Imobzi API and n8n's HTTP request helper.
Troubleshooting
- Unsupported Resource Error: If the resource parameter is not recognized, the node throws an error indicating the resource is unsupported. Ensure the resource is correctly set to "integracao" for this operation.
- Unsupported Operation Error: If an invalid operation is selected, the node will throw an error. Use only supported operations like "getAll" for fetching many items.
- API Authentication Failures: Errors related to authentication usually indicate missing or invalid API credentials. Verify that the API key credential is properly configured.
- Empty Results: If no data is returned, check your filter conditions and pagination parameters to ensure they match existing data.
- Rate Limits or Network Issues: The node relies on network connectivity and API availability. Temporary failures may occur due to rate limits or connectivity problems; retry or check API status if needed.
Links and References
- Imobzi API Documentation (official API docs, for detailed endpoint info)
- n8n Expressions Documentation (for using expressions in property values)
- n8n HTTP Request Node (underlying mechanism for API calls)
This summary focuses on the Integracao resource with the Get Many operation, describing how to retrieve multiple integration records with filtering, ordering, and pagination support.