Notification

Last modified: May 22, 2026

Introduction

Notification allows you to suspend a workflow path until the workflow is notified.

It can be used in the following two ways:

  • Notification can be used as a standalone event on a workflow path. It suspends the workflow path until the workflow receives a notification. Use it as a standalone event when you want the path to be blocked until the notification is received. For example, when a workflow needs to wait for an external system to confirm that a payment is processed before continuing.

    Standalone Notification event

  • Notification can also be attached to another workflow activity as a Boundary Event. Use it as a boundary event when you want to either run a parallel path alongside the parent activity (non-interrupting) or redirect path execution by aborting the parent activity (interrupting).

    Notification boundary event

Properties

Notification properties consist of the following sections:

General Section

The Caption describes what happens in this element. It is displayed under the workflow element to make the Notification easier to read and understand without the need to add annotations.

Boundary Properties Section

The Interrupting property sets the notification boundary event to be either interrupting or non-interrupting.

By default, it is set to No, which means that the notification boundary event is non-interrupting. When it is set to Yes, the notification boundary event is interrupting. For more information, see Boundary Events.

Common Section

Name is the internal name of the Notification. When referring to the element in an application, you will use this name. It must be unique within the workflow, but you can have two Notification events with the same name in different workflows.

Sending Notification

To trigger the Notification event and resume the workflow path, use the Notify Workflow microflow activity.

Read More