Overview
This node integrates with Vtiger CRM, an open-source customer relationship management system. Specifically, the "Extend Session" operation allows users to extend the validity of an existing session by providing a session identifier obtained from a prior login operation. This is useful in scenarios where long-running workflows need to maintain authenticated access without re-logging in repeatedly.
Practical examples include:
- Keeping a session alive during batch data synchronization.
- Extending session duration before performing multiple consecutive API calls.
- Avoiding session expiration errors in automated workflows interacting with Vtiger CRM.
Properties
| Name | Meaning |
|---|---|
| Session Name | The session ID string obtained from a previous login operation; used to identify which session to extend. |
Output
The node outputs JSON data representing the response from the Vtiger CRM API for the extend session request. This typically includes success status and any relevant session information returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Vtiger CRM instance accessible via its API endpoint.
- 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 CRM webservice.php endpoint.
Troubleshooting
Common issues:
- Providing an invalid or expired session name will likely cause the API to reject the extend session request.
- Network connectivity problems to the Vtiger CRM server can cause request failures.
- Missing or incorrect API credentials will prevent successful authentication.
Error messages:
- If the session is invalid or expired, the API may return an error message indicating session failure.
- Errors related to missing parameters or unauthorized access will be thrown as node operation errors with descriptive messages.
To resolve these:
- Ensure the session name is correctly passed from a successful login operation.
- Verify network connectivity and correct API endpoint configuration.
- Confirm that the API credentials are valid and have sufficient permissions.