Actions20
- Session Actions
- Message Actions
- Contact Actions
- Typing Actions
- Webhook Actions
Overview
The WhatsApp Multi-Session node allows users to interact with the WhatsApp Multi-Session API, specifically for managing sessions. This node is particularly useful for applications that require automated messaging capabilities through WhatsApp, such as customer support bots or notification systems. Common scenarios include creating new WhatsApp sessions for different users, retrieving session information, and managing session connections.
For example, a business could use this node to create a dedicated WhatsApp session for each customer service representative, allowing them to send and receive messages seamlessly through their own session.
Properties
| Name | Meaning |
|---|---|
| Session ID | The WhatsApp session ID (required) |
| Session Name | Display name for the session (optional) |
Output
The output of the execute() method will be an array of JSON objects, where each object represents the result of the operation performed. For the "Create" operation, the output will typically include details about the newly created session, such as its ID and any relevant metadata. If there are errors during the execution, the output will also contain error messages and codes.
Dependencies
- An API key credential is required to authenticate requests to the WhatsApp Multi-Session API.
- The server URL for the WhatsApp Multi-Session API must be configured in the n8n environment.
Troubleshooting
- Common Issues: Users may encounter issues related to authentication failures, invalid session IDs, or network errors.
- Error Messages:
- Authentication failed: Indicates that the provided API key is incorrect or lacks necessary permissions. Ensure the API key is valid and has the correct access rights.
- Media link has expired: This occurs when trying to access a media file using a temporary URL that has expired. Request a new media URL from the webhook.
- HTTP errors (e.g., 404, 403): These indicate that the requested resource was not found or access is forbidden. Verify the session ID and ensure proper permissions are set.