Overview
This node integrates with the Vtiger CRM system, allowing users to perform various operations on CRM entities such as creating, retrieving, updating, deleting records, querying data, and describing modules. Specifically, the Delete operation removes an entity from Vtiger CRM based on its unique identifier.
Common scenarios for using the Delete operation include:
- Automatically cleaning up outdated or invalid CRM records.
- Removing duplicates or erroneous entries during data synchronization workflows.
- Managing lifecycle of leads, contacts, or other CRM objects by deleting them when no longer needed.
Example: A workflow that deletes a contact record in Vtiger CRM when it is marked as unsubscribed in an email marketing tool.
Properties
| Name | Meaning |
|---|---|
| Entity ID | The unique identifier of the entity to delete, formatted as MODULExID (e.g., "1x1234"). |
Output
The node outputs a JSON object representing the response from the Vtiger CRM API after attempting the delete operation. This typically includes:
success: Boolean indicating if the deletion was successful.- Additional metadata or error messages returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires connection credentials to a Vtiger CRM instance, including:
- Host URL of the Vtiger server.
- Username.
- An API access key for authentication.
- The node uses the Vtiger webservice API endpoints (
/webservice.php) for all operations. - Requires n8n HTTP Request helper functions to communicate with the API.
Troubleshooting
- Authentication errors: If the node fails at the login challenge step, verify that the username and API access key are correct and that the Vtiger server is reachable.
- Entity not found: When deleting, if the specified Entity ID does not exist, the API will return an error. Ensure the ID is correctly formatted and exists in the CRM.
- Invalid Entity ID format: The Entity ID must be in the form
MODULExID(e.g., "1x1234"). Using an incorrect format will cause the API call to fail. - API endpoint issues: Confirm that the Vtiger instance supports the webservice API and that the
/webservice.phpendpoint is accessible. - Permission issues: The user associated with the API key must have sufficient permissions to delete records in the specified module.