External Webhook Integration Architecture - commercetools Connector

Data Pipeline Execution

1. Ingestion (Webhook/Batch Job)

• CT Queue: Webhook notifications are pushed to the `ct-queue`.
• CT Queue Listener: This class reads the message from the `ct-queue` and pushes it to the Event Queue.
• Event Queue: This queue is responsible for holding the event message until it is processed.

2. Processing & Payload Extraction

• Message Router: The router reads the message name from the Event Queue and passes it to the corresponding handler.
• Message Handling: The handler reads the message data, fetches additional information via the SDK, maps it to the Fluent data model, and pushes the resulting data to the Fluent OMS.

3. Execution & Customization

• Extensibility: Handlers are fully extensible, allowing partners to modify the logic as required for their specific implementation.
• Route Configuration: Partners can manage message names and override handler classes via the `application-connector.yml`.

Data Storage & Schema Mapping

Developer Extension Points

Implementation Patterns

• Overriding Handlers: Partners can override existing handlers by updating the `application-connector.yml` file to point to a new handler class.
• New Handlers: New handlers can be added by extending the `MessageHandler` class and ensuring the package is within `com.fluentcommerce.connect`.