MAGENTO n8n INTEGRATION: AUTOMATE MAGENTO WITH N8N

Keeping product information current is crucial for e-commerce success. This action lets you modify any product attribute—price, description, stock status, or custom fields—without touching the Magento admin panel.

Key parameters: Credential to connect with (required), Resource set to "Product", Operation set to "Update", SKU (required to identify the target product), and Update Fields where you add the specific fields you want to change.

Use cases: Automatically adjust prices based on competitor monitoring tools, update stock quantities after syncing with warehouse management systems, mark products as out-of-stock when inventory hits zero, or bulk update product descriptions or SEO metadata from a content management system.

This action is particularly powerful when combined with triggers from other systems. For example, when your ERP updates inventory, a webhook can trigger n8n to update the corresponding product in Magento automatically.

When you need to work with multiple products at once—for inventory audits, bulk updates, or reporting—this action retrieves a list of products based on your criteria. It's the foundation for any workflow dealing with catalog-wide operations.

Key parameters: Credential to connect with (required), Resource set to "Product", Operation set to "Get Many", Return All toggle, Limit (numeric field for maximum products to retrieve), Filter dropdown to apply conditions, and Options for additional customization.

Use cases: Export your entire product catalog to a spreadsheet for auditing, find products below a certain stock threshold for reordering alerts, sync product data to external marketplaces like Amazon or eBay, or generate daily inventory reports sent via email or Slack.

Retrieving specific product information is essential for workflows that need to check stock levels, verify prices, or route data based on product attributes. This action fetches complete product details using the SKU identifier.

Key parameters: Credential to connect with (required), Resource set to "Product", Operation set to "Get", and SKU text input field where you specify the Stock Keeping Unit of the product to retrieve.

Use cases: Check current stock levels before accepting orders from external channels, verify product prices match across multiple sales platforms, retrieve product details to include in customer notification emails, or build conditional workflows that behave differently based on product attributes.

When you execute this action, n8n returns the complete product object including all attributes, stock information, pricing, images, and custom data fields.

Sometimes products need to be removed from your catalog—discontinued items, duplicate entries, or test products. This action permanently deletes a product from Magento using its SKU.

Key parameters: Credential to connect with (required), Resource set to "Product", Operation set to "Delete", and SKU text field where you enter the Stock Keeping Unit of the product to remove (required).

Use cases: Clean up test products after development cycles, remove discontinued products automatically when flagged in your PIM, delete duplicate products identified by an audit workflow, or archive seasonal products at the end of a campaign.

⚠️ Warning: Product deletion is permanent in Magento. Consider using the Update action to set product status to "disabled" instead if you might need the product data later.

Creating products programmatically in Magento opens the door to powerful catalog management automation. This action allows you to add new products to your store directly from n8n workflows, making it perfect for bulk imports, supplier integrations, or any scenario where manual product entry becomes a bottleneck.

Key parameters: Credential to connect with (required), SKU (unique identifier), Name (display name), Attribute Set Name or ID (specifies attribute set), Price (numeric field defaulting to 0), and Additional Fields (expandable section for more product attributes like description, stock, weight, visibility).

Use cases: Import products from a supplier's spreadsheet or API automatically, create test products during development workflows, sync products from a PIM (Product Information Management) system, or duplicate products across multiple Magento stores.

This action works best when combined with a data source like Google Sheets, Airtable, or a webhook receiving product data from external systems.

Once an order is packed and ready to go, this action marks it as shipped in Magento. This triggers customer notification emails and updates the order status throughout your system.

Key parameters: Credential to connect with (required), Resource set to "Order", Operation set to "Ship", and Order ID text field specifying which order to mark as shipped (required).

Use cases: Automatically mark orders as shipped when your fulfillment center confirms dispatch, trigger shipping status when tracking numbers are generated by carrier integrations, batch ship multiple orders after daily fulfillment runs, or connect with 3PL (third-party logistics) systems that notify when orders leave the warehouse.

This action typically lives at the end of a fulfillment workflow, after inventory is reserved, labels are printed, and packages are handed to the carrier.

For order management workflows that operate at scale—daily reports, batch fulfillment, or analytics—this action retrieves multiple orders based on your specified criteria.

Key parameters: Credential to connect with (required), Resource set to "Order", Operation set to "Get Many", Return All toggle, Limit (numeric input, default 5), Filter dropdown to apply conditions like order status or date range, and Options for additional customization.

Use cases: Generate daily sales reports sent to management via email, pull all "pending" orders for batch fulfillment processing, sync recent orders to your accounting software or ERP, or build dashboards showing order volume and revenue metrics.

Understanding individual order details is essential for customer service, fulfillment, and troubleshooting. This action retrieves complete information about a specific order using its unique identifier.

Key parameters: Credential to connect with (required), Resource set to "Order", Operation set to "Get", and Order ID text field where you enter the unique order identifier (required).

Use cases: Fetch order details when a customer contacts support via live chat, check order status before triggering fulfillment workflows, retrieve shipping address for integration with shipping carrier APIs, or pull order data for custom invoice generation or reporting.

The returned data includes everything about the order: customer information, billing and shipping addresses, line items, payment method, totals, and order status history.

When customers change their minds, fraud is detected, or inventory issues arise, this action cancels an order in Magento. It updates the order status and can trigger refund processes depending on your Magento configuration.

Key parameters: Credential to connect with (required), Resource set to "Order", Operation set to "Cancel", and Order ID text input specifying the order to cancel (required).

Use cases: Automatically cancel orders flagged as fraudulent by your detection system, cancel abandoned cart orders that remain unpaid after X days, process cancellation requests from customer service tools, or cancel orders when inventory checks reveal products are out of stock.

💡 TIP: Combine this action with a notification step to alert your customer service team whenever an order is automatically cancelled. This helps maintain great customer relationships even when things don't go as planned.

Invoice creation is a critical step in the order-to-cash cycle. This action generates an invoice for a specific order, which is typically required before an order can be shipped in Magento's standard workflow.

Key parameters: Credential to connect with (required), Resource set to "Invoice", Operation set to "Create", and Order ID text field where you specify which order to invoice (required).

Use cases: Automatically create invoices when payment is confirmed via webhook, generate invoices for orders imported from external sales channels, batch invoice processing for B2B orders on net payment terms, or trigger invoice creation as part of a complete order processing workflow.

After creating the invoice, you can combine this with the Ship Order action to complete the fulfillment process entirely within n8n.

Customer data evolves over time—addresses change, preferences update, and new information becomes available. This action modifies existing customer records with new data.

Key parameters: Credential to connect with (required), Resource set to "Customer", Operation set to "Update", Customer ID (required), Email (optional), First Name (optional), Last Name (optional), Website Name or ID, and Update Fields section for additional fields to modify.

Use cases: Sync customer profile updates from your CRM to Magento, update customer groups based on purchase behavior or loyalty tiers, correct customer data flagged during quality audits, or merge customer information from multiple sources.

For marketing campaigns, customer analysis, or bulk operations, this action retrieves multiple customer records based on your criteria.

Key parameters: Credential to connect with (required), Resource set to "Customer", Operation set to "Get Many", Return All toggle, Limit (default 5), Filter dropdown for search conditions, and Options for additional settings.

Use cases: Export customer lists to email marketing platforms like Klaviyo or Mailchimp, generate customer reports for analysis and segmentation, find customers who haven't purchased recently for win-back campaigns, or sync customer data to your CRM on a scheduled basis.

Retrieving customer data is fundamental for personalization, support, and marketing workflows. This action fetches complete customer information using the unique customer ID.

Key parameters: Credential to connect with (required), Resource set to "Customer", Operation set to "Get", and Customer ID text field where you enter the unique customer identifier (required).

Use cases: Fetch customer details when they contact support via helpdesk integration like Zendesk, retrieve customer data to personalize marketing emails, check customer tier or group before applying special pricing, or pull customer addresses for integration with shipping services.

When customers request account deletion (GDPR, CCPA, or personal preference) or you need to clean up duplicate records, this action removes a customer from Magento.

Key parameters: Credential to connect with (required), Resource set to "Customer", Operation set to "Delete", and Customer ID text field specifying which customer to delete (required).

Use cases: Process GDPR "right to erasure" requests automatically, clean up duplicate customer accounts identified by matching algorithms, remove test accounts after development or QA cycles, or handle account closure requests from customer service tools.

⚠️ Important: Customer deletion is permanent and may affect order history reporting. Ensure compliance with your data retention policies before implementing automatic customer deletion.

Building your customer database programmatically is essential for omnichannel businesses. This action creates new customer accounts in Magento, allowing you to sync customers from CRMs, import from other platforms, or register customers who purchase through external channels.

Key parameters: Credential to connect with (required), Resource set to "Customer", Operation set to "Create", Email (required—uniquely identifies the customer), First Name (optional but recommended), Last Name (optional but recommended), and Additional Fields section for extra customer data like date of birth, gender, tax/VAT number, or custom attributes.

Use cases: Sync new leads from HubSpot or Salesforce to Magento for remarketing, create customer accounts when users sign up through a separate application, import customers from a legacy e-commerce platform during migration, or register B2B customers automatically when they're approved in your sales pipeline.