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 creates a session with a specified name and configuration, optionally starting the session immediately after creation. It is useful for managing sessions in applications that require session handling, such as chatbots, automation workflows, or API integrations that maintain stateful interactions.
Use Case Examples
- Creating a new session named 'default' with custom configuration and starting it immediately.
- Creating a session with proxy settings and webhook configurations for event handling.
Properties
| Name | Meaning |
|---|---|
| Name | The unique identifier or name of the session to be created. |
| Start | Boolean flag indicating whether to start the session immediately after creation. |
| Config | JSON configuration object for the session, including metadata, proxy settings, debug options, webhook configurations, and other session-specific settings. |
| Request Options | Settings for request handling such as batching, SSL certificate validation, proxy usage, and timeout duration. |
Output
JSON
sessionId- Identifier of the created session.status- Current status of the session after creation.config- The configuration object used for the session.
Dependencies
- Requires an API key credential or authentication token to interact with the session management service.
Troubleshooting
- Ensure the session name is unique to avoid conflicts or errors during creation.
- Verify the JSON configuration is correctly formatted to prevent parsing errors.
- If the session fails to start, check the 'Start' flag and the service availability.
- Proxy settings must be correct and accessible; otherwise, requests may fail.
- Timeout settings should be adjusted based on network conditions to avoid premature request abortion.