Overview
This node provides integration with the Vtiger CRM system, allowing users to perform various operations such as creating, updating, querying, and managing sessions within Vtiger CRM. The Logout operation specifically terminates an active session in Vtiger CRM by invalidating the provided session name.
Typical use cases for the Logout operation include:
- Ending a user session after completing a series of CRM interactions to ensure security.
- Cleaning up sessions programmatically in automated workflows.
- Managing session lifecycle in multi-step automation processes involving Vtiger CRM.
Example: After logging in and performing data updates or queries, you can use this node's Logout operation to close the session cleanly.
Properties
Name | Meaning |
---|---|
Session Name | The identifier of the active session to be logged out. This value is obtained from a prior Login operation and is required to terminate that session. |
Output
The output is a JSON object representing the response from the Vtiger CRM API for the logout request. It typically contains information about whether the logout was successful.
Example output structure:
{
"success": true,
"result": "Logout successful"
}
No binary data is produced by this operation.
Dependencies
- Requires an active connection to a Vtiger CRM instance via an API key credential.
- The node uses HTTP requests to communicate with the Vtiger CRM webservice endpoint (
/webservice.php
). - Proper credentials including host URL, username, and access key must be configured in n8n for authentication.
- The session name parameter must be valid and correspond to an active session in Vtiger CRM.
Troubleshooting
- Invalid Session Name: If the session name is incorrect or expired, the logout operation may fail. Ensure the session name is obtained from a successful login operation and has not timed out.
- Authentication Errors: If credentials are misconfigured or invalid, the node will not be able to connect to Vtiger CRM. Verify API keys and host URLs.
- API Endpoint Issues: Network issues or incorrect host URLs can cause request failures. Confirm the Vtiger CRM instance is reachable.
- Error Messages: The node throws errors with messages returned from the Vtiger API. For example, if the session is already logged out or invalid, the error message will indicate this. Review the error details to adjust inputs accordingly.
Links and References
- Vtiger CRM Webservice API Documentation
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)