JetAPI
MessagingSend messages through JetAPI, a gateway reaching WhatsApp, Telegram, SMS, MAX, VK, and Odnoklassniki behind one API. Agents pick the channel per recipient without a connector per network.
What This Integration Enables
JetAPI is a reach story, not a delivery story. Behind one API token it reaches WhatsApp, Telegram, SMS, MAX, VK and Odnoklassniki, which matters most when your customer base sits across markets where the default messenger is not the one your product team assumed. MAX, VK and Odnoklassniki are Russian market networks. If a share of your recipients live there, the alternative to this connector is not a better connector, it is a project.
The mechanic that makes it useful inside a flow is the channel order. You list channels in preference order and JetAPI tries them in turn, so a message goes out over WhatsApp when the recipient is reachable there and falls back to SMS when they are not. That is genuinely convenient and it is also where the honesty problem lives, because the two channels are not the same medium. A messenger message can run to 3,500 characters. A Latin alphabet SMS gets 160. The agent can see that difference before it sends, which is exactly why it should be the thing that stops and asks.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order notifications over whatever reaches the customer
An order in WooCommerce moves to shipped. The agent validates the recipient with Lookup Phone Number, then calls Send Message with WhatsApp listed ahead of SMS. Customers on WhatsApp get the full message with the tracking link and a quotable reference to the original confirmation. Everyone else gets a short SMS. The agent then polls Get Delivery to record the status, the operator and the cost of each send against the order, so support can see what was sent and what it cost when a customer says nothing arrived.
Sending the document rather than a link to a portal
An invoice is generated and needs to reach the customer. The agent calls Send File with the PDF. On WhatsApp and Telegram Personal an image under 10 MB is delivered natively as a photo, and everything else arrives as a download link that stays valid for seven days. The agent records the seven day expiry against the invoice record in QuickBooks Online, so a collections follow up three weeks later sends a fresh copy rather than a dead link.
Working the inbound reply without leaving your own application
On WhatsApp Message fires when a customer replies. The agent reads the message, classifies it, and for anything routine responds with Send Message. For anything that needs a person, it calls Add Chat Notes to attach the customer's order history and open tickets to the conversation, then Open Dialog By Phone to produce a link that drops an agent straight onto that thread inside your own application. The support rep sees the context from Zendesk next to the chat instead of alt tabbing to find it.
Human-in-Loop Highlight
The channel fallback is the thing that will bite you, and it will do it silently. When the agent composes a 900 character shipping update and lists WhatsApp before SMS, the recipients who are not on WhatsApp do not get a shorter version of the same message. They get a truncated one, billed per segment, and the part that got cut is usually the part at the end that mattered. Before a Send Bulk Message run, the agent resolves the channel per recipient using Lookup Phone Number, counts the fallbacks, and stops: "412 of these 1,840 recipients are not reachable on WhatsApp and will receive this as SMS. Here is the 160 character version they will get, and the account balance from Get Account is 6,100 credits. Send the SMS variant, hold those 412 for the email flow, or rewrite?" A person decides which recipients get the compromise, because a truncated message is a decision about the customer relationship and not a formatting detail. This is what an automation exception looks like when the agent is honest about what it is about to do.
Agent Capabilities
15 actionsMessaging
5- Send Message Sends a text message to one phone number, trying channels in the order given so a message delivers over WhatsApp when possible and falls back to SMS otherwise. Supports scheduling up to a month ahead and quoting an earlier message. Used for order, delivery and appointment notifications where the right channel varies per recipient.
- Send Bulk Message Sends the same text to a list of phone numbers in one request. Used for broadcasts and campaign blasts, with the same channel order and scheduling behaviour as a single send.
- Send File Sends a file to a phone number. Images under 10 MB arrive natively as photos on WhatsApp and Telegram Personal, and everything else arrives as a download link valid for seven days. Used to deliver invoices, shipping documents and images without pointing the customer at a portal login.
- Get Delivery Returns the current status of a message submitted through Send Message or Send File, together with the recipient's mobile operator and the cost of the send. Used to reconcile what was sent, on which network, at what price.
- Delete Delivery Deletes a message that was already sent, revoking it in the conversation on the WhatsApp and Telegram Personal channels. Used in the narrow case where a wrong message was sent and the channel still allows it to be pulled back.
Account
3- Get Account Returns the account balance, the registered sender names, the channels enabled for sending and the date the subscription is paid until. Used as the guard before a broadcast so a campaign does not stop halfway through for want of funds.
- Lookup Phone Number Returns the mobile operator, country and normalised international form of a phone number. Used to validate recipients before spending a send on them and to understand which network the send will be billed against.
- List UTM Marks Returns the UTM marks defined on the account. Used to attach campaign labels to sends so results can be told apart in reporting.
Webhooks
3- List Webhooks Returns every webhook subscription on the account with its events and destination URL. Used to audit subscriptions, including any created outside this connection.
- Get Webhook Retrieves a single webhook subscription by identifier. Used to confirm which events a specific subscription listens for before changing it.
- Update Webhook Changes the destination URL or the event list of an existing webhook subscription. Used when a receiving endpoint moves or an event set needs narrowing.
Web Messenger
4- Create Chat Link Creates a link to the JetAPI web messenger that can be embedded in an iframe, so support staff work the WhatsApp and Telegram inbox from inside your own application. Entry can be password protected or left open.
- Open Dialog By Phone Opens the web messenger straight onto the conversation with a given phone number, showing the most recently active channel when a contact has both WhatsApp and Telegram. The dialog can be isolated so the agent cannot navigate back to the full chat list.
- Add Chat Notes Attaches notes to the conversation with a phone number, so a rep sees order history, open tickets and account context next to the chat. Note bodies accept Markdown links and emphasis.
- Delete Web Messenger Chats Removes the stored conversations and messages shown in the web messenger for the account and reports how many of each were deleted. Used for data retention cleanups, and worth treating as permanent.
Triggers
2 triggersEvent Triggers
2- On WhatsApp Message Fires when a message is sent or received on the connected WhatsApp account. Each delivery runs the flow with the message text, or for media a temporary download link produced by JetAPI. Used to start a reply, routing or ticket creation flow the moment a customer writes in.
- On Messenger Event Fires when one of the selected JetAPI events occurs, covering WhatsApp and Telegram messages, outgoing message status changes, and the connected WhatsApp account logging in or out. Used to watch delivery status across channels and to alert an operator when the connected account drops its session, which is the failure that silently stops every downstream send.
Frequently Asked Questions
What can FlowRunner do with JetAPI?
FlowRunner agents can run Send Message, Send Bulk Message, and Send File in JetAPI, plus 12 more actions.
Does connecting JetAPI to FlowRunner require OAuth?
No. JetAPI connects to FlowRunner with an API key, no OAuth flow required.
Can JetAPI trigger a FlowRunner workflow automatically?
Yes. JetAPI supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with JetAPI
$100 in credits. No card required. Connect in minutes.