Overview
This node integrates with Vtiger CRM (an open-source customer relationship management system) to perform various operations on CRM data entities. Specifically, the Update operation allows users to modify existing records in Vtiger by specifying the entity ID and the fields to update.
Common scenarios for this node include:
- Updating contact or lead information after receiving new data from a form submission.
- Modifying deal stages or statuses based on external triggers.
- Automating updates to CRM records as part of a workflow that synchronizes data between systems.
For example, you might use this node to update a Lead's phone number or email address when a customer submits updated contact details through a website form.
Properties
| Name | Meaning |
|---|---|
| Entity ID | The unique identifier of the record to update, formatted as MODULExID (e.g., "1x1234"). |
| Body | A JSON object containing the fields and their new values to update in the record. |
Output
The node outputs a JSON array containing the response from the Vtiger API after attempting the update. This response typically includes:
- A success flag indicating if the update was successful.
- The updated record data merged with the changes.
- Any error messages if the update failed.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vtiger CRM instance.
- Needs the base URL and username for the Vtiger API configured in the credentials.
- Uses HTTP requests to communicate with the Vtiger webservice API endpoints.
Troubleshooting
- Entity does not exist or error message: If the specified Entity ID does not correspond to an existing record, the node throws an error indicating the entity could not be found. Verify the Entity ID format and existence in Vtiger.
- Authentication errors: If the API key or username is incorrect, the initial challenge/login request will fail. Ensure credentials are correct and have sufficient permissions.
- Invalid JSON in Body: The Body property must be valid JSON representing the fields to update. Malformed JSON will cause the request to fail.
- Unsupported operation error: If an unsupported operation is selected, the node will throw an error stating the operation is not implemented.