Imobzi icon

Imobzi

Interagir com a API da Imobzi

Overview

This node integrates with the Imobzi API to manage various resources such as leads, properties, contacts, contracts, and more. Specifically for the Lead - Delete operation, it allows users to delete a lead record from their Imobzi account by specifying the lead's name or ID.

Common scenarios where this node is beneficial include:

  • Automating cleanup of outdated or invalid leads.
  • Integrating lead management workflows where leads are removed after certain conditions are met.
  • Synchronizing lead data between Imobzi and other systems by deleting leads that no longer exist elsewhere.

Example use case:

  • After qualifying leads in a CRM, automatically delete those that do not meet criteria using this node to keep the lead database clean.

Properties

Name Meaning
Lead Name or ID Select a lead from a dynamically loaded list or specify a lead ID directly (supports expressions). This identifies which lead to delete.

Output

The node outputs a JSON object representing the response from the Imobzi API after attempting to delete the lead. The structure typically contains a data field with details about the deletion result or confirmation.

If the deletion is successful, the output JSON will contain relevant information confirming the removal of the lead. If an error occurs, the output may contain an error message describing the issue.

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 interact with the Imobzi REST endpoints.
  • No additional external dependencies beyond the Imobzi API and its authentication.

Troubleshooting

  • Common issues:

    • Specifying an invalid or non-existent lead ID will cause the API to return an error.
    • Network connectivity problems can prevent the node from reaching the Imobzi API.
    • Insufficient permissions on the API key may block deletion operations.
  • Error messages and resolutions:

    • "Resource 'lead' not supported!": Indicates an unsupported resource was selected; ensure "Lead" is chosen.
    • "Operation 'delete' not supported!": Indicates an unsupported operation; verify the operation is set to "Delete".
    • API errors related to authorization or missing lead ID should be resolved by checking credentials and input parameters.
    • To handle errors gracefully, enable "Continue On Fail" in the node settings to process subsequent items even if one fails.

Links and References

Discussion