Why trigger on Processing rather than on order created?

WooCommerce creates the order before payment clears, so order.created fires for carts that never pay. Processing is the status WooCommerce sets once payment is confirmed for goods that need shipping, which is the moment a packer should see it. Stores selling only downloadable goods, which WooCommerce auto-completes, get a one-line change in the filter.

Can I use ClickUp, Asana or monday instead of Trello?

Yes, with a node swap. The card step is one Trello node. ClickUp, Asana and monday each have a create-task node in n8n that takes the same name, description and list, and the line-item checklist becomes subtasks or a checklist depending on the tool. The dedupe check and the error branch do not change.

What if a customer edits their order after the card is made?

The card is not updated. An order.updated event for an order already in the sheet is dropped by the dedupe step, so the card shows the order as it stood when it went to Processing. If your store edits orders often, ask about the variant that posts the change to the card as a comment.

Do I need a paid n8n or Make plan?

No. Any n8n Cloud plan or a self-hosted community edition runs it. The Make blueprint runs on Make's free plan inside its monthly operations cap; the setup guide shows how to count what one order uses so you can check that against your volume.

WoGSTrSMade to order

Ecommerce & orders

WooCommerce paid order → Trello pick card, Google Sheets log and Slack #orders

Paid orders become a log row, a pick card and a channel post, in that order.

WooCommerce sets a paid order to Processing, and that status change starts the run. The order is logged to a Google Sheet, a Trello card lands in your To Pick list with a checklist of line items and the shipping address, and Slack gets the card link. Built for small stores where the person packing is not the person watching the WooCommerce admin. Repeat status updates on the same order are ignored, so one order gets one card.

How it works

Wo
Trigger
Order updated (order.updated webhook), filtered to status Processing
WooCommerce
if
Step 1
Keep only Processing orders
Orders arriving with any status other than Processing stop here, which drops the pending, on-hold, completed and refunded updates that WooCommerce also sends through order.updated.
GS
Step 2
Register the order once
A lookup on the order number against the Order Log finds repeats and ends the run; a new order gets one row with number, date, customer, email, line items with SKU and quantity, shipping method, ship-to address and total.
Tr
Step 3
Create the pick card
A card lands in the To Pick list, named with the order number and customer, with a checklist of line items and the shipping address in the description.
S
Step 4
Post to #orders
#orders gets the order number, item count, shipping method and a link to the Trello card.
GS
Step 5
Write the card URL back
The order's row gets the Trello card URL and a Status of Carded, so the sheet doubles as the index to the board.
if
Step 6
Report a failed card
If Trello rejects the card, an error branch posts the order number and the error text to Slack and sets the row's Status to CARD FAILED, so nothing is lost silently.

What changes once it runs

The pick card exists within a minute of the order turning Processing, before the WooCommerce admin email is opened.
One card per order, even though WooCommerce sends order.updated more than once during an order's life.
Packers work from Trello, and nobody needs a WooCommerce login to see what to ship.
A sheet holds every order with its card link, ready for a weekly check against what actually shipped.
Failed card creation reaches Slack with the order number, rather than disappearing into a log.

What you get

Workflow export for n8n with the status filter, dedupe check, card creation and error branch built in.
Make scenario blueprint on the WooCommerce New Event webhook module, with an error handler on the Trello module.
Order Log Google Sheet template with the ten columns the workflow writes.
Written setup guide covering the WooCommerce API key and webhook, the Trello token, the Slack bot and the sheet.
Walkthrough video of a test order moving from Pending to Processing and arriving on the board.
30 days of email support for setup questions.

Before you start

WooCommerce store with a REST API key set to Read/Write, so the n8n trigger can register its own webhook; no extra plugin needed.
Trello board with a To Pick list, plus an API key and token for the account that creates cards.
Google Sheet for the order log (template included).
Slack workspace with an #orders channel and a bot token that can post to it.
n8n Cloud or self-hosted n8n with a public URL for the WooCommerce webhook.

Built for

Questions before you buy

Why trigger on Processing rather than on order created?: WooCommerce creates the order before payment clears, so order.created fires for carts that never pay. Processing is the status WooCommerce sets once payment is confirmed for goods that need shipping, which is the moment a packer should see it. Stores selling only downloadable goods, which WooCommerce auto-completes, get a one-line change in the filter.
Can I use ClickUp, Asana or monday instead of Trello?: Yes, with a node swap. The card step is one Trello node. ClickUp, Asana and monday each have a create-task node in n8n that takes the same name, description and list, and the line-item checklist becomes subtasks or a checklist depending on the tool. The dedupe check and the error branch do not change.
What if a customer edits their order after the card is made?: The card is not updated. An order.updated event for an order already in the sheet is dropped by the dedupe step, so the card shows the order as it stood when it went to Processing. If your store edits orders often, ask about the variant that posts the change to the card as a comment.
Do I need a paid n8n or Make plan?: No. Any n8n Cloud plan or a self-hosted community edition runs it. The Make blueprint runs on Make's free plan inside its monthly operations cap; the setup guide shows how to count what one order uses so you can check that against your volume.

Nearby on the shelf

Whole catalog