Overview
This node integrates with JetAPI to send text messages via multiple messaging channels, specifically WhatsApp and Telegram. It supports sending messages directly through a selected channel or using a "cascade" mode that auto-selects the best delivery channel based on 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 cascade mode to optimize message delivery without manually selecting the channel.
For example, you can send a WhatsApp message to a customer's phone number or send a Telegram message by specifying the recipient's username or user/group ID.
Properties
| Name | Meaning |
|---|---|
| Channel | Select the delivery channel: WhatsApp, Telegram, or Cascade (auto-select channel based on your JetAPI account settings). |
| 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 Telegram user ID (positive for private chat, negative for group chat). |
| Message Text | The text content of the message to send. Supports up to 3500 characters for messengers and 160 for SMS. |
| Additional Options | 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. This typically includes details about the sent message such as message IDs, status, and any metadata returned by the API.
The output is structured as an array of JSON objects, each corresponding to an input item processed. If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with the error message.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with JetAPI.
- Makes HTTP POST requests to
https://api.jetapi.io/api/v1/delivery. - Requires network access to JetAPI endpoints.
- No additional environment variables are needed beyond the API authentication token.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Incorrect phone number or Telegram identifiers may result in delivery failures.
- Exceeding message length limits (3500 chars for messengers, 160 for SMS) may cause errors.
- Scheduling messages with invalid date formats will fail.
Error messages:
- Authorization errors: Check that the API key credential is correctly configured and valid.
- Validation errors: Verify that all required fields (phone, username, etc.) are provided and correctly formatted.
- Network errors: Ensure the n8n instance has internet access and JetAPI service is reachable.
To handle errors gracefully, enable "Continue On Fail" in the node settings to process subsequent items even if some fail.