Skip to content
OmniChannels.ai

E-commerce

WooCommerce + OmniChannels.ai: order updates on WhatsApp and SMS

Connect via API & webhooksConnect via MCPUpdated

In short

WooCommerce can trigger WhatsApp, SMS and RCS messages through OmniChannels.ai for order confirmations, shipping updates, COD checks and back-in-stock alerts. A webhook created under WooCommerce, Settings, Advanced, Webhooks sends order events to n8n, Make, Zapier or your own code, which then calls our REST API with your token. There is no WooCommerce plugin from us to install.

What you can do

  • Order confirmation

    When an order is created, send an approved WhatsApp template with the order number and total, or an SMS where WhatsApp is not available.

  • Shipping and fulfilment updates

    When an order moves to completed, or to a shipped status added by your shipping plugin, send the tracking link on WhatsApp.

  • Cash-on-delivery confirmation

    When a COD order is placed, ask the customer on WhatsApp to confirm. Their reply arrives on your webhook, and your automation updates the order status before dispatch.

  • Abandoned cart reminder

    If a cart-recovery plugin records abandoned carts, remind customers who opted in to marketing, using an approved WhatsApp marketing template.

  • OTP and back-in-stock alerts

    Your own code can send a one-time code at checkout or login, and a product update can notify customers who asked to hear when an item is back.

  • Ask an AI assistant

    An assistant connected to both our MCP server and your WooCommerce store, through a connector of its own, can find the orders and send the updates after you approve.

    Try asking

    “Send a WhatsApp order update to customers whose orders shipped today.”

How it connects

Connect via API & webhooksConnect via MCP

WooCommerce webhooks POST the full order or product as JSON to a delivery URL when a topic such as Order created or Order updated fires, and sign each delivery with a secret. They do not let you set our Authorization header or reshape the body, so our API cannot take them directly. Point the delivery URL at an n8n or Make webhook, a Zapier Catch Hook, or a small endpoint of your own.

That step picks the phone number, name and order fields, checks the status you care about, and calls our REST API: JSON for a single SMS, multipart/form-data for WhatsApp templates. Delivery statuses and customer replies, such as COD confirmations, come back to the one webhook URL configured on your OmniChannels.ai account.

  • Create webhooks in WooCommerce → Settings → Advanced → Webhooks
  • Route them through n8n, Make, Zapier or your own code to our API
  • Verify the webhook signature in your own endpoint
  • Approved WhatsApp templates and marketing opt-in where required
  • Statuses and replies arrive on your account's webhook URL

Set it up

  1. 1

    Request API access

    Request test access and receive an API token. Test sends go only to your own verified numbers.

    Guide: Quickstart: send your first message
  2. 2

    Prepare templates and sender IDs

    Get your WhatsApp templates approved, for example order confirmation and shipping update in English and Arabic, and an SMS sender ID approved for each destination country.

    Guide: WhatsApp Business API
  3. 3

    Create the receiving step

    Create a webhook trigger in n8n or Make, a Catch Hook in Zapier, or an endpoint in your own code, and copy its URL.

    Guide: Make and Zapier with webhooks
  4. 4

    Add the WooCommerce webhook

    In WooCommerce, open Settings, Advanced, Webhooks, add a webhook with a topic such as Order updated, paste the delivery URL and set a secret.

  5. 5

    Call the API

    Filter on the order status, map the billing phone and order fields, and send the request with your token in the Authorization header.

    Guide: SMS API
  6. 6

    Track delivery and replies

    Have your team or account admin set your webhook URL, then test with an order placed on your own verified number.

    Guide: Webhooks and delivery statuses

Vendor documentation

WooCommerce is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by WooCommerce; this page describes a connection built with WooCommerce's own MCP, HTTP or webhook features.

Example workflow

How a typical request moves from WooCommerce to your customer and back.

  1. 01

    WooCommerce webhook

    Order created or updated, sent as JSON

  2. 02

    n8n, Make, Zapier or code

    Checks status, maps fields, calls the API

  3. 03

    OmniChannels.ai API

    Sends the template or SMS with your token

  4. 04

    Customer's phone

    WhatsApp, SMS or RCS order update

  5. 05

    Status and replies

    Delivery status and COD answers go to your webhook

1. WooCommerce webhook: Order created or updated, sent as JSON 2. n8n, Make, Zapier or code: Checks status, maps fields, calls the API 3. OmniChannels.ai API: Sends the template or SMS with your token 4. Customer's phone: WhatsApp, SMS or RCS order update 5. Status and replies: Delivery status and COD answers go to your webhook

Questions

Is there an official OmniChannels.ai plugin for WooCommerce?

No. You use WooCommerce's built-in webhooks, sent to an automation tool or your own code, which then calls our API. You can also write a small custom plugin that calls the API from WooCommerce hooks.

Can a WooCommerce webhook call the OmniChannels.ai API directly?

No. WooCommerce sends its own order payload and cannot add our Authorization header or build our request body, so a step in between is needed to map the fields and make the call.

Does WooCommerce track abandoned carts?

Not out of the box. Cart-recovery plugins record abandoned carts and many can call a webhook. Send reminders only to customers who opted in, using an approved WhatsApp marketing template.

How do COD confirmations work?

You send an approved WhatsApp template asking the customer to confirm. The reply arrives as an inbound message on your account's webhook, and your automation updates the order through the WooCommerce REST API.

Get API and MCP access

Tell us your channels, countries and use case. An engineer issues test credentials and verifies your test numbers.