Shopware 6 Flow Builder – Automation & Integration Guide

1. Introduction

Shopware 6 introduced the Shopware Flow Builder, a potent low-code automation tool that lets merchants create event-driven workflows and business processes without having to write any custom code. Through visual configuration, it is intended to provide flexibility, increase efficiency, and simplify operational tasks.

With Flow Builder, merchants can create automated action sequences that are triggered by Shopware system events (e.g., order placed, payment status changed, customer registered). Every flow includes:

• • • Trigger (event) – such as an order status change.
    • Conditions – such as payment method or customer group.
    • Actions – such as sending an email, changing a status, or calling a webhook.

Benefits for Online Stores

• • • Automation
      Reduces manual tasks like sending emails or updating order statuses.
    • Flexibility
      Offers granular control over workflows using conditions and branching logic.
    • Scalability
      Suitable for small businesses as well as large-scale operations by automating complex business logic.
    • Improved Customer Experience
      Enables timely and consistent communication (e.g., shipping updates, thank-you emails).
    • No Coding Required
      Non-technical users can create, edit, and manage flows directly in the admin interface.

Relevant Flow Builder Use Cases in Shopware

• • Send an automated email when an order is completed.
  • Notify internal teams via email or webhook when high-value orders are placed.
  • Automatically assign customers to different groups based on purchase behavior.

2. What is Shopware Flow Builder?

Shopware 6 comes with a visual workflow automation tool called Shopware Flow Builder. By responding to system events and chaining conditions and actions without requiring custom development, it enables merchants to create unique business logic. Store administrators can create flows that automate a variety of operational procedures using its user-friendly drag-and-drop interface.

Three essential components make up each flow:

• Trigger – The event that starts the flow (e.g., “Order placed”).
• Conditions – Optional filters to define when the flow should continue (e.g., “Payment method is PayPal”).
• Actions – The steps executed when the conditions are met (e.g., “Send email to customer”).

Benefits for Online Stores

• Operational Efficiency: Reduces manual tasks and improves order processing speed.
• Personalized Communication: Enhances customer engagement by automating tailored emails based on customer or order behavior.
• Error Reduction: Minimizes the risk of human error in repetitive tasks.
• Time-Saving: Quickly deploy and modify workflows via a no-code interface.
• Adaptability: Allows merchants to respond quickly to business needs or changes without developer intervention.

Relevant Flow Builder Solutions in Shopware

• Order Management: Trigger actions when order status changes (e.g., notify logistics team).
• Customer Segmentation: Assign customers to groups based on behavior or purchase history.
• Email Automation: Automatically send transactional or marketing emails.
• Payment Handling: Trigger refunds, alerts, or escalations based on payment events.
• Third-party Integrations: Use webhooks to connect to external systems and automate cross-platform tasks.

3. Requirements

Before you build your first flow, it is worth clearing up a misconception that costs teams a lot of time: the Flow Builder is part of the Shopware 6 core. It is listed in Shopware’s own feature overview for the Community Edition, so you do not need a paid plan and you do not need to install anything. There is no separate “Flow Builder plugin”.

What is free and what is not

The base Flow Builder — triggers, conditions and actions — is available to every Shopware 6 installation. Three extensions are tied to a paid plan and arrive through the Shopware Commercial extension:

• Sharing flows (import and export) — from the Rise plan, available since Shopware 6.4.19.0.
• Call URL / webhook actions — from the Evolve plan.
• Delayed actions — Beyond plan only.

If a guide tells you the Flow Builder itself is commercial, it is out of date.

System requirements

There are no Flow-Builder-specific requirements. The normal Shopware 6 requirements apply. For the current 6.7 line Shopware documents:

• PHP 8.2, 8.3 or 8.4
• MySQL 8.0.17 or newer, or MariaDB 10.11 or newer
• Node.js 20 or newer

Older guides still name PHP 7.4 and MySQL 5.7. Those values belong to the 6.4 era and no longer apply.

Two things worth preparing

Mail configuration. Most first flows send an email. Configure your mail service in the administration before you build the flow, otherwise the action fires and nothing arrives.

API credentials, only if you need them. A Client ID and Client Secret are relevant for the Call URL action, which requires the Evolve plan. For everything else you do not need them.

4. Creating Your First Flow

The Flow Builder is part of the Shopware 6 core, so nothing needs to be installed. You can start automating processes right away tailored to your store’s operations. Below is a step-by-step guide to creating a basic flow.

Example: Send a Confirmation Email When an Order Is Placed

1. Navigate to Flow Builder
   Go to Settings → Flow Builder → Add Flow.
2. Define Basic Flow Information
   Name: Order Confirmation Email
   Description: (optional) Sends an email to the customer when a new order is placed.
   Priority: set based on execution order (lower numbers = higher priority).
   Active: toggle ON to enable.
3. Set a Trigger
   Under Trigger, select Order placed (Event: checkout.order.placed ).
4. Add a Condition (Optional)
   Add condition: Payment Method → is → PayPal (only if paid via PayPal).
5. Add an Action
   Choose Send email; configure recipient (Customer email), template (Order confirmation), and language.
6. Save and Test
   Save the flow (ensure Active). Place a test order to confirm the email is sent.

Other Examples of Useful Flows

• Order value above €500 → Notify sales manager via email.
• Customer registered → Send welcome discount email.
• Payment failed → Create internal task or webhook alert.

5. Testing the Flow Builder

1. Simulate the Triggering Event
   Perform the event (e.g., place a new order).
2. Check the Outcome
   Verify emails, tasks, or webhooks as configured.
3. Review Execution Logs
   In Settings → Flow Builder → Executions to see success/failure details.
4. Adjust and Re-Test
   Modify conditions/actions and repeat until correct.

6. Troubleshooting

Common Errors and Issues

• Flow Not Triggering – ensure flow is active, trigger event matches, and conditions aren’t excluding it.
• Emails Not Sent – verify SMTP settings and that the email template is assigned to the correct sales channel.
• Webhook Failures – confirm endpoint is reachable, credentials valid, payload format correct.
• Multiple Flows Conflict – use differing priorities to control execution order.

How to Find and Analyze Logs

• Execution Logs – Settings → Flow Builder → Executions.
• System Logs – server logs in /var/log/ (e.g., shopware.log ).
• Developer Tools – use Postman or browser dev tools to inspect webhook requests.

7. Best Practices & Security

Top Techniques

• Name Flows Clearly – consistent, descriptive titles ease maintenance.
• Use Conditions Wisely – avoid overly broad triggers.
• Set Priorities Strategically – leave gaps (100, 200, 300) for future flows.
• Test in Staging – validate complex flows off-line first.

Security Guidelines

• Expose webhooks only to trusted HTTPS endpoints.
• Store API credentials securely and rotate them regularly.
• Audit execution logs for suspicious activity.
• Limit administrator access via ACL roles.

8. Frequently Asked Questions (FAQ)

Q1: Is Flow Builder included in Shopware’s free Community Edition?
A: Yes. The Flow Builder is part of the Shopware 6 core and Shopware lists it in the feature overview for the Community Edition. What is tied to a paid plan are three extensions: sharing flows (Rise and above), the Call URL / webhook action (Evolve and above) and delayed actions (Beyond only). Those arrive through the Shopware Commercial extension.

Q2: Can I trigger custom events in Flow Builder?
A: Yes. Developers can dispatch custom events in code; if registered, Flow Builder can listen to them.

Q3: Can one flow contain multiple actions?
A: Absolutely. A single flow may include several sequential actions.

Q4: Does Flow Builder work in multilingual stores?
A: Yes. Assign language-specific templates and configure flows per sales channel or locale.

Related topics

• Shopware Automation Platform
• Flow Builder- Workflow automation for business logic
• Shopware LangChain Automation
• Low-Code Automation in Shopware