Actions12
Overview
This node integrates with the Vtiger CRM system, enabling various operations such as creating, updating, querying, and deleting records within Vtiger. Specifically, the Update operation allows users to modify existing CRM records by sending updated data elements to the Vtiger API.
Common scenarios for using the Update operation include:
- Modifying contact details or account information after receiving new data.
- Updating the status of deals or tickets based on workflow progress.
- Correcting or enriching existing CRM entries programmatically.
For example, after retrieving a customer record, you might update their phone number or address fields using this node's Update operation by providing the session name and the JSON representation of the updated element.
Properties
| Name | Meaning |
|---|---|
| Session Name | The active session identifier obtained from a prior Login operation; required for authentication in all operations except login. |
| Element | A JSON object representing the CRM record fields and values to be updated. This must conform to Vtiger's expected format for the record. |
Output
The node outputs a JSON array containing the response from the Vtiger API for the update request. This typically includes success status, any error messages, and details about the updated record as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Vtiger CRM instance accessible via its webservice API endpoint.
- Needs valid credentials including host URL, username, and an API access key for authentication.
- The node uses an API session token ("Session Name") obtained through the Login operation to authorize requests.
- The node depends on n8n's HTTP request helper methods to communicate with the Vtiger API.
Troubleshooting
- Invalid Session Name: If the session token is expired or invalid, the API will reject requests. Ensure you perform a successful Login operation first and use the returned session name.
- Malformed Element JSON: The "Element" property must be a correctly structured JSON object matching Vtiger's expected schema. Invalid JSON or missing required fields can cause errors.
- API Connection Issues: Network problems or incorrect host URLs will prevent communication with Vtiger. Verify connectivity and credential correctness.
- Unimplemented Operations: Some operations like "extend_session", "logout", and "sync" are not implemented and will throw errors if used.
- Error Messages: API error responses are passed through; common messages relate to authentication failures, permission issues, or invalid parameters. Review the message content for guidance.
Links and References
- Vtiger CRM Webservice API Documentation
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)