GREEN-API
MessagingSend and receive WhatsApp messages through your own GREEN-API instance. Agents deliver texts and files by URL, verify numbers are on WhatsApp, read chat history, and poll the notification queue for inbound messages without configuring webhooks.
What This Integration Enables
GREEN-API puts a real WhatsApp number under API control: your own connected instance, not a hosted business platform. That cuts both ways, and this page takes the trade seriously. The upside is direct: agents send texts and files to the chat surface most customers actually watch, and receive replies as structured events by polling the notification queue, no webhook infrastructure required. The downside is that the asset on the line is your WhatsApp number itself, which is why disciplined flows treat sending as a privilege to be preflighted, not a default. - Send notifications, alerts, and confirmations to customers and teams from any automation - Deliver invoices, images, and documents to a contact or group by URL - Verify a number is registered on WhatsApp before messaging it - Poll for and process inbound messages without configuring webhooks - Confirm the instance is authorized and healthy before any send flow runs The channel's power is that it is personal. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step is what keeps an automated sender from behaving like a spammer on a number you cannot afford to lose. The polling model is worth a word, because it removes the usual infrastructure tax. Receiving WhatsApp messages normally means standing up a webhook endpoint, securing it, and keeping it alive. Here the queue does the buffering: events wait server-side until a flow pulls them with Receive Notification and acknowledges with Delete Notification, so a paused flow loses nothing and a resumed one picks up exactly where the queue left off.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order confirmations where the customer actually looks
An order fires in [Shopify](/integrations/shopify) or [WooCommerce](/integrations/woocommerce). The agent checks Get State, verifies the buyer with Check WhatsApp, and sends the confirmation with Send Message, then the invoice PDF with Send File By URL, addressed to the buyer's chatId. The customer gets everything in one WhatsApp thread they will actually open, and the team sees the delivery logged in [Slack](/integrations/slack).
The shared inbox that is not a shared phone
Customers reply to the business number all day. A scheduled flow loops Receive Notification, logs each inbound message to [Google Sheets](/integrations/google-sheets) with sender, text, and timestamp, and clears each event with Delete Notification. Simple questions get a templated answer from the agent; anything with heat in it, a refund demand, a delivery dispute, posts to the support channel with the full thread from Get Chat History attached, and a person replies through the same instance. The phone stops being a bottleneck without the conversation losing its human.
Form follow-up that verifies before it sends
A [Typeform](/integrations/typeform) response arrives with a phone number. The agent runs Check WhatsApp on the digits first: registered numbers get a WhatsApp confirmation with next steps via Send Message, unregistered ones fall back to email. No messages fired into the void, and the follow-up reaches each respondent on a channel that can actually receive it.
Human-in-Loop Highlight
Send Message spends a currency this connector cannot mint: the standing of your own WhatsApp number. GREEN-API is an unofficial gateway, and WhatsApp blocks numbers whose messages draw reports, Get State even has a dedicated value for it, blocked, at which point every customer conversation on that number goes dark at once. So FlowRunner flows ration the send path by relationship. Transactional messages to a customer who just ordered flow through automatically. Anything outside that, a first-touch message to a number with no chat history, a batch send to a list, a group blast, stops and posts: "42 recipients, no prior conversation with 39 of them, message text attached. This send pattern risks the instance. Approve, trim to the 3 existing chats, or cancel?" A person decides, because the agent can compose a message in a second but cannot restore a blocked number at any speed. Get Chat History gives the gate its evidence: who has actually talked to us, and who would be hearing from us cold.
Agent Capabilities
7 actionsMessaging
3- Send Message Sends a plain text message to a contact or group chat, addressed by chatId in the `{countrycode}{number}@c.us` or `{group-id}@g.us` format, returning the WhatsApp message ID. Supports quoting an existing message. The operation this page's human gate rations.
- Send File By URL Delivers a file from a publicly accessible URL as an image, video, audio, or document based on file type, with an optional caption. The document-delivery step for invoices and attachments.
- Get Chat History Retrieves a chat's recent messages with type, text, direction, timestamp, and message ID. The context read behind reply routing and the gate's cold-contact check.
Contacts
1- Check WhatsApp Checks whether a phone number, digits only, is registered on WhatsApp. The preflight that keeps flows from messaging the void.
Instance
1- Get State Returns the instance's authorization state: authorized, notAuthorized, blocked, sleepMode, or starting. The health check that runs before every send flow.
Notifications
2- Receive Notification Polls the incoming queue for the oldest unread event, an inbound message or delivery status, with a receiptId. Returns null when the queue is empty. The webhook-free path for receiving messages.
- Delete Notification Deletes a processed notification by receiptId so the queue advances. Always paired with Receive Notification in a processing loop.
Frequently Asked Questions
What can FlowRunner do with GREEN-API?
FlowRunner agents can run Send Message, Send File By URL, and Check WhatsApp in GREEN-API, plus 4 more actions.
Does connecting GREEN-API to FlowRunner require OAuth?
GREEN-API uses a custom authentication method to connect to FlowRunner.
Can GREEN-API trigger a FlowRunner workflow automatically?
GREEN-API doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with GREEN-API
$100 in credits. No card required. Connect in minutes.