Overview
This node integrates with JetAPI to send text messages via multiple messaging channels, specifically WhatsApp and Telegram. It supports sending messages directly through these platforms or using a "Cascade" mode that auto-selects the best channel based on your account settings and priority configured in the JetAPI dashboard.
Common scenarios for this node include:
- Automating customer notifications or alerts via WhatsApp or Telegram.
- Sending marketing or transactional messages programmatically.
- Using the cascade feature to optimize message delivery without manually selecting the channel.
Practical example:
- A business wants to notify customers about order status updates via WhatsApp if available, otherwise fallback to Telegram automatically.
- Sending personalized Telegram messages by username or user/group ID for targeted communication.
Properties
| Name | Meaning |
|---|---|
| Channel | Select the delivery channel: WhatsApp, Telegram, or Cascade (auto-select channel based on account settings and priority). |
| Recipient Type | (Only for Telegram) How to identify the recipient: Phone Number, Telegram Username, or Telegram User or Group ID. |
| Phone Number | (For WhatsApp or Cascade) Recipient's phone number in international format (e.g., +12345678900). |
| Phone Number (Telegram) | (For Telegram when recipient type is Phone Number) Recipient's phone number in international format. |
| Username | (For Telegram when recipient type is Telegram Username) Telegram username without the '@' symbol. |
| Telegram User or Group ID | (For Telegram when recipient type is Telegram User or Group ID) Numeric ID identifying the user (positive) or group (negative). |
| Message Text | The text content of the message to send. Supports up to 3500 characters for messengers and 160 for SMS. |
| Additional Options | Collection of optional fields to customize the message: - UTM Mark: Label for marking shipments. - Callback URL: URL to receive delivery status updates. - External ID: Client-side message ID for idempotence. - Scheduled At: Delayed dispatch date/time (UTC+0). - Priority: Message priority (High, Medium, Low). - Reply to Message ID: Message ID to reply to (from webhook). - Simulate Typing: Boolean to simulate typing indicator in WhatsApp (default true). |
Output
The node outputs JSON data representing the response from the JetAPI delivery endpoint after attempting to send the message. This typically includes details such as message IDs, status, and any error information if the request failed.
No binary data output is produced by this node.
Example output structure (simplified):
[
{
"message_id": "string",
"status": "string",
"error": "string (if any)"
}
]
Dependencies
- Requires an API key credential for authenticating with JetAPI.
- Makes HTTP POST requests to
https://api.jetapi.io/api/v1/delivery. - No additional environment variables are required beyond the API authentication token.
Troubleshooting
Common issues:
- Invalid or missing phone numbers or Telegram identifiers will cause message sending to fail.
- Incorrect API credentials will result in authorization errors.
- Scheduling messages with invalid date formats may cause rejection.
- Exceeding character limits for message text can lead to errors.
Error messages:
- Authorization errors: Check that the API key credential is correctly configured.
- Validation errors: Verify that all required fields (phone, username, etc.) are provided and correctly formatted.
- Network errors: Ensure connectivity to
api.jetapi.ioand no firewall restrictions.
Resolution tips:
- Double-check input parameters according to the selected channel and recipient type.
- Use the callback URL option to monitor delivery statuses and troubleshoot failures.
- Enable "Continue On Fail" in n8n to handle errors gracefully during batch processing.