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 meeting confirmation
AI-generatedOverview
This node enables sending and confirming WhatsApp messages via the WaliChat API. Specifically, the Send meeting confirmation operation allows users to respond to event invitations by accepting or declining them. This is useful in scenarios where automated workflows need to handle meeting invites sent through WhatsApp, such as confirming attendance for appointments, webinars, or business meetings.
Practical examples:
- Automatically accept a meeting invite received on WhatsApp when certain conditions are met.
- Decline an event invitation based on user preferences or availability.
- Integrate WhatsApp meeting confirmations into CRM or scheduling systems to keep records synchronized.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The target WaliChat Number ID used to send the message. Select from available WhatsApp numbers linked to your account. |
| Event Message ID | The unique identifier of the event message (meeting invite) you want to respond to. Must be a valid hexadecimal string between 18 and 32 characters. |
| Response | Your reply to the event invitation. Options: "Accept Invitation" or "Decline Invitation". |
| Options | Additional optional settings for message delivery and post-delivery actions, including: - Priority (Normal, High, Low) - Custom label - Reference ID - Agent on behalf of whom the message is sent - Real-time sending mode - Delivery queue mode - Maximum retries - Chat actions after delivery (assign, resolve, label, metadata, etc.) |
| Message Expiration | Defines how long the message remains valid before expiring. Can specify expiration in seconds, duration format (e.g., 1h), or a specific date/time. |
| Mark Chat as Read | Whether to notify WhatsApp that previous unread messages in the chat will be marked as read after sending this message (blue double-check). |
| Typing simulation | Number of seconds to simulate typing or recording status before sending the message (0 disables simulation). |
| Quote Message | Optionally quote another message in the same conversation by specifying its message ID (hexadecimal string 18-32 chars). |
| Strict Message Order | Ensures messages are sent in strict order to the target chat, useful for chatbots or sequences. Not compatible with real-time or never-queue delivery modes. |
Output
The node outputs JSON data representing the result of the meeting confirmation action. This typically includes details about the confirmation status, message IDs, timestamps, and any relevant metadata returned by the WaliChat API.
No binary data output is involved in this operation.
Dependencies
- Requires an active WaliChat WhatsApp API account with at least one configured WhatsApp number.
- An API key credential must be configured in n8n to authenticate requests to the WaliChat service.
- The node depends on the WaliChat API's ability to manage event messages and their confirmations.
Troubleshooting
- Invalid Event Message ID: If the event message ID does not match the required hexadecimal format or length, the node will throw a validation error. Ensure the ID is correct and corresponds to an existing event message.
- Authentication Errors: Missing or invalid API key credentials will prevent the node from communicating with WaliChat. Verify that the API key is correctly set up in n8n credentials.
- Message Delivery Failures: Network issues or API rate limits may cause message sending to fail. Use the retry options and delivery queue modes to mitigate transient errors.
- Incorrect WhatsApp Number or Target: Selecting a WhatsApp number or target chat that is not properly configured or accessible can cause failures. Confirm that the selected device and target exist and are valid.
- Incompatible Options: Using strict message order together with real-time or never-queue delivery modes is not supported and may cause errors. Adjust these settings accordingly.