The tasks that eat up the most time in a PrestaShop 8 store with no technical team are always the same: pushing orders into the ERP, notifying the warehouse, tagging VIP customers, sending shipping notifications, requesting reviews, running backups and chasing abandoned carts. All seven can be automated with self-hosted n8n in one afternoon of work. This post is the complete recipe for each workflow: trigger, steps, and the common pitfalls worth knowing about before they show up.
For the store side of these flows we use the webhooks from the Zeyvro n8n Connector module, but every workflow can also be built with manual webhooks and the PrestaShop API — we point out the difference where it matters.
Initial setup
Before building the first workflow:
- A basic VPS with Docker — self-hosted n8n runs comfortably on the cheapest tier of any provider (in the range of a few euros a month). Installation takes about 30 minutes.
- A dedicated subdomain (n8n.yourstore.com) with automatic SSL.
- Credentials generated and stored in n8n: your ERP’s API (Holded in this guide), the Slack API if you use it, and the SMTP details of your service email.
- The order event enabled in the store: with the n8n Connector module, tick the outbound order event in the BO and point it at your n8n webhook URL; without the module, a manual webhook attached to the order confirmation hook.
With the base setup in place, each workflow below takes between fifteen and thirty minutes to build.
Workflow 1: confirmed order to the ERP
Triggered by the PrestaShop order event. It creates the customer in Holded if they’re new, creates the invoice with the order lines mapped, and stores the invoice ID back on the order (as a reference or private note) — so you can always cross-reference order↔invoice in both directions.
This is the workflow that replaces the most manual work: every order you currently key into the ERP by hand is minutes that disappear from your day.
Workflow 2: warehouse notification by email
Daily cron, first thing in the morning. It collects the previous day’s orders in “Processing in progress” status, generates a PDF with the picking list grouped by product, and emails it to the warehouse manager. If your warehouse is outsourced, this flow kills the daily “here’s the list” email chain.
Workflow 3: VIP customer detection
Triggered by the order event. It adds up the customer’s order history and, if it exceeds the threshold you define (say, €300 over twelve months), moves them into PrestaShop’s VIP customer group and generates a cart rule (a personalized coupon) with a discount for their next purchase. The threshold and the discount are your decisions — the workflow just applies them consistently, which is exactly what manual review never manages. The VIP group also lets you set specific prices or priority shipping without touching anything else.
Workflow 4: shipping notification to the customer
Triggered by the order status changing to “Shipped” with a tracking number. It sends the notification to the customer by email and, if they’ve opted in to WhatsApp, also via WhatsApp with the carrier’s tracking link.
Workflow 5: review request at 7 days
Daily cron. It identifies orders delivered exactly 7 days ago and sends the review request email with a personalized link. It filters out customers who have already left a review so you don’t spam them. This flow automates the one activity that never gets done consistently by hand — and consistency is the only thing that builds review volume.
Workflow 6: database backup to Google Drive
Weekly cron, overnight. It generates a compressed dump of the PrestaShop database, encrypts it with a symmetric key and uploads it to Google Drive, into a dedicated folder with several weeks of retention.
In most stores without a technical team, this workflow doesn’t replace manual work — it replaces nothing, because the backup simply wasn’t being done (or the hosting provider’s backup was the only safety net). It’s the most important of the seven.
Workflow 7: high-ticket abandoned cart recovery
Hourly cron. It identifies carts from the last 24 hours with no associated order and above the amount you define (say, €80). It sends the automatic recovery email and, on top of that, fires an internal Slack notification with the customer’s details so the highest-value carts get a manual phone call. The dual channel is the key: email automates the volume, while the internal alert saves the personal touch for where it pays off.
The two common pitfalls you’re going to hit
Two adjustments that almost every implementation ends up needing — better to know them upfront:
- Guest customers without a tax ID (workflow 1): if the Holded mapping assumes the tax ID field is always filled in, the workflow fails on guest checkout orders. Fix: a placeholder tax ID with a guest-customer flag in the mapper, and review those cases separately.
- The tracking number arrives after the status change (workflow 4): in many setups the order moves to “Shipped” before the carrier returns the tracking number, and the notification goes out without tracking. Fix: make the send conditional on the tracking number being present, with a retry every few minutes if it isn’t.
The store side: the Zeyvro n8n Connector module
Everything above can be built by hand with hooks and the PrestaShop API, but the most fragile part of the build is always the same: the webhooks and their authentication. The Zeyvro n8n Connector module ships that part ready from the BO: outbound events with authentication, a normalized payload and filters so you don’t send orders you don’t need, plus inbound actions so n8n can write back to the store without exposing the full API.
When it’s worth it: if you plan to build several workflows over time and prefer to centralize your data output in one controlled point. When it’s not: if you’re only going to run one or two very specific workflows.
If you want to understand the tools before choosing, read what n8n is and how it compares to Zapier and Make; for ERP synchronization in detail, the guide to connecting Holded, Sage or A3. If you want to replicate this setup, write to us at hola@zeyvro.com with your context.
Zeyvro builds PrestaShop 8 modules from a real store running in production. Unobfuscated code.
Frequently asked questions
How long does it take to automate a PrestaShop 8 store with n8n?
With the base setup done (VPS + n8n + credentials, around an hour), the usual workflows (ERP invoicing, notifications, reviews, backups) take 15-30 minutes each to build. All seven in this guide fit into one afternoon of work.
How much does it cost to run n8n for a store?
Self-hosted n8n runs on the cheapest VPS tier of any provider, for a few euros a month, and doesn’t charge per execution — the cost doesn’t grow with your order volume.
What kind of store tasks can be automated?
ERP invoicing, warehouse notifications, VIP customers via customer groups, shipping notifications, review requests, backups and abandoned cart recovery, among many others.
Do I need a module for this?
Not strictly: PrestaShop has hooks and an API you can use to build the webhooks by hand. A connector module removes the most fragile part (webhooks and authentication), normalizes the payload, and adds filters and inbound actions from the BO.
The authenticated webhooks, filters and inbound actions from this guide, ready from your BO.
View Zeyvro n8n Connector →