Aunoa
MessagingSend approved WhatsApp and RCS message templates and pull dashboard reporting from Aunoa, the Spanish conversational AI platform. Agents deliver templated customer messages and read engagement results back.
What This Integration Enables
Aunoa is built for teams whose WhatsApp traffic is notification rather than conversation. There is no free-form send in this connector and no inbound trigger, and that is not an omission. The platform's whole shape assumes governed, approved, one-way delivery at volume: templates that Meta has cleared, parameters declared up front, dashboards afterwards to prove the batch landed. If your requirement is a two-way support inbox, this is the wrong connector in the catalog. If your requirement is that ten thousand order confirmations go out tonight and that every one of them is auditable, it is the right one.
Two details shape how agents work with it. Aunoa covers RCS alongside WhatsApp, which very few connectors in this catalog do, and the sending channel is selected per recipient with WhatsApp as the default when the field is left empty. And Send Template will not deliver a message when the recipient profile is missing any parameter the template declares. It does not fail loudly; that recipient simply does not receive anything. An agent that reads Get Template first and compares the declared parameter names against the batch turns a silent gap into a visible one, which is the difference between an automation you can trust at volume and one you find out about from a customer.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A delivery notification batch that cannot silently drop a row
Fulfilment closes for the day in ShipBob and the agent assembles tonight's notification batch: one recipient per shipment, each with a tracking number, a carrier and a delivery window. Before it sends anything it calls Get Template and reads the parameter names the approved template currently declares. It then checks every recipient row against that list. Rows that carry all the declared values go into the approved batch. Rows missing one, usually because a carrier handed back a shipment with no tracking reference yet, go into a separate list with the specific field named. Send Template delivers the first list. The second list reaches a person while there is still time to chase the carrier, rather than being discovered as a support ticket three days later.
One notification flow, two channels
An appointment reminder needs to reach customers on whichever channel their number supports. The agent calls List Channels and reads back the channel types configured on the bot and the sender identity each one uses. It builds one recipient list per channel, resolves the recipient identifier that each channel expects, and calls Send Template once per group. The message text is the same approved template in both cases. The routing decision lives in the flow rather than in three parallel copies of a campaign, and adding a channel later means the agent picks it up from List Channels rather than someone rebuilding the send.
A dashboard metric that raises its hand
Aunoa's reporting is a real API surface rather than a screen you visit. On a schedule, the agent calls List Reports to resolve the report identifier, then Download Report for yesterday, which comes back base64 encoded with its byte length, and writes the file to Amazon S3 as the archive of record. It then calls Get Widget Data for the conversation volume widget over a rolling window with the timezone set to the market the report covers, and compares the result against the prior period. A drop past the threshold posts to the operations channel in Slack with the numbers attached. The report stops being something someone remembers to open.
Human-in-Loop Highlight
The gate on this connector sits on the parameter diff, not on the wording. Aunoa's Send Template accepts many recipients in one call, each with their own parameter values, and any recipient whose profile is missing a value the template declares is not delivered to. Nothing throws. So the agent does the work a person cannot do at batch scale, calling Get Template to read the current parameter list and checking every row against it, then stops and posts the result: "Tonight's shipment batch is 4,120 recipients. 37 are missing the tracking_number parameter this template declares and will not be delivered if I send now. Send the 4,083 complete rows and hold the rest, send everything, or hold the whole batch?" A person answers in Slack and the flow resumes on that answer. This is the human-in-the-loop moment that matters for a send-only channel: the decision is not whether the copy reads well, it is what to do about the recipients the platform would quietly skip.
Agent Capabilities
7 actionsChannels and Templates
3- List Channels Returns the messaging channels configured on the Aunoa bot, each with its channel type, display name and the sender identity messages will originate from. Agents call it to confirm which channels are live before a send and to resolve the recipient identifier a given channel expects.
- List Templates Returns the approved templates available on a channel, each with its keyword, whether it takes parameters and the names of those parameters. Used to discover what the account can currently send without reading it out of a console.
- Get Template Returns a single template by its full name, reporting whether it takes parameters and which parameter names it expects. This is the validation step an agent runs immediately before building a send, so the batch is checked against the template as it exists now rather than as it existed when the flow was built.
Sending
1- Send Template Sends an approved template to one or more recipients, each with their own parameter values. This is how Aunoa delivers outbound WhatsApp and RCS notifications. Every parameter the template declares must be present for a recipient or that message is not delivered, and the recipient field selects which configured channel sends the message, defaulting to WhatsApp when omitted.
Reporting
3- List Reports Returns the dashboard reports defined for a bot with their identifiers, names, types and creation times. The identifier returned here is what the other two reporting operations expect, so agents call it first when building any reporting workflow.
- Download Report Downloads a generated report for a single day as a binary file, returned base64 encoded with its byte length, ready to be written to storage or attached to an email. The date is supplied as YYYYMMDD and must match a day the report was produced for.
- Get Widget Data Returns the data behind a single widget of a dashboard report over a date range, so one metric can be pulled into a flow without downloading the whole report. The timezone is an IANA name such as Europe/Madrid and determines how days are bucketed.
Frequently Asked Questions
What can FlowRunner do with Aunoa?
FlowRunner agents can run List Channels, List Templates, and Get Template in Aunoa, plus 4 more actions.
Does connecting Aunoa to FlowRunner require OAuth?
No. Aunoa connects to FlowRunner with an API key, no OAuth flow required.
Can Aunoa trigger a FlowRunner workflow automatically?
Aunoa doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Aunoa
$100 in credits. No card required. Connect in minutes.