Into the CRM, automatically
A new enquiry becomes a row, a card or a deal the moment it lands — with the number and the first line already filled in — instead of a note someone writes up at the end of the day, if they remember.
Point Wanova at your endpoint and seven events from your own WhatsApp Web arrive as JSON — message received, message sent, attachment, call, location, member joined, member left. Your browser posts them directly to you: no cloud in the middle, no approval process, no per-message fee.
Expert plan · posted from your machine · works while WhatsApp Web is open
Your CRM, your sheet, your ticketing tool, the channel where your team actually looks — none of them can see a WhatsApp message unless someone copies it across by hand, which means it happens for the important ones and never for the rest.
A new enquiry becomes a row, a card or a deal the moment it lands — with the number and the first line already filled in — instead of a note someone writes up at the end of the day, if they remember.
Route an incoming call or a message with the word “urgent” into your team channel. The person who needs to act isn't sitting in WhatsApp Web all day; the alert can find them where they are.
Post every event into a sheet or a warehouse and you finally have numbers: enquiries per day, response times, which campaign produced the messages. WhatsApp gives you none of this.
Paste an HTTPS URL — your own service, or a Zapier / Make / n8n catch hook — choose the events you care about, and send a test to see the exact request arrive. There's nothing to deploy on our side, because there is no our side.
Message received, message sent, attachment received, incoming call, location shared, member joined a group, member left a group. Each one is a separate switch, so a noisy group doesn't fill your automation quota with joins and leaves you didn't want.
Every event posts the same envelope — event name, timestamp, chat id, group or not — plus only the fields that event actually carries, so there are no empty keys to code around. The panel previews the exact JSON for each event before you write any handler code.
The POST is made by the extension's own background worker, browser to endpoint. Message content never passes through a Wanova server — the same reason we can't read it is the reason we can't leak it.
Webhooks are the right tool when another system has to know. But if the reason you're wiring one up is that messages go unanswered, Wanova can answer them where they are.
The AI co-pilot answers routine questions from your own product facts, in the customer's language, and refuses to invent a price. Negotiation, quotes and complaints are never auto-sent — they're handed to you.
See the AI chatbot →Who went quiet after a quote, what you promised and when — worked out from the conversations themselves, on your machine, with no integration to build.
See follow-up radar →One price per account — not per person and not per number. Every plan covers several WhatsApp numbers and as many teammates as share them. The AI co-pilot starts on Professional.
Events are posted from your browser, never through our servers · See full pricing
Seven: a message received, a message you sent, an attachment received, an incoming call, a shared location, someone joining a group, and someone leaving a group. You pick which of them fire — turning off the ones you don't need keeps your automation bill and your logs small.
No, and that's the point. The official Business API means an approved account, a provider, and a per-conversation fee before you can receive anything programmatically. Wanova reads the WhatsApp Web session you're already signed into and posts the event to your URL from your own browser — no application, no approval, no per-message pricing.
Neither passes through us. The extension's own background worker performs the HTTPS POST from your machine straight to your endpoint. Your message content never touches a Wanova server, which is also why we can't replay, queue or inspect it for you.
No. Wanova lives in your WhatsApp Web session, so events fire while that tab is open and your account is connected. Close the browser and nothing is sent — including anything that arrives while it's shut. If you need delivery that survives a closed laptop, you need the Business API, not a browser extension. We'd rather say that plainly than let you find out on a Monday morning.
A flat JSON object: a shared envelope — event name, timestamp, chat id, whether it's a group — plus only the fields that event actually carries, like the contact's number and name or the file type. The shape is fixed rather than template-editable, which is exactly what lets your handler rely on it; the panel previews the real JSON for every event, so you can write against it before you turn anything on.
Expert. Starter and Professional are the messaging and AI plans — broadcasts, scheduling, templates, keyword replies, exports, privacy tools, the AI co-pilot — and webhooks sit with the plan built for people wiring WhatsApp into other systems.
Try every feature free for 7 days. No credit card, and no Business API application.
Start free trial