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, and users. Specifically, for the Agenda resource with the Get operation, it retrieves a single agenda item by its name or ID.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a specific agenda entry in your real estate management system.
- Automating workflows that require agenda data retrieval, such as syncing calendar events or reminders.
- Integrating agenda data into other systems or reports.
Example: You want to get details of an agenda item titled "Monthly Meeting" or identified by a specific ID to use in a follow-up email or notification.
Properties
| Name | Meaning |
|---|---|
| Agenda Name or ID | Select an agenda from the dropdown list or specify its ID using an expression. This identifies which agenda item to retrieve. |
The property uses a dynamic options loader (getAgendas) to populate the list of available agendas.
Output
The node outputs the retrieved agenda item data in the json field of the output. The structure corresponds directly to the Imobzi API response for an agenda item, typically including fields like title, date, description, and any other agenda-specific attributes.
No binary data output is produced by this operation.
Example output JSON snippet:
{
"id": "123",
"title": "Monthly Meeting",
"date": "2024-06-15T10:00:00Z",
"description": "Discuss monthly targets and progress"
}
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 the Imobzi REST endpoints.
- No additional external dependencies are required beyond the configured API authentication.
Troubleshooting
Error: Resource "agenda" not supported!
This indicates an invalid resource selection; ensure "Agenda" is selected as the resource.Error: Operation "get" not supported!
This means the operation is not recognized; verify that "Get" is chosen as the operation.API Authentication Errors
If the node fails due to authentication issues, check that the API key credential is correctly set up and has sufficient permissions.Invalid ID or Agenda Not Found
If the specified agenda ID does not exist, the API will return an error. Confirm the ID is correct or select from the provided list.Continue On Fail Behavior
If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- Imobzi API Documentation (general reference for API endpoints and data structures)
- n8n Expressions Documentation (for using expressions in property fields)