Actions101
- š¤ Chatting Actions
- š„ļø Sessions Actions
- š Auth Actions
- š¼ļø Screenshot Actions
- š¢ Channels Actions
- š¢ Status Actions
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ Groups Actions
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
Overview
This node operation stops a specified session by its name. It is useful in scenarios where you need to programmatically terminate active sessions, such as ending user sessions in an application or stopping background processes associated with a session. For example, it can be used to stop a session after a certain task is completed or to manage session lifecycle in automation workflows.
Use Case Examples
- Stopping a user session after logout to free up resources.
- Terminating a session that has been idle for too long to enhance security.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the session to stop. This is a required string input that identifies which session to terminate. |
| Request Options | Optional settings to customize the HTTP request behavior, including batching, SSL certificate validation, proxy configuration, and request timeout. |
Output
JSON
stoppedSession- Details or confirmation of the stopped session.
Dependencies
- Requires an API key credential or authentication token to access the session management API.
Troubleshooting
- Ensure the session name provided exists and is active; otherwise, the stop operation may fail or return an error.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
- Proxy settings must be correctly configured if used; incorrect proxy URLs or credentials can cause request failures.
- Timeouts may occur if the server is slow to respond; adjust the timeout setting accordingly.