One-off jobs are nice; running jobs are better. Saleor has first-class webhooks and a GraphQL API, and your server has cron — which means the agent can wire up automations that work while you sleep. Each idea below is a small, inspectable piece of code the agent writes, installs, and keeps an eye on. Here are ten workflows worth setting up.

1. Order notifications to your team chat

Every paid order deserves a shout. The agent registers a Saleor app and subscribes an ORDER_PAID webhook to a tiny relay service it writes on your server; the relay formats the order and posts it to Slack or Telegram. You get the number, total, and channel within seconds of payment, and the code sits in a folder you can read and change later.

Try: “Set up an app with an ORDER_PAID webhook that posts to our Telegram chat -1001234567: order number, total, channel, and a link if there is one.”

2. Low-stock alerts before you run dry

Stockouts are lost sales you notice too late. A nightly job queries every variant’s quantities per warehouse, compares them to a reorder threshold you set, and emails a digest with current levels and a suggested reorder. The first run usually surprises people — that is the point.

Try: “Every evening at 6, email ops@ourshop.com all variants under 15 units with stock per warehouse and a suggested reorder quantity based on the last 30 days of sales.”

3. Recover abandoned checkouts

Saleor keeps checkout objects even when customers bail before paying — complete with the email they typed, the lines they added, and the totals they saw. A morning job finds checkouts older than 24 hours with no matching order, and emails you the most valuable ones with cart contents and contact details where available. You follow up with a personal email or a discount code — that part stays human. Even a 5% recovery rate on a busy shop is real money for a two-minute daily scan.

Try: “Each morning, list checkouts older than 24 hours that never became orders, with email, total value, and cart contents, top 20 by value.”

4. Nightly accounting export

Your bookkeeper wants a file, not dashboard access. A scheduled export pulls the day’s paid orders, splits out refunded ones, and writes a CSV with date, number, customer country, subtotal, tax, shipping, and total into a shared folder. A consistent format means fewer questions at month-end.

Try: “Export yesterday’s fully paid orders to /home/accounting/orders-YYYY-MM-DD.csv with date, order number, country, subtotal, tax, shipping, total, and put refunded orders in a separate file.”

5. Flag risky orders for review

A first-time customer paying $800 to a brand-new shipping country deserves a second look before you ship. The agent hooks ORDER_CREATED: if the value passes your threshold and the customer’s history is thin or the country is new, it tags the order’s private metadata and emails your team. Legitimate orders sail through; odd ones wait for a human.

Try: “When an order over $300 is created, check the customer’s order history and shipping country; if it’s their first order or a new country, set order metadata flagged=true and email security@ourshop.com.”

6. Review requests a week after fulfillment

Timing is everything with review emails — too early and the package hasn’t landed, too late and the moment is gone. The workflow records fulfillment timestamps from the ORDER_FULFILLED webhook, and a cron job sends the request seven days later, listing the purchased products with links. Cancelled or refunded orders are skipped automatically.

Try: “Send a review request email 7 days after each order is fulfilled, listing the products bought, and skip the order if it was refunded or cancelled in the meantime.”

7. A product feed your ads can read

Google Merchant Center and most ad tools want a feed: title, price, availability, image URL. Saleor already has all of it. A nightly job regenerates the feed file from everything published in your default channel, so your ads never point at dead links or stale prices. The agent validates the output against the feed spec before calling it done.

Try: “Build a nightly job that writes /var/www/feeds/google-merchant.xml from all products in the default channel with title, price, availability, and image URL, and check it against Google’s feed requirements.”

8. Backfill missing translations

Selling into Germany with English-only product pages costs you conversions, and typing translations by hand does not scale past a few dozen products. The agent finds products in your catalog missing German translations, drafts them from the English descriptions, shows you a sample for approval, and then writes them back through the translation API. Machine-drafted, human-approved — that order matters, because a wrong translation on a product page is harder to spot than a missing one.

Try: “Find every product missing a German translation, draft one from the English description, show me 5 samples, and if I approve apply the rest.”

9. A weekly catalog health report

Broken image links, missing SEO descriptions, variants with no price in one channel, collections that went empty — small defects that compound. A Monday-morning email keeps the list short and actionable. The same job can also report sales velocity, so you see problems next to performance instead of in a vacuum.

Try: “Every Monday email me a catalog report: products missing images or SEO descriptions, variants missing a price in any channel, and empty collections older than 30 days.”

10. A watchdog that restarts the stack

Saleor runs as several containers — API, Celery worker, dashboard — and any of them can wedge under load. The API can answer while the worker has silently died, which means search indexing and email stop while the shop looks fine. A one-minute watchdog queries the GraphQL API and checks the worker queue; two failures in a row and it restarts the unhealthy services and reports what it did. It is a seatbelt, not a strategy, and knowing it exists lets you sleep on launch night.

Try: “Set up a watchdog that checks the GraphQL API every minute, restarts the api and celery worker if it fails twice in a row, and messages me what it restarted.”

Each of these is small code you own, running on your own server — no SaaS in the middle. Start with the workflow that hurts weekly, and let the agent maintain it as your catalog grows. Running Saleor with an agent doing the busywork is the point: Saleor on OpenSysLab.