A WooCommerce connection reaches your store through WooCommerce's own REST API, at your site's address. Bizomate keeps the site address and a REST API key — its consumer key and consumer secret — and calls your store with them.
Who can do this
Workspace Admins and Editors, on any plan — WooCommerce is not a premium connection. Viewers see the connection but cannot add or change it.
On WordPress's side, an Administrator or Shop manager, who can make REST API keys.
Before you start
- Your store on https. The key goes with every call, so Bizomate only sends it over https — an
http://address is refused. - Pretty permalinks. WooCommerce's REST API lives at
/wp-json/, which WordPress only answers when Settings › Permalinks is set to anything other than Plain.
Steps
In WordPress, make the key:
- Sign in to your WordPress admin and select WooCommerce, then Settings.
- Select the Advanced tab, then REST API.
- Select Add key (or Create an API key if there are none yet).
- In Description, type Bizomate.
- In User, choose an Administrator or Shop manager. The key can do what that person can.
- In Permissions, choose Read/Write. With Read only, every step that changes something is refused.
- Select Generate API key.
- Copy the Consumer key (it starts
ck_) and the Consumer secret (it startscs_). WooCommerce shows the secret only once.
In Bizomate, add the connection:
- Select Connections in the bar at the top, then + Add connection.
- Under Commerce, select WooCommerce. It reads "Stored credential".
- In Connection name, type a name — for example Northwind shop.
- In Site address, type your store's address — https://shop.northwind.example. If WordPress lives in a folder, include it: https://northwind.example/shop. Typed without
https://, Bizomate adds it. - Paste the key in Consumer key — WooCommerce › Settings › Advanced › REST API › Add key, with Read/Write.
- Paste the secret in Consumer secret — Shown once, beside the key. It is hidden as you type.
- Leave Test the connection before saving ticked. Bizomate asks the store for its status before keeping the details.
- Select Save connection. The button reads Testing, then the dialog closes.
The toast "Connection added" says "“Northwind shop” is ready. Every workflow in this workspace can use it."
What happens next
- WooCommerce steps list it under Connection: products, stock, orders, order notes, customers and coupons.
- WooCommerce triggers can use it — four store events that start a run when they happen.
- Test in the connection's panel answers "Reached", the store's name or address, and the WooCommerce version — for example Reached shop.northwind.example · WooCommerce 9.3.3.
Good to know
- Read/Write is needed. The test only reads, so a Read key passes it and then fails at the first step that changes something, and when publishing a workflow with a WooCommerce trigger.
- A new key. If you revoke the key in WooCommerce, every WooCommerce step fails. Make a new one, then in Bizomate open the connection's panel, select Revoke and Revoke connection, then Reconnect, fill in every field again and select Reconnect.
- Security plugins and firewalls on the site can block calls from outside. If the store works in a browser but Bizomate cannot reach it, check that the site allows requests to
/wp-json/wc/v3.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| "Fill in Site address." / "Fill in Consumer key." / "Fill in Consumer secret." | A box is empty. | Fill it in. |
| WooCommerce refused it — "Site address “…” is not an https address — WooCommerce's REST API key must travel over https. Nothing was saved." | The address starts http://, or is not a whole address. |
Use the store's https:// address. If the site has no certificate, set one up first. |
| WooCommerce refused it — "WooCommerce refused: Consumer key is invalid. Check the connection's details on Connections. Nothing was saved." | The key is wrong or was revoked. | Copy the key again, or make a new one. |
| WooCommerce refused it — "WooCommerce refused: Sorry, you cannot list resources. Check the connection's details on Connections. Nothing was saved." | The key's user cannot manage WooCommerce, or the web server drops the sign-in on the way. | Make the key for an Administrator or Shop manager. If it still fails, ask your host to pass the Authorization header to WordPress. |
| WooCommerce refused it — "WooCommerce refused: No route was found matching the URL and request method. Nothing was saved." | Permalinks are set to Plain, or the address is not the WordPress site. | Change Settings › Permalinks in WordPress, and check the address. |
| "WooCommerce refused: Sorry, you are not allowed to create resources. …" in a run | The key is Read only. | Make a Read/Write key and reconnect. |
| "Could not reach WooCommerce: …" or "WooCommerce did not answer within 30 seconds." | The site could not be reached, or is slow. | Check the site is up, then try again. |