Layer 04 · Communication Layer
Reach users on every channel from one send API
Reach users through email, SMS, push, and in-app notifications with one SDK. Templates, delivery, and notification center are platform modules — not vendor integrations each team assembles.
Why this layer
Built into the platform, not bolted on
Every module in this layer solves the same class of problem the same way — regardless of who implements it.
01
Twilio-style canonical delivery
Like OTP through Twilio, every outbound message follows one API, one template model, and one delivery flow — regardless of who wrote the integration code.
02
In-app and outbound unified
Notification center read state, push delivery, and email sends share event triggers. Users see consistent messaging across channels.
03
Templates versioned in config
Message templates live in platform configuration — deployable, reviewable, and consistent across environments. No hardcoded copy scattered through codebases.
Canonical implementation
One path for every author
Junior developers, senior engineers, and AI agents produce the same standard output.
How Conflux does it
One send path for email, SMS, push, and in-app
Communications and notifications are separate modules but share the same event model. Trigger a platform event — the right channels deliver with tracking built in.
Canonical path
conflux.communications.send() with channel and template selection
Template variables validated against typed schemas
Delivery status, bounces, and retries handled by the platform
In-app notifications sync read state across devices
What you get
Send multi-channel messages without vendor SDK sprawl
Ship an in-app notification center out of the box
Manage templates through config, not scattered strings
Track delivery and engagement from one surface
01 · Communication Layer
Every channel through one send API
Email, SMS, WhatsApp, and push delivery with template management, variable substitution, and bounce handling. The Twilio model applied across all outbound channels.
Communications · One canonical path
SDK
await conflux.comms.send({ template, to })CLI
conflux comms templates list
Config
comms: channels: [email, sms, push]
What's possible with Communications
01
Email, SMS, WhatsApp, and push through one send API
02
Template management with variable substitution
03
Delivery tracking and bounce handling
02 · Communication Layer
In-app notification center for your users
Read/unread state synced across devices, triggered by platform events or application code. Users get one notification surface — not a custom inbox per app.
Notifications · One canonical path
SDK
await conflux.notifications.send({ userId, body })CLI
conflux notifications templates
Config
notifications: center: enabled
What's possible with Notifications
01
In-app notification center for users
02
Read/unread state synced across devices
03
Triggered by platform events or application code
Explore
Continue through the platform
Nine layers, one cohesive stack. Browse adjacent layers or return to the full registry.