AlexLobanov
NNovu
•Created by AlexLobanov on 4/15/2025 in #💬│support
Novu Cloud | Multiple Slack destinations together with Email and In-APP
We're building a B2B application that provides services to our customers. For user management, we're using Clerk, where each customer is associated with a Clerk organization.
Each organization can have multiple users, and we’re designing a system to support three main notification workflows:
Notification Workflows:
1. Anomaly Detection Alerts
1.1 Channels: In-app, email, Slack
1.2. Scope: Organization-wide (all users in a tenant)
2. Release Notes Updates
2.1.Channels: In-app, email, Slack
2.2. Scope: Organization-wide
3. Report Generation Completion
3.1 Channels: In-app, email, Slack
3.2 Scope: User-specific (tied to the user who triggered the report)
Requirements:
We need to support configurable and flexible notification routing while preventing redundant alerts.
Specifically:
Tenant Structure
All users should be grouped under a Tenant, where the tenant ID is the Clerk organization ID.
User-to-Workflow Mapping
Each user may be subscribed to multiple workflows.
To support per-user and per-workflow Slack channel destinations, we'll assign a unique subscriberId using a combination of: subscriberId = user_id + org_id + workflow_id
Slack Destination Configuration
Each organization should be able to configure one or more Slack channels:
1. Org-level channels for workflows like Anomaly Detection or Release Notes
2. User-level channels (or fallback options) for workflows like Report Generation
====
Open Questions:
We’re currently unsure how to:
Design workflow triggers in a way that avoids sending duplicate alerts (especially in cases where multiple users in the same org might see the same event).
Efficiently deduplicate organization-wide alerts while maintaining user-level alerting for individual workflows.
Is there any ideas on how to solve it using Novu?
6 replies