When will the extension be available in the Shopware Store?

It is currently going through Shopware's review. Once approved, the store link will appear here. The full documentation is already public.

Do I need n8n as a cloud service?

No. The extension talks to any reachable n8n instance, including a self-hosted one. Data is sent over HTTP POST to whichever webhook address you configure.

What format does the data arrive in?

JSON in the body of the POST request. The exact structure per data type is documented in the API reference.

Can I connect other systems with it?

Yes. The extension posts to any HTTP address. n8n is the obvious recipient, but any system that accepts JSON over POST works just as well.

In reviewIntegrations & middleware

n8n Connector

Products, customers and orders as JSON to n8n webhooks — automation without building your own integration.

Read the documentation Notify me when it is available

At a glance

Products, customers and orders as JSON over HTTP POST
A separate webhook address per data type and per sales channel
Two Flow Builder actions with the webhook address set on the sequence
Documentation bilingual and fully public

Features

Three data types, three webhooks: Products, customers and orders each go to their own webhook address. That keeps different n8n workflows cleanly separated instead of routing everything through one entry point.
Flow Builder actions: Two actions — send customer to webhook and send order to webhook — can hang off any trigger. The target address is set per sequence, so one store can serve several automations in parallel.
Per-sales-channel configuration: Every webhook address can be overridden per sales channel. Several stores in one installation can therefore talk to separate n8n instances.
Trigger from the administration: Three admin API endpoints trigger sending products, customers or orders — from the interface or from your own script.
Filter products by category: Instead of the whole catalogue, sending can be limited to selected categories — useful when only part of the assortment belongs in an external system.
Fully documented: Installation, configuration, flow actions, API reference and troubleshooting are available bilingually at docs.pixelfarben.com — readable before you buy.

Shopware compatibility

Shopware compatibility per extension
Extension	6.0	6.1	6.2	6.3	6.4	6.5	6.6	6.7
n8n Connector	6.0 — Not supported	6.1 — Not supported	6.2 — Not supported	6.3 — Not supported	6.4 — Not supported	6.5 — Not supported	6.6 — Not supported	6.7 — Supported

LegendSupportedNot supported

Requirements

Shopware 6.7
A reachable n8n instance, self-hosted or cloud
PHP with cURL

Frequently asked questions

When will the extension be available in the Shopware Store?: It is currently going through Shopware's review. Once approved, the store link will appear here. The full documentation is already public.
Do I need n8n as a cloud service?: No. The extension talks to any reachable n8n instance, including a self-hosted one. Data is sent over HTTP POST to whichever webhook address you configure.
What format does the data arrive in?: JSON in the body of the POST request. The exact structure per data type is documented in the API reference.
Can I connect other systems with it?: Yes. The extension posts to any HTTP address. n8n is the obvious recipient, but any system that accepts JSON over POST works just as well.

Other extensions

In the Shopware StoreCRM

HubSpot CRM Integration

Customers, orders and products from Shopware into HubSpot — event-driven or on a schedule.

Technical name: VLPHubSpot
Shopware compatibility: 6.7.0.0 – 6.7.12.2

In the Shopware StoreCheckout & cart process

SocialConnect

Technical name: VLPSocialLogin
Shopware compatibility: 6.5.0.0 – 6.7.12.2

In the Shopware StoreCheckout & cart process

Split street and house number

Two separate checkout fields instead of one — while the backend still receives the plain Shopware address field.

Technical name: VLPCustomFields
Shopware compatibility: 6.0.0.0 – 6.7.12.2