Here you learn all about workflows
Name and Identifier
Trigger
Channels
Selecting existing workflow group and creating a new workflow group
ApiKey <API_KEY>
Workflow Promotion Error: Notification Group Id Not Found
Go to the workflow settings in Novu's interface.
Remain within the general settings tab.
Check the right-hand side for the notification group dropdown.
Verify if any group is selected. The group's association will be demonstrated here.
How to disable a workflow for a single 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.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.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?
transactionId
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.transactionId
.