Imobzi icon

Imobzi

Interagir com a API da Imobzi
Join our community

Actions62

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 Documento resource with the Get operation, it retrieves a single document item by its ID or name.

Common scenarios where this node is beneficial include:

  • Fetching detailed information about a specific document stored in Imobzi.
  • Automating workflows that require document metadata retrieval before further processing.
  • Integrating document data into other systems or reports.

Practical example:

  • You want to retrieve a contract document's details by selecting it from a list or specifying its ID dynamically, then use that data downstream in your workflow for validation or notification purposes.

Properties

Name Meaning
Document Name or ID Select a document from a dropdown list loaded dynamically from Imobzi, or specify an ID via expression. This identifies which document to retrieve.

Output

The node outputs the retrieved document data in the json field of the output item. The structure corresponds directly to the document object returned by the Imobzi API, containing all available fields and metadata for the specified document.

No binary data output is indicated for this operation.

Example output JSON snippet (structure depends on Imobzi API response):

{
  "id": "123",
  "filename": "contract.pdf",
  "uploadDate": "2023-01-15T12:34:56Z",
  "size": 204800,
  "mimeType": "application/pdf",
  // ... other document metadata fields
}

Dependencies

  • Requires an active connection to the Imobzi API using an API key credential configured in n8n.
  • The node uses authenticated HTTP requests to interact with Imobzi endpoints.
  • No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

  • Error: Resource not supported!
    This occurs if an unsupported resource name is provided. Ensure the resource parameter is set correctly to "documento" for documents.

  • Error: Operation not supported!
    Happens when an invalid operation is selected. For getting a document, ensure the operation is set to "get".

  • Error related to missing or invalid ID
    The document ID or name must be provided and valid. If the dropdown does not load options, check API connectivity and credentials.

  • API request failures
    Could be due to network issues, invalid credentials, or API limits. Verify API key validity and network access.

  • To handle errors gracefully, enable "Continue On Fail" in the node settings to allow workflow continuation despite individual item errors.

Links and References

Discussion