Our community has consistently been vocal about one thing; that integrations were a main cost-driver for projects. Integration Platforms charge a premium, extensions only offer point to point integrations and are hard to adjust, and custom-built quickly runs up the hour estimates. We heard you! At a recent Open Stage session on the Shopware Discord, Product Manager Sam Crudge Hill walked through Nexus, a native iPaaS built into the core platform itself, and has now gone into Early Access.
Why is this one not like the others?
Nexus reframes integrations entirely: instead of treating Shopware as one more endpoint to bolt middleware onto, it treats it as the orchestration layer.
Sam's argument for Nexus is its close coupling with the Shopware core, instead of being limited by available webhooks and APIs, it can tap into all events and data structures developers actually need. While external middleware only has access to APIs and Webhooks, Nexus has a far deeper integration. "The idea behind Nexus," Sam put it, "is it being specifically built for Shopware by Shopware, with a powerful integration that can easily be extended".
Sam is clear that Nexus is not trying to compete with agnostic tools like n8n on breadth. Those tools serve every industry, and they should keep doing that. Nexus is going for depth instead: an event-based, native coupling that external systems can't match from the outside.
The Architecture
Workflows live inside projects: a simple organisational container that separates one set of automations from another. Triggers come in two flavours: a scheduled trigger, which behaves like a cron job, and a Shopware event trigger, which listens for actions inside the shop such as order creation. Under the hood the system runs on Kafka, which provides retries and dead-letter queues when a run fails. That is the part that matters most: because at volume, this provides the reliability companies need for their business critical integrations.
Today, Nexus officially supports four integrations: Microsoft Dynamics Business Central, Slack, AWS S3, and another Shopware Shop via API integration. A moderate start for an Early Access but more is to come. Integrations for Pimcore and NetSuite are already in active development, and, in true Shopware spirit, the real potential will be unlocked through the community marketplace, which we will come back to.
Portable workflows and multi-tenant switching
One capability that shows Nexus being built with Shopware agencies in mind is the new multi-organisation feature. Developers can switch between tenants to move between fully separate environments, each with its own projects, integrations, and permissions. The practical effect, Sam demonstrates, is portability. "If I've done some work with a workflow and I work with another client who needs something very similar but with some slight tweaks, I can switch tenants and I'm going to be able to import said workflow".
This means building a workflow once is investing in a toolbox that can be used for different clients. Node configurations such as field mappings can be saved as templates and reused across workflows. And because export and import rely on unique integration IDs rather than transferring sensitive credentials like API keys, workflows travel between environments without leaking secrets.
Reliability comes first
Sam talks about a rate-limiting node he is building to let developers throttle the volume of data moving through a workflow, preventing a happy-path automation from accidentally overwhelming a hypothetical self-hosted WMS on a Tuesday afternoon. More interestingly, the team is exploring an automated safety system that would detect elevated server error rates from a destination and throttle requests accordingly. Reliability comes first. Integration Platforms form the backbone of critical infrastructure that companies rely on. Orders can’t go missing, and a skipped price update on a product might mean margins evaporate. Reliability is non-negotiable.
Sam explains the team is constantly evaluating the inherent risks that come with integration platforms, and finding solutions to mitigate them.
On observability, the roadmap includes exporting monitoring data to third-party tools such as Grafana, which means developers won't be locked into whatever dashboard Nexus ships. Basic role-based access control – admin, read-only, read/write – is also planned.
Where Nexus is opinionated, Sam was clear: “There is a generic API request node today, but no inbound webhooks or custom code execution yet, due to security concerns we want to solve properly before shipping”.
What's coming: AI-Assisted workflows
To bridge the gap between the current developer-first iteration and the more accessible tool Shopware envisions, AI is planned to play a meaningful role. Shopware's Copilot is on the roadmap to suggest data mappings that users can approve or modify. And, further out, to enable natural-language workflow creation and automatic logical mappings between systems like Microsoft Dynamics and Shopware.
How to take part in Early Access
Best thing? You can take this out for a spin today! If you’re running Shopware 6.7.1 or higher and have enabled Nexus in your shop via your shops admin panel under Nexus and once you’ve linked your shop you can sign-in to Nexus at nexus.shopware.com and you're away! For developers who want to build on what is shipping and provide feedback to shape the service on topics such as rate limiting, marketplace governance, and Copilot-assisted mappings, the Early Access is the moment to do that.
If reading about Nexus made you think of a question, a concern, or a workflow you wish existed, the Shopware Open Stage is where that conversation happens. It runs every third Thursday of the month on the Shopware Discord server, and it is there for the community to present, push back, and provide input.
