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 such as leads, properties, contacts, contracts, financial accounts, rentals, documents, tasks, agendas, events, integrations, users, and account information. Specifically, the "Get Many" operation retrieves multiple items from a selected resource, supporting filtering, ordering, pagination (limit and offset).
Common scenarios where this node is beneficial include:
- Fetching lists of leads or contacts for marketing or CRM workflows.
- Retrieving property or rental data for real estate management automation.
- Accessing financial accounts or contracts for accounting or legal processes.
- Gathering tasks, events, or agendas for scheduling and task management.
Practical example:
- Retrieve up to 50 leads starting from the 10th record, ordered by creation date, filtered by name containing "John".
Properties
| Name | Meaning |
|---|---|
| Order By | Field 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). |
These properties are used to control the pagination and sorting of the retrieved list of items.
Additionally, the node supports complex filters (not listed here in detail) allowing users to specify multiple filter conditions on fields with operators like equals, contains, starts with, greater than, etc., tailored per resource.
Output
The output is an array of JSON objects representing the retrieved items from the Imobzi API. Each item corresponds to one entity from the selected resource.
- The
jsonfield contains the data object(s) returned by the API. - The structure of each item depends on the resource queried (e.g., lead, property, contact).
- No binary data output is produced by this node.
Example output snippet (simplified):
[
{
"json": {
"id": 123,
"name": "John Doe",
"email": "john@example.com",
...
}
},
{
"json": {
"id": 124,
"name": "Jane Smith",
"email": "jane@example.com",
...
}
}
]
Dependencies
- Requires an API key credential for authenticating requests to the Imobzi API.
- The node uses n8n's built-in HTTP request helper with authentication to communicate with the Imobzi REST endpoints.
- No additional external dependencies beyond the configured API credential.
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 the resource value matches one of the predefined options.
- Unsupported Operation Error: Selecting an operation other than create, get, getAll, update, or delete will cause an error. Use only supported operations.
- API Request Failures: Network issues, invalid credentials, or API limits may cause request failures. Check your API key configuration and network connectivity.
- Filter Misconfiguration: Incorrect filter fields or operators may result in no data or errors. Verify that filter fields exist on the resource and operators are valid.
- Limit and Offset Values: Setting limit below 1 or offset below 0 is invalid; ensure these values respect their minimum constraints.
To resolve errors, verify input parameters, credentials, and API availability.
Links and References
- Imobzi API Documentation (Assumed official API docs URL)
- n8n Documentation - Creating Nodes
- n8n Expressions Guide (for dynamic parameter usage)
If you need details about other operations or resources, feel free to ask!