Imobzi icon

Imobzi

Interagir com a API da Imobzi

Overview

This node integrates with the Imobzi API to manage real estate-related data. Specifically, for the Lead resource and the Get operation, it retrieves detailed information about a single lead by its name or ID. This is useful in scenarios where you want to fetch up-to-date lead details from your Imobzi account within an automated workflow.

Practical examples:

  • Automatically retrieving lead details when a new inquiry is received.
  • Enriching CRM records with lead information stored in Imobzi.
  • Triggering follow-up actions based on specific lead data fetched dynamically.

Properties

Name Meaning
Lead Name or ID Select a lead from a dropdown list loaded dynamically from Imobzi, or specify a lead ID manually using an expression. This identifies which lead to retrieve.

Output

The node outputs a JSON object containing the lead's data as returned by the Imobzi API. The structure corresponds directly to the lead resource fields in Imobzi, including all available properties of that lead.

Example output snippet (simplified):

{
  "id": 123,
  "name": "John Doe",
  "email": "john.doe@example.com",
  "phone": "+5511999999999",
  ...
}

No binary data output is produced by this operation.

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 REST endpoints.
  • No additional external dependencies beyond the Imobzi API and n8n's HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Specifying a non-existent lead ID will result in an error or empty response.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "Resource 'lead' not supported!" — indicates an internal misconfiguration; ensure the resource parameter is correctly set.
    • "Operation 'get' not supported!" — indicates an unsupported operation; verify the operation parameter.
    • API errors from Imobzi (e.g., 404 Not Found) typically mean the specified lead does not exist.
  • Resolutions:

    • Verify and reconfigure the API key credential.
    • Confirm the lead ID exists in Imobzi before running the node.
    • Check network access and proxy settings if applicable.
    • Use expressions carefully to ensure valid IDs are passed.

Links and References

Discussion