Actions5
- Message Actions
- Contact Actions
- Session Actions
Overview
This node integrates with the Sendtick API to send WhatsApp messages. It allows users to send text messages to specified phone numbers or WhatsApp IDs through a selected WhatsApp session. This is useful for automating customer notifications, alerts, or any communication via WhatsApp in workflows.
Typical use cases include:
- Sending order confirmations or updates to customers.
- Delivering reminders or alerts automatically.
- Broadcasting messages to specific contacts using WhatsApp sessions.
Properties
| Name | Meaning |
|---|---|
| To | Recipient phone number with country code. Can be a full WhatsApp JID (e.g., 60123456789@s.whatsapp.net) or a phone number with optional leading "+". The node normalizes this to a valid WhatsApp ID format. |
| Session ID | Identifier of the WhatsApp session to send the message from. This selects which WhatsApp account/session will be used for sending. |
| Message | The text content of the message to send. |
Output
The node outputs JSON data representing the response from the Sendtick API after attempting to send the message. This typically includes details about the sent message such as status, message ID, or error information if the request failed.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"status": "success",
"messageId": "abc123",
"to": "60123456789@s.whatsapp.net",
"message": "Your message text here"
}
Dependencies
- Requires an API key credential for authenticating with the Sendtick API.
- The node uses the Sendtick API endpoint at
https://sendtick.co/api/v1. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Missing Session ID: If the "Session ID" property is empty, the node throws an error stating that the session ID is required. Ensure you provide a valid session identifier.
- Invalid Recipient Format: The "To" field must be either a valid phone number with optional "+" prefix or a full WhatsApp JID. Errors occur if the format is incorrect, e.g., non-digit characters in the phone number or invalid JID local part.
- Empty Message: The message text cannot be empty; otherwise, an error is thrown.
- API Request Failures: Network issues or invalid API credentials can cause request failures. Verify your API key and network connectivity.
- Error Handling: If "Continue On Fail" is enabled, errors are returned as JSON objects with an "error" field instead of stopping execution.
Links and References
- Sendtick API Documentation (for detailed API usage)
- WhatsApp Business API Guidelines (for understanding WhatsApp message formats)