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
Overview
This node allows scheduling WhatsApp messages to be sent via the Wassenger API. It supports sending text messages at a specified future date and time, enabling automation of message delivery for reminders, promotions, notifications, or any scenario where timed communication is needed.
Practical examples include:
- Scheduling appointment reminders to customers.
- Sending promotional messages during specific campaigns.
- Delivering event notifications ahead of time.
The node supports targeting individual phone numbers, groups, or channels, with options to customize message priority, retries, labels, and post-delivery chat actions.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The Wassenger Number ID used as the sender device for message delivery. |
| 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 send time). |
| Options | Collection of optional settings including: - Priority: Normal, High, Low - Label: Custom label to categorize the message - Reference ID: Custom reference identifier - 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 delivery retry attempts - Chat Actions: Post-delivery actions like assigning chat, resolving, labeling, metadata management |
| Message Expiration | Defines message TTL (time-to-live) using seconds, duration string (e.g., "1h"), or specific expiration date/time. |
| Mark Chat as Read | Whether 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 feel. |
| Quote Message | Message ID to quote when sending this message (must be in same conversation). |
| Strict Message Order | Ensures messages are sent in strict order to the target chat. Useful for chatbots or sequences. Not compatible with live mode or never queue delivery. |
Output
The node outputs JSON data representing the result of the scheduled message operation. This typically includes confirmation details such as message IDs, status, and metadata returned by the Wassenger API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured.
- Some properties load dynamic options from the API, such as available devices, groups, channels, team agents, labels, and departments.
- Proper configuration of these entities in Wassenger is necessary for successful operation.
Troubleshooting
- Invalid phone number format: Ensure phone numbers follow the E.164 format (e.g., +1234567890). The node validates this and will error if invalid.
- Missing required fields: Device, target, and corresponding target identifiers (phone, group ID, or channel ID) must be provided.
- Delivery failures: If messages fail to deliver, check the maximum retries setting and consider adjusting delivery queue mode.
- Live mode risks: Using real-time delivery ("live" or "never queue") for high-volume messaging can increase risk of WhatsApp bans.
- Action validation errors: When specifying chat actions, ensure agent and department IDs are valid 24-character hexadecimal strings.
- Message quoting errors: Quoted message IDs must be valid and belong to the same conversation.
- Expiration misconfiguration: Expiration times must be within allowed ranges and correctly formatted.
- API authentication issues: Verify the API key credential is valid and has sufficient permissions.