Can Lyro send WhatsApp messages through Waboxapp?

No. This toolkit is inbound only - both actions it exposes, Receive Incoming Waboxapp Message Event and Waboxapp Webhook ACK Event, handle payloads that Waboxapp posts to your endpoint rather than calls Lyro initiates. Lyro replies to the customer over the channels it sends on directly, WhatsApp among them, while Waboxapp supplies the inbound event and its delivery status.

What has to be configured before Lyro sees a Waboxapp event?

A webhook URL on the Waboxapp side. Both actions are webhook handlers, so nothing reaches Lyro until Waboxapp is pointed at an endpoint. The acknowledgment handler then validates the token on each payload before processing it, so anything that fails that check is discarded rather than acted on.

What is the difference between the message event and the ACK event?

The message event carries a new inbound WhatsApp message as a POST form payload. The acknowledgment event carries a status change on a message that already exists, delivered or read, which is how Lyro tells "a customer just wrote in" apart from "an earlier message reached them".

How is this different from wiring Waboxapp into Zapier or Make?

Those tools run one predefined path per trigger. Lyro receives the same Waboxapp webhook payload inside an open conversation and decides what to do with it in context - answer the customer, or hand the thread to a human agent with the full history attached when it cannot resolve it.

Waboxapp MCP integration

Receives real-time WhatsApp message events and processes the deliver and read acknowledgments that follow, validating the webhook token on each payload.

Connect Waboxapp See all integrations

2actions available

What your agent can do with Waboxapp

Every action runs live through MCP. Nothing to build, nothing to maintain.

Process incoming message acknowledgment events.

See all 2 actions

How businesses use Waboxapp + Lyro

Each card is one request a support team gets, and the Waboxapp actions Lyro runs to close it.

Catch inbound WhatsApp messages and their delivery state
Lyro handles the form payloads Waboxapp posts to your webhook, so a new customer message and the deliver or read acknowledgment that follows it are both picked up the moment they fire.
Receive Incoming Message EventWaboxapp Webhook ACK Event

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Waboxapp actions it has and picks the ones a request needs.

01
Connect Waboxapp
Authorize the Waboxapp account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Waboxapp actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Waboxapp · Lyro

Everything else about Waboxapp

Setup, permissions, and the limits of what Lyro can do inside Waboxapp.

No. This toolkit is inbound only - both actions it exposes, Receive Incoming Waboxapp Message Event and Waboxapp Webhook ACK Event, handle payloads that Waboxapp posts to your endpoint rather than calls Lyro initiates. Lyro replies to the customer over the channels it sends on directly, WhatsApp among them, while Waboxapp supplies the inbound event and its delivery status.

Every action available in Waboxapp

All 2 actions your agent can call on Waboxapp, straight from the live MCP connection.

Waboxapp webhook ack event
Process incoming message acknowledgment events.
Receive incoming waboxapp message event
Receive real-time incoming WhatsApp message events via webhook.