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 → Send scheduled message
AI-generatedOverview
This node enables sending scheduled WhatsApp messages via the WaliChat API. It is designed to deliver text or media messages at a specified future date and time, allowing users to automate message delivery for campaigns, reminders, notifications, or customer engagement workflows.
Common scenarios include:
- Scheduling promotional messages to customers at optimal times.
- Sending appointment reminders or alerts automatically.
- Automating follow-up messages in customer support or sales pipelines.
For example, a business can schedule a message to be sent to a customer’s phone number or group chat exactly at 9 AM on a specific date, ensuring timely communication without manual intervention.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The target WaliChat Number ID used to send the message. This identifies the sending device/account. |
| Target | Type of target chat: Phone (individual), Group, or 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 | Text content of the message to be sent (up to 6000 characters). |
| Delivery date | Date and time when the message should be delivered (scheduled time). |
| Options | Collection of optional settings including: - Priority: Normal, High, Low - Label: Custom label to categorize the message - Reference ID: Custom reference for tracking - Team Agent: Send on behalf of an agent - Live mode: Real-time sending without queue - Delivery Queue Mode: Default, Always Queue, Never Queue, Opportunistic - Maximum Retries: Number of retry attempts - Chat Actions: Post-delivery actions like assign chat, resolve, add/remove labels, set metadata, etc. |
| Message Expiration | Defines message TTL with options to expire after seconds, duration (e.g., "1h"), or at a specific date/time. |
| Mark Chat as Read | Boolean to notify WhatsApp that previous unread messages are read after delivery (blue double-check). |
| Typing simulation | Seconds to simulate typing or recording status before sending (0 disables). Useful for more natural interaction. |
| Quote Message | Message ID to quote when sending this message (must be in same conversation). |
| Strict Message Order | Boolean to ensure messages are sent in strict order. Useful for chatbots or sequences. Not compatible with live or never queue modes. |
Output
The node outputs JSON data representing the result of the scheduled message operation. This typically includes confirmation details such as message IDs, status, timestamps, and any metadata related to the scheduled message.
If binary data were involved (e.g., media files), it would be included accordingly, but for scheduled text messages, output is primarily JSON confirming scheduling success or failure.
Dependencies
- Requires an active WaliChat WhatsApp API account with valid API key credentials configured in n8n.
- The node depends on WaliChat API endpoints for devices, groups, channels, labels, team agents, departments, and message scheduling.
- Proper permissions and plan features may be required for certain delivery queue modes or advanced options.
Troubleshooting
- Invalid phone number format: Ensure phone numbers use E.164 format (e.g., +1234567890). Errors will occur if the regex validation fails.
- Missing required fields: Device ID, target type, and corresponding target identifiers (phone/group/channel) must be provided.
- Delivery queue mode conflicts: Using "Never Queue" or live mode with high message volume risks WhatsApp bans; avoid these modes for bulk messaging.
- Agent or department IDs invalid: When assigning chats post-delivery, agent and department IDs must be valid 24-character hex strings.
- Message expiration misconfiguration: Ensure expiration values are within allowed ranges and correctly formatted.
- Quote message errors: Quoted message ID must exist in the same conversation; otherwise, the API may reject the request.
- Strict order incompatibility: Do not enable strict message order with live or never queue modes; this combination is unsupported.