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 retrieve multiple "Tarefa" (Task) records based on user-defined filters, ordering, limits, and offsets. It is useful for scenarios where you need to fetch a list of tasks from Imobzi, such as generating reports, syncing task data with other systems, or automating workflows that depend on task information.
For example, you can use this node to:
- Retrieve all tasks that start with a specific title.
- Get tasks containing certain keywords in their description.
- Fetch a limited number of tasks ordered by creation date.
- Skip a number of tasks to paginate through results.
Properties
| Name | Meaning |
|---|---|
| Filtros | A collection of filter conditions to narrow down the tasks returned. Each filter includes: - Campo Name or ID: The field of the task to filter by (loaded dynamically). - Operador: Comparison operator, options include: "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 (string). |
| Limit | Maximum number of results to return (number, minimum 1, default 50). |
| Offset | Number of items to skip before starting to collect the result set (number, minimum 0, default 0). |
Output
The node outputs an array of JSON objects under the json property, each representing a task retrieved from Imobzi. The structure corresponds directly to the task data returned by the Imobzi API, including fields like title, description, dates, and any other task attributes.
No binary data output is produced by this operation.
Example output snippet (simplified):
[
{
"json": {
"id": 123,
"title": "Follow up client",
"description": "Call client to discuss contract",
"due_date": "2024-07-01",
...
}
},
{
"json": {
"id": 124,
"title": "Prepare report",
"description": "Monthly sales report",
"due_date": "2024-07-05",
...
}
}
]
Dependencies
- Requires an active connection to the Imobzi API via an API key credential configured in n8n.
- The node uses authenticated HTTP requests to interact with Imobzi endpoints.
- No additional external dependencies are needed beyond the configured API authentication.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using unsupported resource or operation names will throw errors.
- Invalid filter fields or operators may result in empty responses or API errors.
- Exceeding API rate limits could cause request failures.
Error messages:
"Recurso \"tarefa\" não suportado!": Means the resource is not supported; ensure "Tarefa" is correctly selected."Operação \"getAll\" não suportada!": Means the operation is not supported; verify the operation choice.- API errors returned from Imobzi will be passed through; check the error message for details.
Resolution tips:
- Verify API credentials and permissions.
- Double-check filter field names and operators.
- Use smaller limits or add offsets to paginate large datasets.
- Enable "Continue On Fail" if partial data retrieval is acceptable.
Links and References
- Imobzi API Documentation (for detailed API endpoint info)
- n8n Expressions Documentation (for dynamic parameter values)
- n8n Node Development Guide