Skip to main content

Handle Zendesk WooCommerce refund tickets with Slack and Gmail

Workflow preview

Workflow preview
100%
Handle Zendesk WooCommerce refund tickets with Slack and Gmail preview
Open on n8n.io

1. Workflow Overview

Zendesk Refund Ticket Automation with WooCommerce Order Lookup, Slack Alerts & Gmail Emails This workflow automatically handles refund related Zendesk tickets for WooCommerce orders. When a new ref...

Best for

  • Ticket Management automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.zendesktrigger, n8n-nodes-base.code, n8n-nodes-base.woocommerce, n8n-nodes-base.if, n8n-nodes-base.merge, n8n-nodes-base.slack, n8n-nodes-base.switch, n8n-nodes-base.set

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Handle Zendesk WooCommerce refund tickets with Slack and Gmail
Workflow name
Handle Zendesk WooCommerce refund tickets with Slack and Gmail

Zendesk Refund Ticket Automation with WooCommerce Order Lookup, Slack Alerts & Gmail Emails

This workflow automatically handles refund-related Zendesk tickets for WooCommerce orders. When a new refund ticket is created, it verifies whether the ticket is related to WooCommerce, fetches the order details, checks refund eligibility and then routes the case based on the refund type. Damaged items notify the internal team via Slack, while other refund cases trigger customer emails via Gmail for further proof or confirmation.

Quick Implementation Steps

  1. Import the workflow JSON into n8n
  2. Connect Zendesk, WooCommerce, Slack and Gmail credentials
  3. Update Slack channel and Gmail sender settings
  4. Activate the workflow
  5. Start receiving and processing refund tickets automatically

What It Does

This workflow listens for new Zendesk tickets and checks whether they are related to WooCommerce refunds. If the ticket qualifies, it extracts the order ID from the ticket description and fetches the corresponding order from WooCommerce.

Once the order data is retrieved, the workflow validates the order status and checks whether a refund already exists. Eligible cases are merged with ticket data and routed based on the refund reason, such as damaged items, wrong items, partial refunds or full refunds.

For damaged items, the workflow immediately notifies the internal support team via Slack. For other refund types, it sends structured and context-aware emails to customers using Gmail, requesting proof or informing them about next steps.

Who’s It For

  • Customer support teams handling WooCommerce refunds
  • Operations teams managing refund communication
  • E-commerce businesses using Zendesk and WooCommerce
  • Non-technical users who want automated ticket handling without coding

Requirements to Use This Workflow

  • Active Zendesk account with ticket access
  • WooCommerce store with REST API credentials
  • Slack workspace with permission to post messages
  • Gmail account connected via OAuth2
  • n8n instance (Cloud or Self-hosted)

How It Works & Set Up

Setup Instructions

  1. Import Workflow
  • Upload the workflow JSON into your n8n instance.
  1. Zendesk Trigger Configuration
  • Connect Zendesk OAuth credentials
  • Trigger runs when a new ticket is created
  1. WooCommerce Configuration
  • Add WooCommerce API credentials
  • Ensure permission to fetch orders by ID
  1. Slack Setup
  • Select the Slack channel for damaged item alerts
  1. Gmail Setup
  • Connect Gmail OAuth
  • Configure sender email and reply settings
  1. Activate Workflow
  • Save and activate the workflow
  • New refund tickets will now be processed automatically

How To Customize Nodes

  • Order ID Regex: Modify extraction logic in the Zendesk normalization node
  • Refund Keywords: Update refund-type detection keywords (damaged, wrong, partial, full)
  • Slack Message Format: Customize internal notification content
  • Email Templates: Change subject lines and messages in Set nodes
  • Eligibility Rules: Adjust order status or refund conditions in IF nodes

Add-ons (Optional Enhancements)

  • Auto-tag Zendesk tickets based on refund type
  • Assign tickets to specific agents or groups
  • Log refund cases to Google Sheets or Airtable
  • Add SLA timers for refund response tracking
  • Integrate WhatsApp or SMS notifications

Use Case Examples

  • Automatically handle damaged product refund requests
  • Ask customers for proof when wrong items are delivered
  • Notify support teams instantly for high-priority refund cases
  • Reduce manual order lookups for refund tickets
  • Standardize refund communication across support channels

> There can be many more similar use cases depending on business needs.

Troubleshooting Guide

Issue Possible Cause Solution
Order ID is null Order number not in ticket text Ask customers to include order number
Workflow not triggering Zendesk trigger misconfigured Check trigger event type
Slack message not sent Channel or credentials incorrect Reconnect Slack account
Email not delivered Gmail OAuth expired Reauthorize Gmail
Workflow stops early Order already refunded This is expected behavior

Need Help?

If you need help setting up this workflow or extending it with advanced automation then our n8n workflow developers at WeblineIndia are happy to assist.

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 - Zendesk – New Refund Ticket Trigger

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

Block 2 - Normalize Zendesk Ticket Data

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

Block 3 - WooCommerce – Fetch Order by ID

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

Block 4 - Normalize WooCommerce Order Data

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

Block 5 - Check Order Status (Completed or Processing)

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 6 - Check If Order Already Refunded

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 7 - Merge Ticket and Order Data

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 8 - Is Refund Reason = Damaged Item?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 9 - Slack – Notify Damaged Item Refund

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 10 - Route Refund Type (Wrong / Partial / Full)

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.3

Block 11 - Prepare Email – Wrong Item Proof Request

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 12 - Email Customer – Request Proof (Wrong Item)

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

Block 13 - Prepare Email – Partial Refund Review

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 14 - Email Customer – Partial Refund Under Review

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

Block 15 - Prepare Email – Full Refund Return Required

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 16 - Email Customer – Return Required for Refund

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

Block 17 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 18 - Sticky Note

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

Block 19 - Sticky Note1

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

Block 20 - Sticky Note2

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

Block 21 - Sticky Note3

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

Block 22 - Sticky Note4

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

Block 23 - Sticky Note5

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

3. Summary Table

Workflow Handle Zendesk WooCommerce refund tickets with Slack and Gmail
Complexity advanced
Nodes 23
Categories Ticket Management
Author WeblineIndia
Published 07 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/14861/14861.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 Handle Zendesk WooCommerce refund tickets with Slack and Gmail do?

Zendesk Refund Ticket Automation with WooCommerce Order Lookup, Slack Alerts & Gmail Emails This workflow automatically handles refund related Zendesk tickets for WooCommerce orders. When a new ref...

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 Ticket Management use case.