Overview
This node integrates with Vtiger CRM, an open-source customer relationship management system. It allows users to perform various operations such as creating, deleting, describing records, extending sessions, querying data, logging in and out, and more.
The Extend Session operation specifically refreshes or extends the current session's validity using a provided session name. This is useful in scenarios where a long-running workflow needs to maintain an active session without requiring a full re-login, thus preventing session expiration during extended automation processes.
Practical example: If you have a workflow that periodically updates CRM data over several hours, you can use the Extend Session operation to keep the session alive between API calls.
Properties
Name | Meaning |
---|---|
Session Name | The identifier of the current session to extend. This value is obtained from a prior login operation and is required to authenticate the session extension request. |
Output
The node outputs a JSON object representing the response from the Vtiger CRM API for the extend session request. This typically includes information about the success status of the operation and any relevant session details returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"success": true,
"result": {
"sessionName": "new_session_token",
"serverTime": "timestamp"
}
}
Dependencies
- Requires an active connection to a Vtiger CRM instance.
- Needs an API authentication credential containing at least the host URL, username, and access key.
- The node uses HTTP requests to communicate with the Vtiger webservice endpoint
/webservice.php
. - The node expects the session name parameter to be provided, which is usually obtained from a successful login operation.
Troubleshooting
- Invalid or expired session name: If the session name is invalid or expired, the API will likely return an error indicating session failure. To resolve, perform a fresh login operation to obtain a new session name.
- Network or connectivity issues: Ensure the Vtiger CRM host URL is correct and accessible from the n8n environment.
- Missing or incorrect credentials: Verify that the API credentials (host, username, access key) are correctly configured.
- Unexpected API errors: Check the exact error message returned by the API for clues; common issues include permission problems or API endpoint misconfiguration.