Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Send messages → Forward message
AI-generatedOverview
This node operation allows forwarding an existing WhatsApp message from one chat to another using the WaliChat WhatsApp API. It is useful when you want to share or redirect a previously received or sent message without retyping or re-uploading content. Common scenarios include customer support workflows where agents forward messages to other departments, broadcasting important messages to groups or channels, or automating message sharing in chatbot sequences.
For example, you can forward a customer's question from a private chat to a group of support agents or forward a promotional message from a channel to individual customers.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The target WaliChat Number ID used for sending the forwarded message. This identifies the WhatsApp account/device that will deliver the message. |
| Target | Type of target chat to send the forwarded message to. Options: Phone (individual), Group, Channel. |
| Phone Number | Target phone number in international E.164 format (e.g., +1234567890). Required if Target is "Phone". |
| Group ID | ID of the target group chat (e.g., 12345678902401234@g.us). Required if Target is "Group". |
| Channel ID | ID of the target channel (e.g., 12345678902402200@newsletter). Required if Target is "Channel". |
| Message ID to Forward | The unique ID of the message to forward. Must be a hexadecimal string between 18 and 32 characters. |
| Source Chat ID | Optional. The chat ID where the original message belongs (e.g., +1234567890 or 123456789012345@g.us). If not provided, the system attempts to discover it automatically. |
| Options | Collection of optional settings including: - Priority (Normal, High, Low) - Label (custom categorization label) - Reference ID (custom reference) - Team Agent (send on behalf of an agent) - Live mode (real-time delivery) - Delivery queue mode (default, always queue, never queue, opportunistic) - Maximum retries - Post-delivery chat actions (assign, resolve, label, metadata management, etc.) |
| Message Expiration | Defines time-to-live (TTL) for the forwarded message. Can specify expiration by seconds, duration (e.g., 1h), or specific date/time. |
| Mark Chat as Read | Boolean flag to notify WhatsApp that previous unread messages in the chat are read after forwarding (blue double-check). Requires WhatsApp read confirmation enabled. |
| Typing simulation | Number of seconds (0-30) to simulate typing or recording status before forwarding the message. Zero disables this feature. |
| Quote Message | Optionally quote another message ID in the same conversation when forwarding. Must be a valid message ID (18-32 hex characters). |
| Strict Message Order | Boolean to ensure messages are sent in strict order to the target chat. Useful for chatbots or sequences. Not compatible with live mode or never queue delivery options. |
Output
The node outputs JSON data representing the result of the forward message operation. This typically includes details such as message IDs, status, timestamps, and any metadata returned by the WaliChat API confirming successful forwarding.
If binary data were involved (not typical for forwarding messages), it would represent media files or attachments, but this operation focuses on forwarding existing messages identified by their IDs.
Dependencies
- Requires an active WaliChat WhatsApp API connection authenticated via an API key credential.
- The node depends on WaliChat services for device management, group/channel info, labels, team agents, and message operations.
- Proper configuration of the WaliChat API credentials in n8n is necessary.
- Some options depend on dynamic loading of devices, groups, channels, labels, team agents, and departments via API calls.
Troubleshooting
- Invalid Message ID: If the message ID to forward does not match the required hexadecimal format or length, the node will throw a validation error. Ensure the message ID is correct and matches 18, 20, 24, or 32 hex characters.
- Target Chat Not Found: Providing an incorrect or missing target phone number, group ID, or channel ID will cause failures. Verify the target identifiers are accurate and accessible by the selected WhatsApp number.
- Source Chat ID Missing: If the source chat ID is not provided, the system tries to auto-discover it. Failure to find the source chat may cause errors. Providing the source chat ID explicitly can help.
- Delivery Mode Conflicts: Using "Never Queue" delivery mode with high message volume risks WhatsApp bans. Use queue modes appropriately based on your messaging plan.
- Agent or Department IDs Invalid: When assigning chats post-delivery, invalid agent or department IDs will cause errors. Ensure these IDs are valid and loaded correctly.
- Typing Simulation Limits: Typing simulation must be between 0 and 30 seconds; values outside this range will be rejected.
- Read Acknowledgment Disabled: Marking chat as read requires WhatsApp privacy settings to allow read receipts; otherwise, it will have no effect.