Design Workflow

Design rules for any Novu workflow — independent of whether you author it in the Dashboard (no-code) or in code with @novu/framework. The decisions here (channels, severity, critical, digest, conditions) are the same on both surfaces; only the syntax differs.

Authoring in code? Pair this skill with framework-integration/ for workflow(...), step.*, controlSchema, and Bridge Endpoint setup. Authoring in the Dashboard or via the Novu MCP? After designing here, fill in step content (subject, body, editorType, headers, conditions) using dashboard-workflows/.

When to use this skill

Use it whenever you need to decide what a workflow should look like:

• "Design an order-confirmation workflow"
• "Which channels should I send for a payment failure?"
• "Make this notification critical"
• "Should this be digested?"
• "Add a fallback for offline subscribers"
• "What's the right template for X?"

Do not use it for: triggering an existing workflow (trigger-notification/), authoring code wrappers (framework-integration/), or rendering severity in the UI (inbox-integration/).