Authorize the Waaru app in Zapier and test one complete Zap.
Live Zapier app publication, OAuth registration, trigger subscription, and representative action testing remain part of production setup.
Use Zapier for narrow handoffs that do not need a direct provider connector. Waaru exposes two reviewed triggers and five contact or label operations, not an unrestricted API surface.
In one line
Waaru triggers Zaps from a minimized inbound WhatsApp message or a newly created contact. Zapier can find, upsert, update, label, or unlabel one approved Waaru contact.
Capability review updated .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
Platform free. AI features are paid separately.
A minimized event starts the Zap. Any return action is tenant-bound, idempotent, and limited to approved contact fields or one selected label.
Two reviewed triggers start Zaps. Approved return actions manage a contact or one selected label.
Operating boundary
The workspace authorizes the reviewed Waaru app in Zapier and tests one complete Zap.
Find one active contact by exact E.164 phone number.
Upsert or update approved fields on one contact, or apply or remove one selected label.
A minimized inbound WhatsApp message or approved new-contact event can start a subscribed Zap.
Authorize the app, subscribe the trigger, map approved fields, and test the trigger and return action together.
No raw HTTP, arbitrary webhooks, message sends, workflow commands, contact deletion, consent changes, or broadcast mutations.
Trigger delivery is duplicate-safe with bounded retry. Return actions stay tenant-bound and idempotent.
Triggers
Actions and search
When to use it
Use a direct connector when the workflow needs current order, payment, calendar, CRM, file, or shipment state. Use Zapier when one approved event or contact update needs to reach a supported app outside that direct set.
Current boundary
The connector does not provide raw HTTP, arbitrary webhooks, Logic Flow starts, Event Automation commands, session or template sends, contact deletion, consent changes, restriction clearing, or broadcast mutation.
Yes. The instant trigger sends a minimized inbound-message event for one authorized WhatsApp connection.
Yes. A contact created through an approved creation path can produce the second supported trigger.
It can upsert or update approved fields on one contact and apply or remove one selected contact label.
No. Session sends and template sends are not part of the current external action surface.
No. External commands that start Logic Flows or Event Automations remain outside the connector until their authorization boundary is separately approved.
Research notes
Primary Zapier references for REST Hook triggers and integration review.
Zapier documents REST Hook trigger subscription and unsubscribe behavior.
Zapier Platform documentation · Accessed 13 August 2026
Zapier publishes integration build guidelines for public app review.
Zapier Platform documentation · Accessed 13 August 2026
Ready to ship a WhatsApp flow that doesn't break?
Public signup is open. The platform is free. AI features are paid separately.
