WooCommerce Stores Get the Same Treatment — Self-Hosted and All

Roughly a third of online stores run on WooCommerce, and a good share of the tooling around them treats that as a lesser case: the integration arrives late, does less, and gets quietly deprecated.

We built the WooCommerce integration against the same internals as every other store connection. Once your products are in the workspace, nothing downstream knows or cares where they came from. Same product picker, same workflow triggers, same AI Agent.

Connecting: a key pair, not an OAuth dance

WooCommerce is self-hosted, so there's no central authorisation server to redirect through. You generate credentials in your own admin instead:

1. In WordPress, go to WooCommerce → Settings → Advanced → REST API
2. Add key — give it a description, set permissions to Read, and generate
3. Copy the consumer key (it starts with ck_) and consumer secret
4. In Autoadify: Integrations → Connect WooCommerce, paste your store URL and both values

That's it. We validate the credentials against your store before saving, so a typo tells you immediately rather than failing silently a week later when a product changes.

Read permission is enough. Autoadify never writes to your store. If a tool asks you for write access to read your catalog, ask why.

Requests use the WooCommerce REST API v3 with Basic Auth over HTTPS. Your store does need to be reachable over HTTPS from the internet — a localhost dev install or an intranet-only store can't receive webhooks, which is a constraint of self-hosting rather than something we can work around.

Your catalog, kept current

On connect, we pull your full product catalog into the workspace. Three webhooks then keep it in step:

• product.created
• product.updated
• product.deleted

Each store gets its own randomly generated webhook secret, so we can verify that an incoming payload genuinely came from your store and not from someone who guessed the URL. Disconnect the integration and we delete the webhooks from your store rather than leaving orphaned entries cluttering your settings.

New products fire your workflows

The same thing that makes the hosted integrations useful works here. If you have an active workflow with a WooCommerce trigger, publishing a product in WooCommerce fires it — with that product's data passed in.

Build the workflow once: generate a product image, write per-platform captions, queue for review. Every new product runs it. For a store publishing regularly, this is where the integration pays for itself.

The AI Agent can read your catalog

Connecting the store gives our AI Agent the ability to look your products up mid-conversation:

You: Write a post about the walnut cutting boards, mention the current price.

It searches your synced catalog, pulls the real product data, and drafts from that. No copy-pasting specs into a chat box, and no risk of it inventing a price.

The agent can research your catalog and generate content freely. Anything that publishes or schedules stops for your explicit approval first — reading and drafting are safe, so they run; going public is a decision that stays yours. The Shopify write-up goes through those permission tiers in more detail.

Running both Woo and Shopify?

Plenty of merchants do — a main store plus a wholesale or regional one. Autoadify treats them as one pool. The composer's product picker searches across every connected store at once, and results are labelled by source so you always know which store a product came from. You can run workflows off both stores in the same workspace.

Honest limitations

• Your store must be publicly reachable over HTTPS. Webhooks can't reach a local or firewalled install.
• Read-only, by design. Autoadify won't update inventory or push products back. It's a marketing tool, not a second admin panel.
• Product-focused today. Webhooks cover product create/update/delete. Order and customer events aren't wired up — if that's something you'd use, tell us, because that feedback is what decides what we build next.

Getting started

Generate a read-only REST API key in WooCommerce, then Integrations → Connect WooCommerce. Your catalog syncs on connect and stays current from there.

For the strategy side — which platforms are worth posting WooCommerce products to, and what to post about each — see WooCommerce social media automation.