Avisa API
MessagingConnect AI agents to Avisa API, a Brazilian gateway that links a WhatsApp account to your automations. Agents send text, media, and interactive messages, manage groups and communities, validate numbers, and react to inbound messages so WhatsApp conversations run inside governed workflows.
What This Integration Enables
Avisa API is a Brazilian gateway that links a WhatsApp account to your automations, and what it is built around is the interactive message. Alongside ordinary text and media it sends lists, quick reply buttons, media buttons, carousels, location requests and Pix buttons, which means a conversation can carry a choice and a payment rather than only words. For a Brazilian sales or service team that is not a nice-to-have. It is the difference between a thread a person has to read and a thread a flow can act on. Access is outside Meta's official Cloud API, and connected accounts remain subject to WhatsApp's terms.
Around that sit the practical parts. Number validation runs domestically and internationally before a send is spent, groups and communities carry full administration, and chat labels and disappearing-message timers keep threads organized. Contacts, identifier resolution, the WhatsApp Business catalog, image status posts and an asynchronous send path with its own status read complete the surface. One trigger delivers inbound messages, and it is the only one, because messages are the only event this platform delivers to a webhook. That single fact shapes how the connector should be operated, and it is the subject of the gate below. Agents run the conversation, the validation and the follow-up. Humans keep the decisions that would be invisible if they went wrong.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A quote that closes inside the thread
An inbound lead messages the business number. New Message Received fires. The agent calls Check Number to confirm the account is live, looks the person up in Pipedrive, and answers with Send List Message offering the three configurations that fit what they asked for. The customer picks one. The agent confirms the price, sends the spec sheet with Send Document, and attaches the amount with Send Pix Button. When payment clears, the deal moves and the confirmation goes out with Send Text Message. Nobody typed a price into a chat window, and the choice the customer made is a value in the flow rather than a sentence someone had to interpret.
A customer community that stays clean
A regional customer community runs as a set of linked WhatsApp groups. The agent creates groups with Create Group, links them with Add Groups To Community, and keeps membership aligned with the subscriber list using Update Group Participants. Where a group is used for announcements it is set to Set Group Admin Only so it reads as a channel rather than a chat. Chat labels applied with Add Chat Label mark which threads have an open ticket, so the human team's own WhatsApp view shows the queue without anyone maintaining a second list. Community removal is proposed rather than executed, because being removed from a customer community is something the customer notices.
Validating before spending the send
An outbound list arrives from Google Sheets. Before anything is dispatched, the agent runs Check Number across the domestic entries and Check International Number across the rest, and splits the list into reachable, not on WhatsApp, and malformed. Reachable numbers get a Send Text Message Asynchronously call, with Get Asynchronous Message Status confirming what actually left. Numbers with no WhatsApp account are routed to another channel rather than counted as unresponsive, and malformed entries are written back to the source with the specific problem, so the list improves instead of being re-imported unchanged next month.
Human-in-Loop Highlight
Avisa API holds exactly one webhook URL for the whole account, and the New Message Received trigger is sitting in it. Set Webhook replaces whatever is registered there, including the callback that trigger registered for itself, and the trigger's own cleanup only clears the slot when it still matches the URL it set. Messages are also the only event this platform delivers, so that one registration is the entire inbound path. Repoint it and the flow does not error, does not retry and does not warn. It just stops hearing from customers, and the first evidence is a customer complaining they were ignored.
So Set Webhook is the one action in this connector an agent never calls unattended, even though it is a two-field configuration write that looks like the least consequential thing on the list. When a flow is asked to point Avisa at a new endpoint, perhaps because a new tool is being wired up, the agent reads Get Webhook first and reports what it found: "Set Webhook was requested for the new analytics endpoint. The slot currently holds the callback for the New Message Received trigger on flow whatsapp-inbound, which is the only inbound path on this account and has handled 1,180 messages in the last week. Replacing it silences that flow with no error raised anywhere. Point analytics at a fan-out from the existing flow instead, or accept the swap?" A person decides. This is the digital andon cord pointed at the agent's own senses rather than at a customer-facing action: the most dangerous write on a connector is not always the one that reaches a customer, it is sometimes the one that quietly disconnects the thing that was listening for them.
Agent Capabilities
58 actionsMessaging
8- Send Text Message Sends a text message to a number or group. Numbers are digits only including country and area code, with no plus sign or formatting.
- Send International Text Message Sends a text message to a number outside Brazil, where the numbering rules differ.
- Send Text Message Asynchronously Queues a text message and returns immediately, for flows that cannot block on the send.
- Get Asynchronous Message Status Reports what happened to an asynchronous send. The read that turns a queued call into a confirmed one.
- Edit Message Edits a message already sent, within the window WhatsApp allows.
- Delete Message Deletes a message that was sent in error.
- React To Message Adds an emoji reaction, which acknowledges receipt without adding a message to the thread.
- Mark Messages As Read Marks inbound messages as read, which is what tells the customer the thread has been picked up.
Media
8- Send Media From URL Sends a file from a publicly reachable URL, which is the simplest path when the file already lives somewhere addressable.
- Send Image Sends an image supplied as base64 data.
- Send Document Sends a document such as an invoice, a contract or a boleto, supplied as base64 data.
- Send Audio Sends audio as a base64 payload.
- Send Link Preview Sends a link with its preview card rendered rather than a bare URL.
- Send Location Sends a coordinate with an optional label.
- Send Contact Sends a contact card, which is how a customer gets the right person's details without retyping a number.
- Download Media Decrypts and downloads media from a received message using the values carried on the inbound payload. The step that turns a customer's photographed document into a file the rest of the flow can work with.
Interactive Messages
7- Send List Message Sends a selectable list, which suits more options than buttons allow. The reply comes back as a chosen value rather than free text.
- Send Template Message Sends a templated message.
- Send Quick Reply Buttons Sends up to a handful of tappable replies. The fastest way to turn an open question into a branch the flow can act on.
- Send Media Buttons Sends buttons attached to a media item, supplied as base64 data.
- Send Carousel Message Sends a carousel of cards, for presenting several options with images side by side.
- Send Pix Button Attaches a Brazilian Pix payment key to the message, so payment happens inside the conversation rather than on a page the customer has to be sent to.
- Send Location Request Button Asks the customer to share their location, which is how a delivery or service address gets captured accurately instead of transcribed.
Instance
3- Get Instance Status Reports whether the connected WhatsApp instance is logged in. The first read of any flow that must not queue work against a dead session.
- Request QR Code Requests the pairing QR code, which is how a session is connected or reconnected. Configure the webhook before calling it.
- Disconnect Instance Ends the live WhatsApp session. The number stops sending and receiving until someone pairs it again.
Integration Users
3- Create Integration User Creates a platform user. Requires the separate integrator token and a Pro plan or above.
- List Integration Users Lists platform users on the integrator account.
- Delete Integration User Removes a platform user.
Validation
2- Check Number Confirms a Brazilian number holds an active WhatsApp account before a send is spent on it.
- Check International Number Does the same for numbers outside Brazil.
Groups
9- List Groups Lists the groups the instance belongs to.
- Get Group Info Returns one group with its metadata and participants.
- Send Group Text Message Sends a text message to a group rather than a number.
- Create Group Creates a group seeded with participants.
- Update Group Participants Adds, removes, promotes or demotes group participants.
- Set Group Name Changes the group subject.
- Set Group Description Changes the group description.
- Set Group Admin Only Restricts posting to admins, which turns a group into an announcement channel without dissolving it.
- Set Group Photo Sets the group image from base64 data.
Communities
3- Create Community Creates a WhatsApp community.
- Add Groups To Community Links existing groups into a community.
- Remove Groups From Community Unlinks groups from a community. Members notice, so treat it as a customer-visible change.
Chats
5- Archive Chat Archives a chat, clearing it from the active view without deleting anything.
- Set Chat Presence Shows a typing or recording indicator before a longer reply lands.
- Set Disappearing Message Timer Sets how long messages persist in a chat.
- Add Chat Label Applies a label to a chat, which is how an agent writes its state into the view the human team already uses.
- Remove Chat Label Removes a label from a chat.
Contacts
5- List Contacts Lists the contacts on the connected account.
- Add Contact Saves a contact to the connected account's address book.
- Remove Contact Removes a saved contact.
- Get Contact Avatar Returns a contact's profile image.
- Resolve LID Resolves the identifier WhatsApp uses in groups and privacy-restricted contexts back to something the rest of the flow can act on.
Status and Catalog
3- Publish Image Status Posts an image status from the connected account. It reaches the account's contacts rather than a named recipient, so treat it as publishing.
- List Catalog Products Lists the WhatsApp Business catalog products.
- Get Catalog Product Returns one catalog product.
Webhook
2- Get Webhook Returns the URL currently registered on the account. Always read this before writing, because there is exactly one slot.
- Set Webhook Registers the account's single webhook URL. It replaces whatever is there, including a callback registered by the New Message Received trigger, which is why this action belongs to a person rather than to an agent.
Triggers
1 triggersEvent Triggers
1- New Message Received Fires when the connected WhatsApp instance receives a message. The event carries the chat and sender identifiers, the message identifier and timestamp, and the message body, with text read from the extended text field and location messages exposing their coordinates. Every other message type is available in full on the untouched message object, so a field the mapping does not name is still reachable. Optional filters narrow delivery to direct chats or group chats, to a single chat, and can exclude messages the instance itself sent. This is the only trigger the platform supports, because messages are the only event Avisa API delivers to a webhook.
Frequently Asked Questions
What can FlowRunner do with Avisa API?
FlowRunner agents can run Send Text Message, Send International Text Message, and Send Text Message Asynchronously in Avisa API, plus 55 more actions.
Does connecting Avisa API to FlowRunner require OAuth?
No. Avisa API connects to FlowRunner with an API key, no OAuth flow required.
Can Avisa API trigger a FlowRunner workflow automatically?
Yes. Avisa API supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Avisa API
$100 in credits. No card required. Connect in minutes.