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 manage various resources, including contacts. Specifically, the Contact - Update operation allows users to update an existing contact's details by specifying the contact's ID and the fields to modify. This is useful in scenarios where contact information changes over time, such as updating phone numbers, email addresses, or other relevant details.
Practical examples include:
- Updating a contact's email after they provide a new one.
- Changing the phone number or title of a contact.
- Adding or modifying descriptive notes related to a contact.
Properties
| Name | Meaning |
|---|---|
| Contact Name or ID | Select a contact from the list or specify its ID via expression to identify which contact to update. |
| Update Fields | Collection of fields to update on the contact. Options include: |
| - Date: Date associated with the contact item. | |
| - Description: Text description for the contact. | |
| - Email: Contact's email address. | |
| - Name: Contact's name. | |
| - Phone: Contact's phone number. | |
| - Title: Contact's title or position. | |
| - Value: Numeric value associated with the contact (context-specific). |
Output
The node outputs JSON data representing the updated contact object returned by the Imobzi API. The output structure contains the updated fields and any additional metadata provided by the API response under the json property.
No binary data output is produced by this operation.
Example output snippet (simplified):
{
"id": 123,
"name": "Updated Contact Name",
"email": "new.email@example.com",
"phone": "1234567890",
"description": "Updated description",
...
}
Dependencies
- Requires an active connection to the Imobzi API using an API key or token configured in n8n credentials.
- The node uses authenticated HTTP requests to interact with Imobzi endpoints.
- No additional external dependencies are required beyond the configured API credential.
Troubleshooting
Common issues:
- Invalid or missing contact ID: Ensure the contact exists and the ID is correct.
- Insufficient permissions or invalid API credentials: Verify that the API key/token has update permissions.
- Empty update fields: If no fields are specified to update, the API may reject the request or perform no action.
Error messages:
"Resource 'contact' not supported!": Indicates an unsupported resource was selected; verify the resource parameter."Operation 'update' not supported!": Indicates an unsupported operation; ensure "update" is selected.- API errors returned from Imobzi will be passed through; check the error message for details like validation failures or authentication errors.
Resolution tips:
- Double-check the contact ID selection or expression.
- Provide at least one field to update.
- Confirm API credentials are valid and have necessary scopes.
- Use the "Continue On Fail" option if you want the workflow to proceed despite individual item errors.
Links and References
- Imobzi API Documentation (Note: link is illustrative; please refer to official Imobzi docs)
- n8n Expressions Documentation
- n8n Node Development Guide