---
title: Webhooks and Event-Driven Architecture | Shopware Community Hub
description: >-
  Explore how webhooks and event-driven architecture enable real-time, efficient
  integrations between Shopware and external systems, reducing API load while…
canonical_url: >-
  https://hub.shopware.com/learn/unit/solutions-architect-webhooks-and-event-driven-architecture
---

# Webhooks and Event-Driven Architecture

<LearningObjectives>

- Understand the concept of **webhooks** and how they are used to automate integrations.
- Explore the benefits of an **event-driven architecture** and how it improves system responsiveness and reduces API load.

</LearningObjectives>

# Webhooks and Event-Driven Architecture

Webhooks and event-driven architecture provide real-time data exchange between Shopware and third-party systems, reducing the need for constant polling and improving integration efficiency.

1. **Webhooks**:

   - Webhooks are HTTP callbacks that are triggered by specific events in Shopware, such as an order being placed or a product being updated. When these events occur, Shopware automatically sends data to a designated URL.
   - **Use Cases**: This is commonly used for notifications or real-time updates, such as sending order details to an ERP or notifying a CRM of new customer registrations.
   - **Setting Up Webhooks**: Webhooks can be configured directly in Shopware’s Flow Builder for simple tasks, or programmatically via plugins for more advanced scenarios.  

   More about Shopware webhooks in these articles: [Webhook Actions in Flow Builder](https://docs.shopware.com/en/shopware-6-en/settings/Flow-Builder#webhook-actions-in-flow-builder) and [Webhook Event Reference](https://developer.shopware.com/docs/resources/references/app-reference/webhook-events-reference.html).

2. **Event-Driven Architecture**:

   - An event-driven architecture allows systems to respond to events asynchronously. Instead of constantly checking for changes, third-party systems only act when relevant events occur.
   - **Benefits**:
   - **Reduced Load**: By only sending data when changes occur, event-driven architectures reduce API load and bandwidth usage.
   - **Real-Time Responsiveness**: Third-party systems can react immediately to events, improving responsiveness and user experience.
   - **Scalability**: This approach scales well as it minimizes unnecessary data requests, keeping systems more efficient and responsive even with high data volumes.

**Examples of Event-Driven Integration Scenarios**:

- **Order Processing**: When an order is placed, a webhook notifies the ERP to start order fulfillment immediately, reducing manual intervention.
- **Inventory Updates**: When inventory levels change, webhooks send updated data to third-party systems, ensuring accurate inventory records across all platforms.

## Best Practices

- **Use Webhooks for Real-Time Updates**: For actions that require immediate responses, such as order or inventory changes, configure webhooks to notify external systems instantly.
- **Combine with API for Data Sync**: Use webhooks for real-time notifications and the API for scheduled batch updates, creating a balanced integration approach.