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 is designed to start a session based on a specified session name. It is useful in scenarios where you need to initiate and manage sessions programmatically, such as automating login processes, starting communication sessions, or managing user sessions in an application.
Use Case Examples
- Starting a user session for an application login automation.
- Initiating a communication session for a chat or messaging service.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the session to start. This is a required string input that identifies the session. |
| Request Options | Various options to customize the HTTP request behavior when starting the session, including batching, SSL certificate handling, proxy settings, and timeout duration. |
Output
JSON
sessionId- Identifier of the started session.status- Status of the session start operation, e.g., success or failure.message- Additional information or error message related to the session start.
Dependencies
- Requires an API key credential or authentication token to authorize session start requests.
Troubleshooting
- Common issues include invalid session names, network connectivity problems, or SSL certificate errors if 'Ignore SSL Issues' is not enabled.
- Timeout errors may occur if the server is slow to respond; increasing the timeout setting can help.
- Proxy misconfiguration can lead to failed requests; ensure proxy URL and credentials are correct.