Authorize Waaru from your WooCommerce store.
The store needs public HTTPS and a current WooCommerce REST API. Setup includes signed-webhook verification and a representative order lookup.
Look up the order, customer, product, or stock state a WhatsApp workflow needs. The connector receives selected store events while keeping current business actions read-only.
In one line
Waaru reads bounded WooCommerce order, customer, product, and inventory data and receives signed order, customer, and product events. It does not mutate store records.
Capability review updated .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
Platform free. AI features are paid separately.
An order or product event can start the journey. A bounded read supplies the current order or inventory state without changing the merchant's store.
WooCommerce
Order W-1842
Operating boundary
The merchant authorizes Waaru through WooCommerce application authentication on a public HTTPS store.
Current business actions do not change WooCommerce records.
Signed order, customer, and product events can continue a workflow.
Authorize the store, verify signed webhooks, and run one representative order lookup.
No changes to orders, customers, products, inventory, refunds, or coupons. Guest-customer profile synthesis is excluded.
Disconnect removes Waaru-managed webhooks. The merchant must remove the generated key in WordPress.
Order service
Fetch one order, list up to twenty recent orders, or list orders for a resolved registered customer. The response is bounded so the workflow receives the business fields it needs rather than an unrestricted store payload.
Customer matching
Find a registered customer by exact email, or resolve a phone number through bounded order data. Guest-customer profile synthesis is outside the current release.
Product questions
Fetch one product, search a bounded product set, or read the current inventory status and quantity before a workflow answers an availability question.
Events
Current boundary
Waaru does not update orders, customers, products, inventory, refunds, or coupons through this connector. Disconnect removes Waaru-managed webhooks; the merchant must also remove the generated key in WordPress because WooCommerce core does not expose REST API-key deletion.
It can read one order, recent orders, registered-customer orders, exact customer matches, products, product search results, and current inventory status.
Yes. Signed order, customer, and product events can start the relevant workflow after verification and durable acceptance.
No. Current WooCommerce business actions are read-only. Order, inventory, refund, coupon, customer, and product mutations are not exposed.
The merchant enters the public store URL, signs in to WordPress, and authorizes Waaru through WooCommerce's application-auth flow. The merchant does not paste an API key into Waaru.
The store needs public HTTPS and a current WooCommerce REST API. Production setup should verify authorization, signed webhooks, and one representative read.
Research notes
Primary WooCommerce references for REST resources and webhook delivery.
WooCommerce documents REST APIs for orders, products, customers, and related store resources.
WooCommerce developer documentation · Accessed 13 August 2026
WooCommerce documents webhooks for store events and delivery topics.
WooCommerce 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.
