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 updates a session configuration for a WhatsApp automation system. It allows users to specify the session name and provide a detailed JSON configuration to modify session settings such as metadata, proxy settings, debugging options, webhook configurations, and storage options. This node is useful for managing and customizing active WhatsApp sessions programmatically, for example, to change webhook URLs, enable or disable debugging, or update proxy settings dynamically.
Use Case Examples
- Updating the webhook URL for a specific WhatsApp session to receive message and session status events.
- Changing the proxy server settings for a session to route traffic through a different proxy.
- Enabling debug mode and adjusting storage options for a session to troubleshoot issues or optimize performance.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the WhatsApp session to update. This is a required string input that identifies which session's configuration will be modified. |
| Config | A JSON object representing the new configuration for the session. This includes metadata, proxy settings, debug flags, webhook definitions, and storage options. The JSON is parsed and sent as the request body to update the session. |
| Request Options | Additional HTTP request options such as batching parameters, SSL certificate validation behavior, proxy settings, and request timeout. These options control how the update request is sent to the server. |
Output
JSON
session- The name of the session that was updated.config- The updated configuration object for the session.status- The status of the update operation, indicating success or failure.
Dependencies
- Requires an API key or authentication token to connect to the WhatsApp automation backend service.
Troubleshooting
- Ensure the session name provided exists and is active; otherwise, the update will fail.
- Verify the JSON configuration is correctly formatted and valid to avoid parsing errors.
- If using a proxy, confirm the proxy URL and credentials are correct to prevent connection issues.
- If SSL validation is disabled, be aware of potential security risks and only use this option if necessary.
- Timeout errors may occur if the server is slow or unreachable; consider increasing the timeout value.