WooCommerce
WooCommerce orders and products as real-time triggers
WooCommerce is the most-deployed ecommerce platform on the web because it sits on top of WordPress, which means it sits on top of a lot of stores. On Tiny Command, six triggers cover the events that matter to merchants: Order Created (new sale), Order Completed (fulfillment done), Order Updated (status or detail change), Customer Created (new account), Product Created, Product Updated. Fourteen actions cover the operational side: Create Order, Create Product, Create Customer, Create Coupon, Get Order, Get Customer, Get Product, Delete Product, plus the list endpoints. The integration uses WooCommerce's REST API with consumer key + secret (generated from your WooCommerce settings). Permissions follow whatever WooCommerce user the key was issued for. Common patterns: an Order Created event syncs the customer into HubSpot, the line items into a Notion fulfillment database, and a thank-you SMS goes via Twilio to the customer if the line items include a "white-glove" tag.
Workflows start when WooCommerce does.
6 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new customer is created in WooCommerce. Use to add them to your ESP, sync to a CRM, or send a welcome offer.
Fires when a WooCommerce order moves to status "completed". Common use: post-purchase email, fulfillment handoff, accounting sync, review request.
Fires when a new order is placed in WooCommerce (any status). Used for immediate ops notifications and pre-fulfillment workflows.
Fires whenever any field on a WooCommerce order changes (status, items, totals, address). Used for mirroring order state into other systems.
Fires when a new product is created in WooCommerce. Use to sync catalog into Meta/Google merchant feeds, search indexes, or marketplaces.
Fires when an existing WooCommerce product is updated (price, stock, image, description). Used to keep external catalogs and search indexes fresh.
Do anything WooCommerce can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Coupon | Creates a new coupon in WooCommerce with code, type (percent/fixed_cart/fixed_product), amount, usage limits, and product/category restrictions. Used to generate personalized discounts from a CRM or campaign tool. |
| Create Customer | Creates a new customer record in WooCommerce with email, name, billing/shipping addresses, and optional metadata. Used when a customer is provisioned upstream (e.g. by your CRM) and needs to exist in Woo. |
| Create Order | Creates a new WooCommerce order with line items, customer, addresses, status, and payment method. Used for back-office orders, draft orders to share with a customer, or migration imports. |
| Create Product | Creates a new WooCommerce product with name, type (simple/variable/grouped), prices, SKU, stock, images, and category. Used to mirror catalog from a PIM or another store. |
| Delete Product | Deletes a WooCommerce product. By default moves to trash; pass force=true to permanently delete. Use the soft-delete path so you can recover from accidents. |
| Get Customer | Returns a single WooCommerce customer by ID with their addresses, role, and order summary. Used to enrich trigger payloads or to render customer-detail UI. |
| Get Order | Returns a single WooCommerce order by ID with line items, totals, customer, addresses, and order notes. The standard read action after a trigger fires with an ID. |
| Get Product | Returns a single WooCommerce product by ID with prices, SKU, stock, images, attributes, and variations. Use as a follow-up step after a product-changed trigger. |
| List Coupons | Lists coupons from a WooCommerce store with their code, discount type, amount, and usage stats. Used for coupon-effectiveness reports or expiry cleanup. |
| List Customers | Lists customers from a WooCommerce store, with email, role, and order stats. Use for ESP sync, churn analysis, or compliance exports. |
| List Orders | Lists orders from a WooCommerce store, with filters for status, date range, and customer. Common in nightly accounting sync and revenue reports. |
| List Products | Lists products from a WooCommerce store with filters for status, category, SKU, and stock. Used for catalog audits and external feed generation. |
| Update Order | Updates a WooCommerce order: status (e.g. mark as completed/refunded), shipping address, customer notes, or meta. The standard hook to push status from your fulfillment system back into Woo. |
| Update Product | Updates an existing WooCommerce product's name, prices, stock, images, or category. Common in inventory-sync flows from your warehouse or ERP. |
Pre-built WooCommerce workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect WooCommerce once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every WooCommerce field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the WooCommerce integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect WooCommerce to Tiny Command?
What WooCommerce triggers does Tiny Command support?
What WooCommerce actions can I run from a workflow?
Is the WooCommerce integration real-time?
Do I need to write code to use WooCommerce with Tiny Command?
How much does the WooCommerce integration cost?
More e-commerce apps people connect.
Same category as WooCommerce, ordered by how often teams pair them. Hover the carousel to pause.
Do more with WooCommerce.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
