Imobzi icon

Imobzi

Interagir com a API da Imobzi
Join our community

Actions62

Overview

This node interacts with the Imobzi API to retrieve multiple agenda items ("Agenda" resource) based on user-defined filters, ordering, limits, and offsets. It is useful for scenarios where you need to fetch a list of agenda entries from Imobzi, such as displaying upcoming appointments, filtering agendas by specific criteria, or integrating agenda data into workflows.

For example, you can use this node to:

  • Retrieve all agenda items starting with a certain title.
  • Get a paginated list of agenda entries ordered by date.
  • Filter agendas that contain specific keywords in their description.

Properties

Name Meaning
Filtros A collection of filter conditions to narrow down the results. Each filter includes:
- Campo Name or ID: The field of the agenda item to filter by (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.
Order By Field name to order the results by.
Limit Maximum number of agenda items to return. Minimum is 1. Default is 50.
Offset Number of agenda 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 agenda items retrieved from the Imobzi API. Each object corresponds to one agenda entry and contains its fields as returned by the API.

Example structure of each item in json output:

{
  "id": "string",
  "title": "string",
  "description": "string",
  "date": "string",
  ...
}

(Note: Actual fields depend on the Imobzi API response for agendas.)

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 API endpoints.
  • No additional external dependencies are required.

Troubleshooting

  • Unsupported Resource Error: If you select a resource not supported by the node, it will throw an error indicating the resource is unsupported. Ensure "Agenda" is selected for this operation.
  • Unsupported Operation Error: Selecting an operation other than "Get Many" (getAll) for the Agenda resource may cause errors if not implemented.
  • API Authentication Errors: If the API key or authentication token is invalid or missing, requests will fail. Verify credentials in n8n settings.
  • Invalid Filter Configuration: Filters must have valid field names, operators, and values. Incorrect filter setup may lead to empty results or API errors.
  • Rate Limits or API Downtime: Network issues or API rate limiting can cause request failures. Retry or check API status.

Links and References

Discussion