Your WooCommerce store, from the conversation.
Ask for the order, change its status, create the coupon. Cedric proposes the change in WooCommerce and waits for your yes.
$50 in free credits when you sign up. No card needed.
- A WooCommerce store answers most questions in its admin, and nobody wants to log in for each one.
- Ask in plain words: the orders still processing, what sold best last month, which products are low on stock.
- Cedric updates an order's status, adds an order note or creates one, and edits products, prices and stock, proposed first.
- Coupons with usage limits and expiry dates can be created from the thread, and store settings such as shipping zones read or changed.
- Refunds, price changes and order status updates change what customers see and pay, so each one waits for your yes.
What can a WooCommerce AI agent do?
Most of what a store owner wants from WooCommerce is a lookup: whether an order has shipped, what a customer ordered last time, which variation of a product is out of stock. A WooCommerce AI agent answers those from the conversation. Cedric searches and lists products, including their variations, categories, tags and attributes, looks up orders with their line items, totals, shipping details and payment status, and reads customer records with contact details, addresses and order history.
The other half is keeping the store current. Cedric creates or updates products and adjusts prices, descriptions, images and stock levels. It creates orders, updates an order's status, adds order notes and issues refunds. It creates and edits discount coupons with usage limits and expiry dates, and it can configure store settings such as shipping zones, tax rates and payment method options. Each of these is proposed before it runs, so the store changes only when someone has read the proposal and said yes.
For the numbers, Cedric pulls sales, top-seller and stock reports for a chosen date range, which is how the weekly report can be answered in the channel instead of assembled from exports. Each store has its own API address and credentials, so the connection is to one store at a time, and the credentials may be read-only, in which case Cedric reads and reports but does not write.
Monday morning
The weekend's orders, and the one that needs a hand.
Jonas Lindqvist9:14 AM
@Cedric what came in over the weekend, and is there anything still stuck in processing from last week? If so, add a note that we are shipping it today.
CedricAPP9:15 AM
Saturday and Sunday: 23 orders, EUR 1,612 in total, top seller the Linen Apron (9 units). One order is still processing from last week: #5817, Anna Roth, placed 27 August, 2 items, EUR 74, paid by card, shipping to Hamburg. Proposed: an order note on #5817 saying "Shipping today, 1 September", visible to the customer, and the status left at processing until you mark it completed.
Looked up
Orders with line items, totals, shipping and payment status; products with variations and stock; customers with their order history.
Updated
An order's status, an order note, a product's price or stock, a new coupon with a usage limit and expiry: proposed first, saved on your yes.
Reported
Sales, top-seller and stock reports for any date range, answered in the thread instead of exported.
Connect WooCommerce in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect WooCommerce from the dashboard
Open the Integrations page and sign in with WooCommerce on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "which orders are still in processing?". You describe the outcome; Cedric picks the WooCommerce actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold WooCommerce into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
A customer writes in through Gmail about a late order; Cedric reads the message, finds the order in WooCommerce and drafts the reply with its status and tracking, sent on your yes. If the store's payments run through Stripe, the charge can be checked in the same ask.
The month's sales report sits well next to traffic from Google Analytics and campaign spend in Google Ads. Ask for the month and Cedric puts the three numbers in one reply, or in a Google Sheets tab the team already reads.
Where the limits are
WooCommerce is a catalog connection, not a built-in playbook. Cedric works from what the WooCommerce connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
One store, its own credentials. Each WooCommerce store has its own API address and keys, and those keys may be read-only. With read-only access Cedric answers questions and pulls reports but proposes no changes.
Refunds, price changes and status updates are confirmed every time. Each one changes what a customer sees or pays, so Cedric shows the order or product and the exact change before running it.
Cedric sees what the WooCommerce connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. WooCommerce is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on WooCommerce's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
No. It connects to the WooCommerce API with the store's own API keys, and it can do exactly what those keys allow. Read-only keys give a read-only Cedric; read and write keys let it propose changes too.
Yes, when the keys allow writes. Store settings such as shipping zones, tax rates and payment method options can be read and configured from the thread, and any change is proposed with the current and new values before it is saved.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect WooCommerce in a minute.
Ask which orders are still processing, then see the note it proposes.
100K credits ($50) on sign up. No card needed.