Overview
This node integrates with Vtiger CRM, an open-source customer relationship management system. It supports multiple operations such as login, listing types, creating, updating, retrieving, deleting records, and more.
For the Delete operation specifically, the node deletes a record in Vtiger CRM identified by its Webservice ID. This is useful when you want to programmatically remove obsolete or incorrect data from your CRM directly within an n8n workflow.
Practical example:
You have a workflow that processes leads and determines if they are invalid. Using this node's Delete operation, you can automatically remove those invalid lead records from Vtiger CRM by specifying their Webservice IDs.
Properties
| Name | Meaning |
|---|---|
| Session Name | The session ID obtained from a previous Login operation; required for authentication. |
| Webservice ID | The unique identifier of the record in Vtiger CRM that you want to delete. |
Output
The node outputs a JSON array containing the response from the Vtiger CRM API after attempting the deletion. This typically includes success status and any relevant messages or error details returned by the API.
No binary data output is involved in the Delete operation.
Dependencies
- Requires an active Vtiger CRM instance accessible via HTTP.
- Needs an API authentication credential (an API key or access token) configured in n8n to authenticate requests.
- The node uses the Vtiger CRM webservice API endpoints (
/webservice.php). - The user must first perform a Login operation to obtain a valid session name (session ID), which is then used in subsequent operations like Delete.
Troubleshooting
Common issues:
- Invalid or expired session name: If the session ID is missing, expired, or incorrect, the API will reject the request.
- Incorrect Webservice ID: Providing a wrong or non-existent record ID will cause the delete operation to fail.
- Network or connectivity problems with the Vtiger CRM server.
Error messages:
- Errors returned by the Vtiger API usually include a message and code. For example, "Session expired" or "Record not found".
- The node throws errors if the initial challenge or login steps fail during authentication.
Resolutions:
- Ensure the Login operation is performed successfully before Delete to get a valid session.
- Verify the Webservice ID corresponds to an existing record.
- Check network connectivity and API endpoint correctness.
- Review API credentials and permissions.