WooCommerce fires a webhook when a customer starts checkout but does not complete. n8n catches it and queues the cart in Postgres. Three timed jobs then run: an email at T+4 hours (product reminder, no discount), a second email at T+24 hours (social proof + shipping reassurance), and a WhatsApp message at T+48 hours for carts over 150 AED only (10% one-time discount).

Our recovery rate at zamanistore.com is 14%, compared to the 4-8% industry average for single-channel email. The WhatsApp step alone recovers 3.8% of carts that ignored both emails.

Critical implementation detail: WhatsApp Business API requires explicit consent. Only message customers who opted in at checkout or in a previous order. Sending unsolicited WhatsApp messages risks your number being banned.

When an order moves to “failed” status in WooCommerce, n8n catches the webhook and sends a personalized recovery email within 5 minutes. The email includes a direct link back to the cart with items pre-loaded, a list of accepted payment methods, and a note that the items are still held for 24 hours.

We run separate workflows for zamani and Coloring Palestine because the tone, currency, and support contact differ. Failed payment recovery is one of the highest-ROI automations — a failed order already had intent; it just needs one friction point removed.

On a multi-currency store with Cloudflare edge caching, a misconfigured cache rule can serve a US visitor an order at AED prices, or a UAE visitor at GBP prices. The order completes, the customer pays the wrong amount, and you find out weeks later during a dispute.

This workflow fires on every new order webhook. It checks the billing country against the order currency. If the country ships to UAE but the currency is USD, or the country is UK but the currency is AED, it puts the order on hold and posts a Slack alert with the order ID, country, and currency. A human reviews before fulfillment.

We catch 2-4 mismatches per week across both stores. Without this workflow each one would mean a manual refund, a reorder, and sometimes a chargeback.

Shipping carrier webhooks break. In March 2026, our SwftBox delivery webhook was silently broken for 14+ days. Over 400 orders sat in “processing” status after being delivered. Customers received no completion email, loyalty points were not awarded, and the WooCommerce dashboard showed zero completed orders that month.

The safety net runs every 4 hours. It queries Postgres for orders that are still in “processing” status but have a tracking code and are older than 48 hours. For each one, it calls the carrier API directly to check delivery status. If the carrier confirms delivery, it marks the order complete in WooCommerce, updates Postgres, and sends a Slack summary.

This workflow is the reason we discovered the 14-day outage. It is now a permanent fixture regardless of webhook health.

A customer submits a return request via a simple Typeform or embedded form. n8n receives the webhook, looks up the original order in WooCommerce to confirm it is within the return window, checks the reason against the return policy categories, and routes it. Approved returns get an automated confirmation email with return shipping instructions. Requests outside the policy window or with missing order IDs get a different email explaining why.

The time saving is not in processing volume — it is in eliminating the back-and-forth of “what was your order number?”, “when did you order?”, “what is your reason?” An automated intake form that validates against the actual order cuts the average return resolution from 3 messages to 1.

Every Friday at 8pm UAE time, n8n scrapes the product pages of the 3-5 main competitors in each product category. It stores the prices in Postgres with a timestamp. Then it compares this week’s prices to last week’s, calculates the delta, and posts a Slack report to #competitor-monitor with a table: competitor name, product, last week’s price, this week’s price, change percentage.

Before this workflow, tracking competitor pricing meant manually visiting 15+ pages weekly. Now it is a 2-minute Slack read every Friday. The bigger value is catching when a competitor drops prices significantly — which is often a signal of a sale, an overstock situation, or a product discontinuation you can capitalize on.

For scraping, n8n’s HTTP Request node with a rotating user-agent works for most simple product pages. For JavaScript-heavy pages, a headless Playwright instance behind an API endpoint is more reliable.

Every two weeks, n8n queries Postgres for customer cohort data: new customers this period vs. last, repeat purchase rate, average order value, top-selling products, geographic breakdown, and the 10 most recent reviews from Site Reviews. Claude writes a 200-word narrative summary comparing this period to the last one and highlighting 2-3 things worth acting on.

The report goes to a private Slack channel. It takes 5 minutes to read and replaces what used to be 30 minutes of pulling Google Analytics, WooCommerce reports, and Site Reviews into a spreadsheet every other Monday.

The key is keeping the output actionable. If the repeat purchase rate dropped, the report says so and names the specific cohort (e.g., UK customers who ordered in February). If a product had a spike in 1-star reviews this period, it flags the product name and review count.

The most complex workflow we run. We submit a product photo and a brief to a form. n8n sends the image to Gemini for product description and visual analysis, uses that output to construct a script prompt, then calls Kling to generate a 5-second video ad with motion. The finished video is saved to Google Drive, and a Slack DM is sent with a preview link and the generated copy variants.

From form submission to Slack notification is about 4 minutes. A single freelancer video shoot would take a week to brief, shoot, edit, and deliver. This workflow produces rough drafts good enough to test in Meta ads for around $0.10 per run.

The videos are not broadcast quality. They work at the top of the funnel where fast production and volume matter more than polish. We use them to test angles before investing in professional production.