How to connect a chatbot to WooCommerce orders

A regular chatbot answers questions about shipping, returns or product specs, because all of that lives in your content. It cannot answer "where is my order number 1042?" though, that information is nowhere on your website. It lives in your WooCommerce and changes by the hour.

Custom actions (beta) close that gap. They connect the assistant to the WooCommerce REST API, so it fetches the order status live and answers on its own, no operator and no plugin. This guide walks you through the setup.

What you will need

• The Pro plan or higher (works during the trial too). Custom actions are a beta feature available from Pro.
• A WooCommerce store with access to the WordPress admin.
• A few minutes. A ready-made template does most of the work for you.

Step 1: Generate WooCommerce REST API keys

WooCommerce has a built-in REST API, you just create an access key. In the WordPress admin go to WooCommerce → Settings → Advanced → REST API and choose Add key.

• Description: so you know what the key is for, for example "Breezaro chatbot".
• User: an account allowed to see orders.
• Permissions: Read is enough. The assistant never writes anything, so do not give it more.

After saving, WooCommerce shows a Consumer key and a Consumer secret. They appear only once, so copy them right away. For details on authentication see the official WooCommerce REST API documentation.

Step 2: Create the action from the template in Breezaro

In the dashboard open Custom actions and pick the Order status (WooCommerce) template from the gallery. The template prefills almost everything:

• Method and URL. GET https://your-shop.com/wp-json/wc/v3/orders/{{orderNumber}}, you only replace your-shop.com with your domain.
• Inputs. orderNumber and email. The assistant asks the customer for them on its own.
• Field selection. Only useful fields from the WooCommerce response reach the assistant (status, date, items, total, currency), not the whole technical object.

What is left is the authentication: put the Consumer key and Consumer secret from step one into a secret header. Breezaro stores them encrypted and never shows them again after saving. The steps are described right next to the template.

Step 3: Turn on the ownership check

This is the most important step, do not skip it. Without it, anyone who guesses an order number would see someone else's data.

The template has the check set up already: the customer's email must match the order's billing email. So the assistant asks for the email first, and if it does not match the order, it behaves as if the order did not exist. The customer cannot tell the difference between "wrong number" and "someone else's order", and guessing is throttled on top of that.

If you pass the order number and email straight to a different endpoint that filters on its own, test the action once with a deliberately wrong email. If the order comes back anyway, the endpoint is not filtering by it, and you should definitely keep the ownership check in Breezaro turned on.

Step 4: Test and enable

The editor has a test step. Enter a real order number and the matching email and run the test. You will see exactly the response the assistant would get, plus the result of the check. An action can only be enabled after a passing test, so a misconfigured endpoint never reaches customers.

Once the test passes, enable the action. From then on, whenever a customer asks about an order, the assistant calls WooCommerce and answers with the current status.

About security

Custom actions are designed so a misconfigured action cannot do harm:

• Read only, HTTPS only. Only GET and POST requests to public addresses are allowed; an action cannot reach your internal network.
• Keys are encrypted and never shown again after saving, not even to your team.
• The ownership check makes sure a customer only sees their own order.
• Field selection sends the assistant only what it needs, not the whole record.
• The assistant may call at most two actions per reply, and calls are rate limited, so they cannot be abused to hammer your store.

What a reply with an action costs

Every action call is billed as one extra reply at your model's credit rate. So an order-status question where the assistant calls WooCommerce costs twice a normal reply: 2 credits on a 1-credit model, 6 credits on a 3-credit model. When the customer asks about something else and no action is called, you pay nothing extra.

What's next

You connect any other system with an HTTP API the same way, custom actions are not tied to WooCommerce. For the full set of options see the custom actions documentation.

Custom actions are still in beta. If you want to try them, get in touch and we will enable them for you.