Workflows

A workflow holds the entire flow of steps (nodes) that are sent to the subscriber. This is where all the different channels are tied together under a single entity.

​

Structure

A workflow acts as the blueprint for the notifications that will be sent. The workflow encapsulates the entire flow and rules of messages that are being sent. This is where all the different channels, filters, rules and actions are tied together under a single entity.

​

Workflow Components

​

Execution of Workflow Steps

Once a workflow is initiated by its trigger, the steps (and channels) within the workflow are executed in a specific sequence. This sequential execution ensures that each step is completed before the next one begins, maintaining a controlled and orderly flow of the notification process. Here’s what you need to know about this process:

• Sequential Execution: Each channel in the workflow is activated one after the other, in the order they are listed within the workflow. This method ensures that each step is given the necessary attention and that dependencies or prerequisites of later steps are adequately met.

• Order of Channels: The order in which channels are listed in the workflow is crucial, as it dictates the sequence of their execution. You should carefully consider the order when setting up your workflows to align with your notification strategy.

Sequential execution provides a predictable and reliable workflow process, ensuring that messages are sent out in an organized manner and that each step’s output potentially influences the subsequent ones.

​

Workflow Groups

Workflow groups are used to categorize workflows based on their purpose or function. This grouping allows you to organize your workflows in a way that makes sense to you and your team. For example, you may want to group all your onboarding workflows or group all your transactional workflows together. You can create as many groups as you need and assign workflows to them as you see fit.

​

Working with workflow groups

To create a workflow group, follow these steps:

1. Navigate to the Workflows page in the Novu interface.
2. Select any workflow from the list.
3. Click on the cog icon on the top right side to open the workflow settings.
4. Stay on the General settings tab.
5. Click on the Workflow Group dropdown and select the group you want to assign to the workflow.
6. To create a new group start writing some text and a Create New option will appear. Click on it to create a new group and select this group for this workflow.
7. Click on the update button on the top right side to save the changes for the entire workflow.

Selecting existing workflow group and creating a new workflow group

To edit a workflow group name, follow these steps:

1. Navigate to the Settings page in the Novu interface.
2. Copy the API Key from settings (Each environment has a different API Key).
3. Navigate to API Reference page to fetch all workflow groups in Novu documentation.
4. Use the previously copied API Key as the Authorization header. Make sure it is in the correct format ApiKey <API_KEY>
5. Click on the send button to fetch all the workflow groups.
6. In the response field copy the _id field of the workfow group that you want to edit.
7. Use the copied _id as the path parameter in the request URL of workflow update API using the same API Key as the Authorization header. Write the new name for the group in the body field.
8. Click on the send button to update the workflow group name.

​

Searching Workflows

Workflows can be searched by their name or trigger identifier. This feature makes it easy to find the desired workflow and quickly access its details.

Workflow search option

Result after serching workflow having event in name

​

FAQs

Workflow Promotion Error: Notification Group Id Not Found

To address the error “Notification Group Id not found” when promoting the workflow from dev to prod, it’s essential to check the allocation of a notification group to the workflow. Here is an outlined process to validate:

1

Go to the workflow settings in Novu's interface.

2

Remain within the general settings tab.

3

Check the right-hand side for the notification group dropdown.

4

Verify if any group is selected. The group's association will be demonstrated here.

New notification group can also be created in the drop-down

If a notification group is not associated, this is likely the cause of the issue. Ensure that the relevant Notification Group Id is assigned in the settings. To do so, you would need to choose one from the drop-down list in the workflow settings .

Remember, deleting a workflow is not recommended because it can lead to unexpected behavior like this. Instead, updating the workflow group associated with the specific workflow is the right process to address the issue.

How to disable a workflow for a single subscriber?

When all channels are turned off for that subscriber then subscriber will not receive any messages from any channel step, effectively disabling the workflow for that subscriber.

2. If you want to make a workflow inactive or active, you can do so through the workflow settings. However, it’s important to note that this action will affect all subscribers.

3. To disable a workflow for only one subscriber, you can achieve this by having the subscriber disable all channels for that specific workflow through their subscriber preferences. This action will solely impact that particular subscriber.

What is the difference between workflowId and trigger identifier?

workflowId is a MongoDB-generated identifier within the Novu system, serving as a unique identifier for workflows. It cannot be modified or altered once generated. This workflowId is utilized in several APIs, including the GET Workflow API.

A trigger identifier is a distinctive label utilized to activate a workflow, typically represented in a slugified format. Novu generates this identifier automatically based on the workflow’s name, and it can be modified at a later time if needed. Currently, our system supports only a single trigger identifier per workflow. However, as part of our future plans, we intend to enable the use of multiple trigger identifiers for a single workflow, each capable of initiating the workflow from different sources.

Hence, while workflowId refers to the umbrella structure that holds the entire flow of messages, the trigger identifier is the specific event that starts this sequence.

How does Novu prevent duplicate notifications sent to subscribers?

The transactionId within Novu is a unique identifier that is used to ensure the idempotent nature of notification delivery.

When you trigger an event to send a notification, you have the option to provide a transactionId. If you do not provide one, Novu will generate a UUID for you.

This identifier is particularly useful for preventing the same notification from being sent multiple times in case the trigger event is inadvertently called more than once.

By leveraging the transactionId, you can make idempotent requests, which means if the same transactionId is used in another request, Novu’s API will recognize it and will not send the same notification again.

This upholds the principle of idempotency, ensuring that the effect of the operation is the same, no matter how many times the request is repeated with the same transactionId.