> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ocoya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect WooCommerce

> Link your WooCommerce store so publishing a product can trigger a post.

Connecting a store lets Ocoya react when you publish a product — the basis of the [WooCommerce poster workflow](/help/create-a-workflow), which turns a new product into a social post.

WooCommerce is the only ecommerce platform Ocoya connects to.

## Before you start

You need **admin access to the store**. The connection is approved inside WooCommerce itself, and only an administrator sees that screen.

The store must also be reachable over **HTTPS**. WooCommerce sends the credentials back to Ocoya over that connection and won't complete the handshake without it.

## Connect it

<Steps>
  <Step title="Open Channels">
    Select **Channels** in the left sidebar, then **Connect channel**.
  </Step>

  <Step title="Choose WooCommerce">
    It's listed under **Ecommerce** rather than with the social networks.
  </Step>

  <Step title="Enter your store URL">
    The address of the store itself — `https://yourstore.com`, not the wp-admin path.
  </Step>

  <Step title="Approve the connection in WooCommerce">
    Ocoya sends you to your own store's approval screen. Sign in as an administrator if you aren't already, and approve.
  </Step>
</Steps>

Once approved you're returned to Ocoya and the store appears under **Ecommerce** connections.

## What Ocoya asks for

<Warning>
  Ocoya requests **read and write** access to the store, not read-only. Write access is needed to create the webhook that tells Ocoya when a product is published — without it, nothing could trigger.
</Warning>

Approving it in WooCommerce creates an API key pair for Ocoya, which you can see and revoke in your store under **WooCommerce → Settings → Advanced → REST API**. Revoking it there cuts Ocoya off regardless of what Ocoya's own settings say.

## Using it

A connected store does nothing on its own — it's a trigger source for workflows. Create a workflow from the **WooCommerce poster** example to post when you publish a product.

Two behaviours to know, both from the trigger itself:

* It fires **only the first time a product goes live**. Editing a published product won't trigger it again.
* Triggering can be **delayed by up to 5 minutes**.

See [Create a workflow](/help/create-a-workflow) and [Triggers and actions](/help/workflow-steps).

## Common problems

**"The approval screen didn't appear."** Check the store URL, and that you're signed in to WordPress as an administrator. A URL with a typo, or one pointing at a staging site, fails here.

**"It connected but nothing triggers."** The workflow also has to exist and be set live. A connected store with no workflow does nothing. See [A workflow didn't run](/help/workflow-didnt-run).

**"I revoked the key in WooCommerce."** Then Ocoya can no longer reach the store. Connect it again from Channels.

## Related

<Columns cols={2}>
  <Card title="Create a workflow" icon="plus" href="/help/create-a-workflow">
    The WooCommerce poster example.
  </Card>

  <Card title="A workflow didn't run" icon="triangle-alert" href="/help/workflow-didnt-run">
    When a product went live and nothing posted.
  </Card>
</Columns>