Actions12
Overview
The node integrates with Vtiger CRM, an open-source customer relationship management system. It allows users to perform various operations on the Vtiger CRM data via its webservice API. The "Sync" operation is listed but not implemented in this version of the node, so it currently throws an error if used.
Common scenarios for this node include automating CRM data management tasks such as creating or updating records, querying data, retrieving details, and managing sessions. For example, a user might automate lead creation when a new contact form is submitted or query customer information to enrich marketing workflows.
Since the "Sync" operation is not implemented, users should use other supported operations like "Create", "Update", "Query", or "Retrieve" for interacting with Vtiger CRM data.
Properties
| Name | Meaning |
|---|---|
| Session Name | The session identifier string obtained through a successful login operation. Required for all operations except "login". |
Note: The provided input properties JSON only includes "Session Name" relevant for non-login operations. Other operations have additional properties (not requested here) such as "Element", "Element Type", "Webservice ID", "Query", and "Related Label".
Output
The node outputs a JSON array containing the response from the Vtiger CRM webservice API corresponding to the invoked operation. The structure of the JSON depends on the operation performed:
- For data retrieval operations (e.g., "query", "retrieve"), the output contains the requested CRM records or metadata.
- For create/update/delete operations, the output reflects the success status and any returned identifiers or messages.
- For login, the output includes session details necessary for subsequent authenticated requests.
No binary data output is produced by this node.
Dependencies
- Requires an active Vtiger CRM instance accessible via its webservice API endpoint.
- Requires credentials including host URL, username, and access key for authentication.
- Uses the
crypto-jslibrary internally to generate MD5 hashes during login. - Must be configured with appropriate API credentials in n8n to authenticate requests.
Troubleshooting
- Unimplemented Operation Error: Using the "Sync" operation will throw an error stating it is not implemented. Avoid using this operation until supported.
- Authentication Failures: Login may fail if credentials are incorrect or the host is unreachable. Check API credentials and network connectivity.
- Session Expiry: Operations require a valid session name obtained from login. If the session expires, re-authenticate to obtain a new session.
- API Errors: The node surfaces error messages returned by the Vtiger API. Review these messages for issues like invalid parameters or permissions.
- Duplicate "listtypes" Case: The code has two cases for "listtypes" with different HTTP methods; this might cause unexpected behavior. Prefer the GET method variant.