EleAPIs
MessagingConnect AI agents to EleAPIs (Express-Chat), the omnichannel chatbot and WhatsApp Business platform. Agents search and segment inbox contacts across website, WhatsApp, and social channels and reply where the customer started.
What This Integration Enables
EleAPIs, the platform behind Express-Chat, has a deliberately short action list, and the shape of that list tells you what the product is for. Five of the eight operations are about the audience: searching the inbox, listing segments, importing contacts in bulk, changing their status, and checking which templates Meta has actually approved. Only three are sends. The message is the easy part here. Getting the list right is the whole job.
That is a genuinely different starting point from a shared inbox, and it makes Search Inbox Contacts the most important action on the connector. It narrows by free text, tags, lifecycle status, segments, online state, assigned agent, whether the contact has interacted or ordered, and by the channel they arrived on, with creation and last-seen date ranges supplied as explicit windows. An agent can build an audience that would take a person several passes through the UI, in one call, from data that is current at the moment of the query. The connector also uses two separate credentials, an Inbox API Token for the contact operations and a WhatsApp API Key for the sends, so a flow can be scoped to read and segment without holding the ability to message anyone. FlowRunner agents use that separation on purpose: assemble freely, send deliberately, and put a person in front of the operations that reach a customer or change a record permanently. That is what human-in-the-loop buys you.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order and appointment updates that check their own paperwork first
An order ships in Shopify. Before composing anything, the agent calls List WhatsApp Templates and reads the current Meta approval status, category and component configuration for the shipping template. If the template is reported approved, the agent fills its parameters and sends with Send WhatsApp Template Message. If it is not, the agent does not fall back to a free-form text message, because free text only reaches contacts inside an open customer service window and the customer has not written in. It raises the blocked template to the marketing owner instead. The failure surfaces as a decision rather than as a silently unsent notification.
CRM contacts into the inbox as a repeatable sync
New customers appear in the CRM. The agent batches them into Import WhatsApp Contacts, supplying each display name, email and phone number split into country prefix and subscriber number, seeded with the tags and custom attributes that will later drive segmentation. Because the endpoint upserts, the same flow can run on a schedule against the whole customer list without creating duplicates. The inbox stays in step with the CRM instead of being reconciled by hand every quarter.
Building a broadcast audience from behaviour rather than a list
A campaign needs everyone who arrived on WhatsApp, carries a specific tag, has ordered before, and has been seen in the last 60 days. The agent expresses that as a single Search Inbox Contacts call, cross-checks the returned segment IDs against List Segments, and hands the resolved audience to the campaign owner with the query it used written out in plain language. The owner is approving a definition they can read, not a row count they have to trust.
Human-in-Loop Highlight
Update Contact Status is the documented mechanism for removing WhatsApp contacts: send the status DELETED and the listed contacts are marked deleted, in one call, for as many identifiers as you pass it. That makes it the right tool for honouring a data erasure request and the wrong tool to hand an unattended agent, because the danger is never the action. It is the filter that produced the list. A search that matched contacts on the wrong channel, or on a last-seen window off by a month, deletes people you still need to reach and gives you no way to tell which ones they were.
So the agent gates the query, not the click. It runs Search Inbox Contacts, then stops rather than piping the result straight into Update Contact Status. What it posts to the data owner is the case for the change: the filter written out in words, the number of contacts it matched, and a sample of those records showing the channel and last-seen date on each. The status about to be applied is stated in the same message. The question is "does this filter describe the people you meant?" and it goes to the person who owns the erasure request, in the channel where they already work. They confirm, and the agent applies the change and logs what it touched. They correct the window, and the agent re-runs the query before anything is written. The agent does the tedious part, which is assembling and evidencing the set. The person owns the part that cannot be reversed.
Agent Capabilities
8 actionsContacts
4- Search Inbox Contacts Retrieves contacts from the inbox with the full set of platform filters: free-text search, tags, lifecycle status, segments, online state, assigned agent, whether the contact has interacted or ordered, and the channel they arrived on, covering website, WhatsApp, Telegram and Facebook. Creation and last-seen date ranges are supplied as objects so an exact window can be requested. This is the action that defines an audience.
- List Segments Returns every segment configured on the account. Segments are the saved audience groups used to target broadcasts and drip campaigns, and their identifiers are what the contact search expects in its segments filter.
- Import WhatsApp Contacts Creates or updates WhatsApp contacts from a list of profiles, each carrying a display name, email address and a phone number split into country prefix and subscriber number, and optionally seeded with tags and custom attributes. Because the endpoint upserts, it is safe to re-run on a schedule when syncing from a CRM.
- Update Contact Status Sets the status of one or more inbox contacts in a single call. Sending the status DELETED marks the listed contacts as deleted, which is the documented way to remove WhatsApp contacts. Subscriber identifiers may be supplied alongside the contact identifiers when the contacts have associated subscriptions.
- List WhatsApp Templates Returns every WhatsApp template on the account with its current Meta approval status, category, language and full component configuration. Only approved templates can be sent, which makes this the natural pre-flight check before any campaign or notification flow.
- Send WhatsApp Template Message Sends an approved template through the WhatsApp Cloud API. The recipient number must include the country code without a leading plus sign, and template variables are supplied through a parameters list mirroring the Cloud API component structure, including header media such as documents and images. Templates with no variables take an empty list.
- Send WhatsApp Text Message Sends a plain text WhatsApp message. WhatsApp only permits free-form text inside an open customer service window, so this continues a live conversation rather than starting one.
- Send WhatsApp Media Message Sends an image or document by public URL with an optional caption. The media URL must be reachable by WhatsApp's servers, and the same customer service window rule applies as for plain text.
Triggers
1 triggersEvent Triggers
1- On New Inbox Contact Fires when a new contact appears in the inbox, emitting the raw contact record. Monitoring can be narrowed to a single segment or to contacts carrying particular tags, so a flow can watch one campaign's intake rather than the whole inbox. The first poll establishes a baseline without firing, which means pre-existing contacts are never replayed into a live workflow. Polling interval is configurable with a 30 second minimum.
Frequently Asked Questions
What can FlowRunner do with EleAPIs?
FlowRunner agents can run Search Inbox Contacts, List Segments, and Import WhatsApp Contacts in EleAPIs, plus 5 more actions.
Does connecting EleAPIs to FlowRunner require OAuth?
No. EleAPIs connects to FlowRunner with an API key, no OAuth flow required.
Can EleAPIs trigger a FlowRunner workflow automatically?
Yes. EleAPIs supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with EleAPIs
$100 in credits. No card required. Connect in minutes.