Overview
This node integrates with Vtiger CRM, an open-source customer relationship management system. Specifically, the "Logout" operation allows users to terminate an active session in Vtiger CRM by providing a valid session identifier obtained from a prior login operation.
Common scenarios for this node include:
- Ending a user session securely after completing automated workflows.
- Managing session lifecycle within integrations to avoid stale or unauthorized sessions.
- Ensuring compliance with security policies by explicitly logging out from the CRM system.
For example, after performing data synchronization or updates in Vtiger CRM using other operations, you can use the Logout operation to close the session and prevent further API calls without re-authentication.
Properties
| Name | Meaning |
|---|---|
| Session Name | The session ID string obtained from a successful Login operation. This is required to identify which session to log out from. |
Output
The node outputs a JSON array containing the response from the Vtiger CRM API related to the logout request. The structure typically includes success status and any relevant messages returned by the API confirming the session termination.
No binary data output is produced by this operation.
Dependencies
- Requires an active Vtiger CRM instance accessible via its webservice API endpoint.
- Needs credentials including host URL, username, and an access key for authentication.
- The node depends on n8n's HTTP request helper methods to communicate with the Vtiger API.
- Uses the
crypto-jslibrary internally for hashing during login (not directly relevant for logout but part of the overall node).
Troubleshooting
- Invalid or expired session: If the provided session name is invalid or already expired, the API may return an error indicating the session cannot be found or has timed out. Ensure the session ID is current and was obtained from a recent login.
- Network or connectivity issues: Failure to reach the Vtiger API endpoint will cause errors. Verify network access and correct host configuration.
- Missing or incorrect credentials: Authentication failures due to wrong username or access key will prevent operations. Double-check credential correctness.
- Operation not implemented error: If the node is configured with an unsupported operation value, it will throw an error stating the operation is not implemented.