WooCommerce integration

WhatsApp for your WooCommerce store with the webhooks it already ships with

Omnifox doesn't have an extension in the WooCommerce Marketplace yet, so there's no "install" button from your WordPress dashboard. What does exist, and works today: WooCommerce ships native webhooks for order created and updated, and with n8n or our API you turn those into a WhatsApp message for order confirmation, a status change, or an abandoned cart.

7 days free. No credit card.

0
Omnifox extensions to install on your WooCommerce
Nativos
the order webhooks WooCommerce already ships with out of the box
n8n o API
to resolve the contact and send the WhatsApp message
First, some honesty

What exists today between Omnifox and WooCommerce

WooCommerce is a WordPress plugin, not a separate platform, and you won't find an Omnifox extension in its Marketplace: it doesn't exist yet. We'd rather tell you here than have you spend half an hour looking for it in your dashboard.

What does exist, out of the box, is WooCommerce's webhook system: in Settings → Advanced → Webhooks you set up an alert for "order created" or "order updated", with a secret to sign each delivery, and WooCommerce fires it on its own every time it happens. The connection point with Omnifox isn't a button, it's that URL you point it at.

To turn that webhook into a WhatsApp message, there are two real paths. If your customer already has an open conversation with you (they messaged you before over WhatsApp, say), a flow with Omnifox's native "Incoming webhook" trigger and the "Send template" node is enough. If it's a new customer who never messaged you — the more common case in a store — you need to resolve their contact from the order's phone number: the official Omnifox node in n8n does that, or our REST API called from your own backend. WooCommerce won't let you add an authorization header to its webhooks, so pointing straight at the API with nothing in between doesn't work; n8n solves that by storing the credential inside the node.

For pre-purchase questions, the webchat widget installs on the same WordPress site with a <script> tag, no plugin needed: that's the sister WordPress integration, with its own step-by-step. Here we stick to the store and its orders.

In one sentence

No extension in the WooCommerce Marketplace, but a real path: native order webhooks, plus n8n or the API to resolve the contact and alert over WhatsApp.

  • Order created/updated webhooks: already built into WooCommerce
  • New customer: n8n resolves the contact by phone number, or your own backend with our API
  • Customer who already messaged you: Omnifox's native flow is enough on its own
  • Messages the business initiates need a Meta-approved template
What you can alert on

What you can actually automate between WooCommerce and WhatsApp

Real use cases, buildable with what already exists today — no promises that fall apart on the first test order.

Order confirmed

As soon as WooCommerce marks the order as paid, your webhook fires a WhatsApp template with the order number and what they bought, without anyone typing it by hand.

Abandoned cart

WooCommerce doesn't have its own "abandoned cart" event, but it does create the order in pending-payment status as soon as checkout begins. A wait node lets a few minutes pass, and if it's still pending, the WhatsApp reminder goes out.

Order status changes

Processing, shipped, delivered, or cancelled: each change can send a WhatsApp alert instead of the customer opening another tab to track the order.

Everything in the same conversation

The order alert lands on the same contact record that already holds their WhatsApp, Instagram, or website chat history: same customer, same thread, same team.

Pre-purchase questions

The webchat widget on your WordPress lets you answer size, stock, or shipping questions before the visitor reaches checkout, with AI or with your team. It's installed separately, on the WordPress integration page.

Without risking your number

Every message the business sends to open a conversation uses a Meta-approved template: the system blocks the send if the template isn't approved, so there's no way to accidentally send spam.

How it connects today

From a WooCommerce order to a WhatsApp message, step by step

The path changes a bit depending on whether the customer had already messaged you or is new. Here's the full version.

1

Turn on the webhook in WooCommerce

WooCommerce → Settings → Advanced → Webhooks → Add webhook. Pick the topic ("Order created" or "Order updated"), paste the delivery URL, and save the secret WooCommerce generates to sign each delivery.

2

Register your WhatsApp template

The message that opens the conversation ("your order was confirmed") has to be a Meta-approved template. You create it from Omnifox and wait for approval, which usually takes anywhere from minutes to a day. The send is blocked if the template isn't approved.

3

Resolve the contact by phone number

With n8n: the official Omnifox node has Contact → Find or create (by phone) and Conversation → Find or create, chained together. With your own API: the same two steps, POST /contacts/upsert and POST /conversations/find-or-create, called from a backend that adds your credential — WooCommerce doesn't let you set that header on the webhook directly.

4

Send the template

With the conversation already resolved, the "Send template" node (in n8n or via POST /conversations/{id}/templates/send) sends the WhatsApp message. For an abandoned cart, add a "Wait" node first, set to however many minutes you want to give before writing.

The real state of this integration

What exists today and what's missing

No "connect with one click" promises that don't exist, and no hiding what actually works.

There's no Omnifox extension in the WooCommerce Marketplace

It isn't published there or in any other extension directory. It's on the roadmap. Today the connection is built with WooCommerce's native webhooks, not an install button.

There's no WooCommerce-specific node

Neither Omnifox's flow editor nor our n8n node has a WooCommerce-specific block. It's built with generic pieces: Incoming webhook, Wait, Find or create contact, Find or create conversation, Send template.

The direct webhook-to-"Send template" path only works for customers who already messaged you

The native "Incoming webhook" trigger doesn't carry the customer's contact record on its own, only the order's JSON. If that person already has an open conversation in Omnifox, the flow finds it on its own. If it's their first time showing up, you need to resolve their contact by phone number with n8n or the API before you can write to them.

WooCommerce doesn't have a native abandoned-cart event

What exists is the order sitting in pending-payment status as soon as checkout starts. The reminder is built by combining that status with a wait node, not with an "enable abandoned carts" switch.

WooCommerce's webhook doesn't support a custom authorization header

WooCommerce's webhook form has no field to add that header, and our API requires it on every request. That's why the recommended path goes through n8n, which stores the credential inside the node, or through your own backend in the middle.

Every template needs Meta's approval

Order confirmed, abandoned cart, or status change: all three are messages the business initiates, so they need a Meta-approved template. The send is blocked in the code itself if the template still isn't approved.

If the extension published in the WooCommerce Marketplace is what's holding you back, write to us: knowing who needs it is what moves it up the roadmap.

FAQ

Frequently asked questions

No, it isn't published in the WooCommerce Marketplace yet. It's on the roadmap. Today the connection is built with WooCommerce's native webhooks pointing at n8n or our API.
You set up a webhook in WooCommerce → Settings → Advanced → Webhooks for the "order created" or "paid" topic, and point it at an n8n flow with the official Omnifox node (or your own backend calling our API), which resolves the contact by phone number and sends an approved WhatsApp template.
Yes, with a specific technique: WooCommerce creates the order in pending-payment status as soon as the customer starts checkout. The order-updated webhook fires the flow, a wait node lets a few minutes pass, and if it's still pending, a WhatsApp reminder goes out.
Not always. If the customer already has an open conversation in Omnifox, the native "Incoming webhook" trigger plus "Send template" is enough, no n8n needed. If it's a new customer, it's worth it: WooCommerce won't let you add the authorization header our API needs for a direct call, and the n8n node resolves the contact for you.
You need to resolve their contact from the order's phone number before you can write to them: the official Omnifox node in n8n has "Find or create contact" and "Find or create conversation" for that, or the same two steps through our REST API from your own backend.
Yes, always. Order confirmed, abandoned cart, or status change are all messages the business initiates, and WhatsApp requires a Meta-approved template for that kind of message. The system blocks the send if the template isn't approved.
That's where the webchat widget comes in — it installs on the same WordPress site with a <script> tag, no plugin needed. That's the WordPress integration page's step-by-step; this page sticks to the store and its orders.
Setting up the webhook in WooCommerce takes minutes. The WhatsApp template depends on Meta's approval, anywhere from minutes to a day. Building the flow in n8n or the API call, once the template is approved, is a matter of minutes.

Another question? [email protected]

Put WooCommerce and WhatsApp in the same inbox today

No extension in the Marketplace, but a real path: native order webhooks, plus n8n or the API to alert over WhatsApp. 7 days free, no card.

Message us on WhatsApp