> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/e-commerce/woocommerce/woocommerce-setup.md). # Set up WooCommerce WooCommerce setup for your AI agent, screen by screen: create a REST API key in WooCommerce, copy the consumer key and secret, and connect it to eesel. Connecting WooCommerce to eesel, screen by screen. You create a REST API key in your WordPress admin, and WooCommerce gives you a **consumer key** and a **consumer secret**. You paste those two values, plus your store domain, into the connection window in eesel. You do it once. For what your agent does with the store, see [AI agent for WooCommerce](/integrations/e-commerce/woocommerce.md). ## Before you begin * You need an **administrator** account on your WordPress site, so you can reach **WooCommerce > Settings > Advanced**. * Have your store's domain ready, for example `store.example.com`. * Keep the eesel dashboard open in another tab. The connection window asks for the key straight after you create it. ## Walkthrough {% stepper %} {% step %} ### Open WooCommerce settings Sign in to your WordPress admin. In the left sidebar open **WooCommerce**, then click **Settings**.

The WooCommerce Home screen in WordPress admin with a callout on Settings under WooCommerce in the left sidebar — WooCommerce in the WordPress admin sidebar, with Settings highlighted.

{% endstep %} {% step %} ### Open the REST API keys Click the **Advanced** tab at the top of the settings page.

The WooCommerce Settings page on the General tab, with a callout on the Advanced tab — The Advanced tab in WooCommerce Settings.

Under **Advanced**, click **REST API keys**.

The Advanced tab showing Page setup, with a callout on the REST API keys link — The REST API keys link under the Advanced tab.

{% endstep %} {% step %} ### Add a key for eesel Click **Add key**. Any keys you already have are listed below it.

The REST API list in WooCommerce with existing keys and a callout on the Add key button — The REST API keys list, with the Add key button.

Give the key a description you will recognise later, such as `eesel`. Leave **User** as an administrator account, and set **Permissions** to **Read/Write**.

The WooCommerce Key details form with callouts to add a description and to set Permissions to Read/Write — The Key details form.

**Read** is enough if you only want order and customer lookups. Your agent needs **Read/Write** to add order notes, change an order's status or record a refund. Granting write access does not turn those actions on. You choose that later, per action. Click **Generate API key**.

The Key details form filled in with the description eesel key and Read/Write permissions, with a callout on Generate API key — The form filled in, ready to generate the key.

{% endstep %} {% step %} ### Copy the consumer key and secret WooCommerce shows your new **Consumer key** and **Consumer secret**. Copy both. They start with `ck_` and `cs_`.

The API key generated screen in WooCommerce with the consumer key, consumer secret and QR code blurred, and callouts on the two Copy buttons — The generated key. Both values are blurred here.

{% hint style="warning" %} Copy both values before you leave this page. WooCommerce hides the consumer secret once you navigate away. If you lose it, revoke the key and create a new one. {% endhint %} {% endstep %} {% step %} ### Paste them into eesel In the eesel dashboard, ask the chat to connect WooCommerce and open the link it gives you, or click **Connect** on the WooCommerce page under **Integrations**. A connection window asks for three things: * **Key:** the consumer key, starting `ck_` * **Secret:** the consumer secret, starting `cs_` * **Domain:** your store domain, for example `store.example.com`

The connection window with masked Key and Secret fields, a Domain field reading the store domain, and a Continue button — The connection window, with the key and secret masked.

Click **Continue**. The window confirms the account is connected.

The connection window saying Successfully connected your WooCommerce account, with a Continue button — The connection is done.

The connection window is run by Pipedream, the service eesel uses to hold the connection. You do not need a Pipedream account of your own. **Check it worked.** The WooCommerce page under **Integrations** reads **Connected**. From a terminal, `eesel status` lists WooCommerce as connected. {% endstep %} {% endstepper %} ## Troubleshooting

The connection window says the key is invalid

* Check you pasted the consumer key into **Key** and the consumer secret into **Secret**. They are easy to swap. * Check the **Domain** is your store's domain with no path, for example `store.example.com`. * Make sure the key has not been revoked. It shows under **WooCommerce > Settings > Advanced > REST API** while it is active.

Lookups work, but notes, status changes or refunds fail

The key was created with **Read** permission. Edit it under **REST API keys** and set **Permissions** to **Read/Write**, or create a new key with Read/Write and reconnect.

I lost the consumer secret

WooCommerce shows it only once. Revoke the key under **REST API keys**, create a new one, and reconnect WooCommerce in eesel with the new pair.

## Related pages * [AI agent for WooCommerce](/integrations/e-commerce/woocommerce.md) for what your agent does with the store and the full action list * [Chat Bubble](/integrations/chat-surfaces/chat-bubble.md) for putting your agent on your storefront * [Actions and Approvals](/instructions-and-memory/actions-and-approvals.md) for choosing what your agent may do * [Integrations overview](/integrations/overview.md) for how sources, triggers and actions fit together --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eesel.ai/integrations/e-commerce/woocommerce/woocommerce-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.