Boiler Framework / Multichannel notifications
Deliver notifications through selected providers with shared templates, configuration and delivery records.
Manage notification templates and versions.
Configure providers, credentials and routing pools.
Track dispatch attempts and provider outcomes.
A practical example
Built for · Application and customer operations teams
Your application needs to send a customer update without embedding provider-specific templates and connection settings throughout its business logic.
Prepare the channel template and validate its content.
Select an installed provider or provider pool with the required credentials and capabilities.
Track the dispatch attempt, provider acceptance and available delivery evidence separately.
Shared notification operations with a clearer view of what was attempted and what was confirmed.
Illustrative workflow. Connections and deployment scope are agreed for your environment.
Inside the product
Organise channel templates, review revisions and validate content before publication. Keep message content independent of the delivery provider.
Manage provider endpoints, encrypted credential revisions, connection checks and provider pools. Inspect installed capabilities before selecting a route.
Use email, SMS, FCM push and installed chat or webhook adapters. Dispatch through standalone or Rabbit-based composition and distinguish provider acceptance from confirmed delivery.
Provider and channel availability depends on the agreed configuration. Direct APNs is not implemented; provider acceptance does not by itself prove delivery.
