Design a Novu notification workflow with AI
Choose the right channels, severity, delays and digest behaviour for a product event. Review the plan before building the actual notification flow in Novu.
Design a Novu notification workflow with AI when a team wants to decide how an order confirmation or payment failure should reach the customer. The novu-design-workflow skill starts with the intended outcome and the channels your organisation supports. It distinguishes the urgency of a message from Novu’s critical setting, which affects preferences and digest behaviour.
A customer already using the application may see an in-app update immediately. A redundant push adds noise, while a receipt by email could still be useful for later reference. The workflow plan makes those decisions explicit and keeps channels named in the brief instead of quietly adding others.
What it does
- Choose channels for a transactional product event.
- Set severity separately from critical delivery.
- Group repeated events into a digest where appropriate.
- Plan a fallback based on existing subscriber state.
- Specify the condition under which a step should run.
Install and use
- Install the skill and provide an event brief, allowed channels and urgency. Implementing the plan requires an authorised Novu project, through its dashboard or official framework.
- Ask, “Design an order-confirmation flow using only in-app and email. Explain which step should be immediate and which may be delayed.”
- Review preference handling and the proposed channel sequence before creating the live workflow.
FAQ
Source
Made by Novu. Original skill: novu-design-workflow, published on GitHub under the MIT licence.
View on GitHub