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 Contrato (Contract) resource with the Delete operation, it allows users to delete a contract by specifying its name or ID. This is useful in scenarios where contracts need to be programmatically removed from the system, such as automating contract lifecycle management or cleaning up outdated records.

Practical example: Automatically deleting a contract when a related rental agreement ends or when a client cancels their service.

Properties

Name Meaning
Contract Name or ID Select a contract from a dropdown list loaded dynamically from Imobzi or specify an ID via expression.

Output

The output JSON contains the response data from the Imobzi API after attempting to delete the specified contract. Typically, this will include confirmation of deletion or relevant status information returned by the API.

No binary data output is produced by this operation.

Example output structure:

{
  "json": {
    // API response confirming deletion or status message
  }
}

Dependencies

  • Requires an active connection to the Imobzi API.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node uses the Imobzi API endpoint /contracts/{id} with HTTP DELETE method to perform the deletion.

Troubleshooting

  • Common issues:

    • Specifying an invalid or non-existent contract ID may result in an error from the API.
    • Network or authentication failures can prevent successful deletion.
  • Error messages:

    • "Resource 'contrato' not supported!" — indicates an unsupported resource was selected; ensure "Contrato" is chosen.
    • "Operation 'delete' not supported!" — indicates an unsupported operation; verify the operation selection.
    • API errors related to authorization or missing permissions should be resolved by checking the API key credentials.
  • Resolution tips:

    • Verify the contract ID exists and is correct.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.

Links and References

Discussion