WOOCOMMERCE n8n INTEGRATION: AUTOMATE WOOCOMMERCE WITH N8N

This trigger fires automatically whenever a new product is added to your WooCommerce catalog. Whether products are created manually through the WordPress admin, imported via CSV, or added through another integration, this webhook catches them all instantly.

Configuration parameters:

• Credential to connect with: Select your WooCommerce account credential from the dropdown. This required parameter establishes the secure connection to your specific store.
• Event: Set to "product.created" to listen specifically for new product additions. This required dropdown ensures your workflow only triggers for the exact event you need.

Typical use cases: Automatically push new products to your Google Shopping feed, notify your marketing team via Slack when new items are ready for promotion, sync new products to external inventory management systems, or create social media draft posts featuring new arrivals.

When to use it: Ideal for multi-channel sellers who need product data synchronized across platforms, or marketing teams who want to automate promotion workflows for new inventory.

This trigger activates whenever any product in your store is modified—price changes, description updates, stock adjustments, category reassignments, or any other product field modification. It's your real-time window into catalog changes.

Configuration parameters:

• Credential to connect with: A required dropdown to select which WooCommerce account credentials n8n should use for authentication.
• Event: Set to "product.updated" to capture all product modifications. Required for the trigger to know which webhook events to listen for.

Typical use cases: Keep price changes synchronized with Amazon, eBay, or other marketplaces, log all product modifications to a Google Sheet for audit purposes, trigger cache invalidation on your CDN when product images change, or alert the warehouse team when stock levels are manually adjusted.

When to use it: Essential for stores with frequent catalog updates, especially those selling on multiple channels where product data must stay consistent.

When a product is removed from your WooCommerce store, this trigger fires immediately. This is crucial for maintaining data integrity across connected systems—you don't want to advertise products that no longer exist.

Configuration parameters:

• Credential to connect with: Required dropdown for selecting your WooCommerce account credentials.
• Event: Set to "product.deleted" to specifically catch product removal events. This required field ensures precise event targeting.

Typical use cases: Automatically remove deleted products from external marketplace listings, update inventory databases to reflect discontinued items, notify relevant teams when products are removed unexpectedly, or archive product data to a backup system before final deletion.

When to use it: Critical for businesses managing products across multiple platforms where orphaned listings can cause customer confusion and order issues.

The most commonly used WooCommerce trigger—this fires the instant a new order is placed in your store. Every purchase, whether from a first-time customer or repeat buyer, triggers your workflow with complete order data including items, totals, customer information, and shipping details.

Configuration parameters:

• Credential to connect with: Required dropdown to authenticate with your WooCommerce store.
• Event: Set to "order.created" to capture new purchases. This required parameter can be fixed or dynamic via expression.

Typical use cases: Send order data to your fulfillment center or 3PL provider instantly, add customers to post-purchase email sequences in Mailchimp or Klaviyo, create invoices automatically in QuickBooks or Xero, post high-value order alerts to your team's Slack channel, or trigger SMS notifications to customers confirming their purchase.

When to use it: Use this for virtually any post-purchase automation—it's the foundation of most e-commerce workflow automation.

This trigger fires whenever an existing order is modified—status changes, shipping updates, item additions, refund processing, or note additions. It's your real-time pulse on order lifecycle changes.

Configuration parameters:

• Credential to connect with: Required dropdown for WooCommerce account selection.
• Event: Set to "order.updated" to listen for modifications. Required field with support for expressions.

Typical use cases: Send shipping notifications when order status changes to "completed", update your CRM when orders are refunded or cancelled, sync order status changes to your customer service platform, or trigger re-engagement campaigns when orders sit in "pending" too long.

When to use it: Perfect for order lifecycle management, especially stores with complex fulfillment processes or those needing tight integration with customer service tools.

When orders are permanently deleted from your WooCommerce store (not just trashed), this trigger fires. While order deletion is less common, tracking it is important for maintaining accurate records across systems.

Configuration parameters:

• Credential to connect with: Required dropdown for selecting authentication credentials.
• Event: Set to "order.deleted" to capture permanent order removals. Required parameter.

Typical use cases: Remove corresponding records from external accounting systems, log deletions for compliance and audit purposes, alert administrators when orders are deleted (potential fraud indicator), or update analytics dashboards to maintain accurate sales data.

When to use it: Important for businesses with strict compliance requirements or those who need to maintain synchronized records across multiple systems.

This trigger fires when a new customer account is created in your WooCommerce store—whether through checkout registration, manual admin creation, or the account registration page. Capture new customers the instant they join.

Configuration parameters:

• Credential to connect with: Required dropdown for WooCommerce authentication.
• Event: Set to "customer.created" to capture new registrations. Required field supporting fixed values or expressions.

Typical use cases: Add new customers to your CRM like HubSpot via n8n, Salesforce, or Pipedrive, trigger welcome email sequences in your marketing automation tool, create customer profiles in your helpdesk software, sync customer data to your loyalty program platform, or send internal notifications about new B2B customer signups.

When to use it: Essential for any store building customer relationships—feeds your marketing automation, CRM, and customer service tools with fresh data instantly.

Fires whenever customer information is modified—address changes, email updates, profile edits, or any other customer data modifications. Keep your customer data synchronized across all platforms.

Configuration parameters:

• Credential to connect with: Required credential dropdown for authentication.
• Event: Set to "customer.updated" to track profile modifications. Required parameter.

Typical use cases: Sync address changes to your shipping/fulfillment providers, update customer records in your CRM when email addresses change, trigger re-verification flows when critical customer data is modified, or keep mailing lists updated with current customer information.

When to use it: Critical for maintaining data quality across integrated systems, especially for stores with active customer bases who frequently update their information.

This trigger activates when a customer account is deleted from your WooCommerce store. Important for GDPR compliance and maintaining synchronized customer databases.

Configuration parameters:

• Credential to connect with: Required dropdown for selecting WooCommerce credentials.
• Event: Set to "customer.deleted" to capture account removals. Required field.

Typical use cases: Remove customer data from connected CRM and email platforms (GDPR compliance), log customer deletions for audit and compliance records, trigger data removal requests to third-party services, or update customer counts in analytics and reporting tools.

When to use it: Essential for GDPR-compliant businesses and stores that need to ensure customer data removal propagates across all connected systems.

Fires when a new coupon or discount code is created in WooCommerce. Track promotional activity and automate related workflows.

Configuration parameters:

• Credential to connect with: Required dropdown for WooCommerce account credentials.
• Event: Set to "coupon.created" to monitor new promotions. Required parameter.

Typical use cases: Automatically announce new coupons to your affiliate partners, log all promotions to a tracking spreadsheet for budget monitoring, trigger social media posts about new discount codes, or notify the marketing team when unauthorized coupons are created.

When to use it: Useful for marketing teams wanting visibility into promotional activity, or for stores that need to track coupon creation for budget and audit purposes.

This trigger fires when existing coupons are modified—usage limits adjusted, expiration dates changed, or discount amounts updated.

Configuration parameters:

• Credential to connect with: Required credential selection dropdown.
• Event: Set to "coupon.updated" to track modifications. Supports fixed or expression input.

Typical use cases: Update affiliate partner systems when commission rates change, log coupon modifications for promotional audit trails, alert marketing managers when high-value coupons are modified, or sync coupon changes to external promotional tracking tools.

When to use it: Important for stores with complex promotional strategies or those who need audit trails of coupon modifications.

Fires when a coupon is deleted from your WooCommerce store. Track promotional cleanup and ensure connected systems are updated.

Configuration parameters:

• Credential to connect with: Required WooCommerce credential dropdown.
• Event: Set to "coupon.deleted" to capture coupon removals. Required field.

Typical use cases: Notify affiliate partners when their promotional codes are deactivated, update external tracking systems to reflect removed coupons, log coupon deletions for promotional auditing, or trigger cleanup workflows in connected marketing platforms.

When to use it: Useful for stores with affiliate programs or complex promotional structures where coupon status must be tracked across systems.