Event-Based Triggers
Launch workflows when products, categories, customers, or orders are created, updated, or deleted. The current implementation listens to entity lifecycle events and dispatches queued workflow execution messages with changed field and revision context.
Event Triggers
Event Triggers
Automating processes and streamlining data management in real-time.
The workflow engine is wired directly into the platform event system. The workflow subscriber listens for `EntityCreatedEvent`, `EntityUpdatedEvent`, and `EntityDeletedEvent`, determines whether the entity is a product, category, order, or customer, and translates that into event names such as `product.created` or `order.updated`.
Instead of executing workflows inline, the subscriber pushes an `ExecuteWorkflowMessage` onto the Messenger queue. That message includes the event name, entity type, entity ID, company ID, changed fields, and revision ID when a revision exists.
This means workflows can react to real application changes without slowing down the original save action, and translation or app-sync workflows can inspect what changed before deciding whether anything should run.
Need automations that respond to real catalog events?
Use event-driven workflows to react to product, category, customer, and order changes without blocking normal editing flows.