Actions20
- Session Actions
- Message Actions
- Contact Actions
- Typing Actions
- Webhook Actions
Overview
The WhatsAppMultiSession node allows users to interact with the WhatsApp Multi-Session API, specifically for managing webhooks. The "Set URL" operation enables users to configure a webhook URL that will receive notifications from WhatsApp. This is particularly useful for applications that need to respond to incoming messages or events in real-time. For example, a business could set up a webhook to automatically handle customer inquiries received via WhatsApp, allowing for seamless communication and automation.
Properties
| Name | Meaning |
|---|---|
| Session ID | The WhatsApp session ID used to identify the specific session for which the webhook URL is being set. |
| Webhook URL | The URL where WhatsApp will send webhook notifications. This should be a publicly accessible endpoint. |
Output
The output of the execute() method when setting the webhook URL typically includes a JSON object confirming the successful update of the webhook configuration. The structure may include details such as the updated webhook URL or a success message. If there are errors during the process, the output will contain error information.
Dependencies
- An API key credential is required to authenticate requests to the WhatsApp Multi-Session API.
- The server URL for the WhatsApp API must be configured correctly in the n8n environment.
Troubleshooting
Common Issues:
- Incorrect or expired session ID: Ensure that the session ID provided is valid and active.
- Invalid webhook URL: The URL must be publicly accessible; otherwise, WhatsApp will not be able to send notifications.
Error Messages:
- "Authentication failed": This indicates that the API key is invalid or has insufficient permissions. Verify the API key and its associated permissions.
- "Media link has expired": If using media URLs, ensure they are requested fresh from the webhook to avoid expiration issues.