What is a Transactional Workflow?

Ranked highest in an event processing queue, a transactional workflow, as its name suggests, sends transactional messages.

How to create a transactional workflow

Your workflow must contain the following:

1. An order-generated event (i.e., "Order added or changed" or "Order status changed.")
2. A group of steps that sends transactional emails or mobile push messages.
3. Between the "Event" block and a "Group of steps" block there are no:
   a. Fixed, dynamic or timed "Delay" node(s);
   b. "Flow splitter" node(s), or
   c. any other "Steps" node(s), even if this node sends transactional messages.

Example:

The workflow above is labeled as transactional; the green lines connect its nodes.

You can also create a partially transactional workflow.

For example:

The first section of the workflow ranks higher, while the node with a fixed time delay makes the other part of the workflow non-transactional.

If you use a transactional campaign but the workflow has not been labeled as transactional, hover over the flash icon to see which blocks are preventing this from happening.

For example:

How a transactional workflow works

A workflow is determined as transactional and prioritized in the event processing queue if API calls transmit events such as new added orders or changes to order data or status.

A workflow will not be prioritized in the event processing queue if:

• new orders or order changes are added via import;
• order statuses are changed manually by users via the interface.