Skip to main content

Automated WooCommerce abandoned cart recovery with Google Sheets email reminders

Workflow preview

Workflow preview
100%
Automated WooCommerce abandoned cart recovery with Google Sheets email reminders preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Recover lost revenue on autopilot with this powerful WooCommerce Abandoned Cart Automation. This workflow connects directly to your WooCommerce store using the REST API to fetch all recent orders. ...

Best for

  • Social Media automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.datetime, n8n-nodes-base.stickynote, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.googlesheets, n8n-nodes-base.emailsend

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jacob.

Original n8n.io source

1.1 Workflow description

Title
Automated WooCommerce abandoned cart recovery with Google Sheets email reminders
Workflow name
Automated WooCommerce abandoned cart recovery with Google Sheets email reminders

Recover lost revenue on autopilot with this powerful WooCommerce Abandoned Cart Automation.

This workflow connects directly to your WooCommerce store using the REST API to fetch all recent orders. It logs them in Google Sheets for easy tracking and visibility. Every day at a scheduled time, it checks for orders with the "pending" status that haven't received a reminder email yet — and sends a personalized follow-up email to the customer.

Use it to:

Automatically remind customers about unpaid orders

Recover abandoned carts without any manual effort

Keep clean logs of all orders and reminders via Google Sheets

Boost conversion rates and revenue with timely, helpful emails

Requirements:

To use this workflow, you need:

A WooCommerce store with REST API access

A connected Google Sheets account

No external plugins are required in WooCommerce. Just make sure the REST API is enabled and credentials are added to n8n.

Google Sheets Configuration

Create a Google Sheet with the following column headers (first row):

Order ID | Buyer | E-mail | Products | Price | Status | Order date | Payment url | Reminder sent

Customize Mail:

Customize the reminder message to match your brand voice and offer incentives like a discount or free shipping to encourage payment.

Set it once and let your abandoned cart recovery run in the background — 24/7.

contact: [email protected]

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - Schedule Trigger1

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 3 - Date & Time

Type / Role
n8n-nodes-base.dateTime - dateTime
Config choices
Version 2

Block 4 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - HTTP Request1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 7 - Convert data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - Adding orders to Google Sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 9 - Get order with pending status

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 10 - Reminder Sent Email Update

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.6

Block 11 - Send remider email

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

3. Summary Table

Workflow Automated WooCommerce abandoned cart recovery with Google Sheets email reminders
Complexity intermediate
Nodes 11
Categories Social Media
Author Jacob
Published 23 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6322/6322.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automated WooCommerce abandoned cart recovery with Google Sheets email reminders do?

Recover lost revenue on autopilot with this powerful WooCommerce Abandoned Cart Automation. This workflow connects directly to your WooCommerce store using the REST API to fetch all recent orders. ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media use case.