Actions20
- Session Actions
- Message Actions
- Contact Actions
- Typing Actions
- Webhook Actions
Overview
The "Forward Message" operation of the WhatsApp Multi-Session node allows users to forward an existing message from one recipient to another within the same WhatsApp session. This functionality is particularly useful in scenarios where a user wants to share important information or conversations with others without having to manually copy and paste the content. For example, customer support teams can quickly forward messages from clients to other team members for further assistance.
Properties
| Name | Meaning |
|---|---|
| Session ID | The WhatsApp session ID required to identify the active session for sending messages. |
| Phone Number | The recipient's phone number (including country code, but without the '+' sign). |
| Message ID to Forward | The unique identifier of the message that needs to be forwarded, which must belong to the same session. |
| Message Text | The text content that will accompany the forwarded message, providing context or additional information. |
Output
The output of the "Forward Message" operation typically includes a JSON object indicating the success or failure of the forwarding action. It may contain details such as the status of the operation and any relevant error messages if the operation fails. If binary data is involved, it would generally pertain to media files associated with the message being forwarded.
Dependencies
To use this node, you need:
- An API key credential for authenticating requests to the WhatsApp Multi-Session API.
- The server URL for the WhatsApp Multi-Session API endpoint.
Troubleshooting
Common issues users might encounter include:
- Invalid Session ID: Ensure that the provided session ID corresponds to an active WhatsApp session.
- Message Not Found: Verify that the message ID exists and belongs to the specified session.
- Authentication Errors: Check that the API key is valid and has the necessary permissions.
Error messages may include:
- "HTTP 404": Indicates that the specified message ID could not be found.
- "HTTP 401": Suggests that the API key is invalid or lacks sufficient permissions.
- "HTTP 403": Implies that access to the requested resource is forbidden.