Introduction
Introduction to the Enbbox Framework. Learn how code-first workflow definitions work, supported channels, and how to integrate with Next.js and Express.
Why Code-First?
While the Enbbox dashboard provides a powerful visual workflow editor, some teams prefer defining workflows in code:
- Developers who want type-safe, version-controlled notification logic
- Teams using GitOps or infrastructure-as-code patterns
- Projects with complex conditional notification logic
Framework vs Dashboard
| Feature | Dashboard | Framework |
|---|---|---|
| Workflow creation | Visual drag-and-drop | TypeScript code |
| Version control | Dashboard history | Git |
| Type safety | N/A | Full TypeScript |
| Testing | Manual testing | Unit tests |
| Deployment | Instant | CI/CD pipeline |
| Best for | Non-technical users, rapid prototyping | Engineering teams, complex logic |
How It Works
- Define workflows in TypeScript using the Enbbox Framework SDK
- Serve the workflow definitions via an Enbbox endpoint in your application
- Sync workflows to Enbbox using the CLI or Bridge API
- Trigger workflows using the standard trigger API
The Framework acts as a bridge between your codebase and the Enbbox platform, allowing you to define notification content and logic in code while leveraging Enbbox's delivery infrastructure.
Architecture
Your App (Framework SDK) ←→ Enbbox Platform ←→ Channel Providers
↕ ↕
Your Codebase Dashboard UIFramework
Enbbox Framework overview — define notification workflows in TypeScript with type-safe steps for email, SMS, push, in-app, and chat channels. Code-first approach with full IDE support.
Framework Quickstart
Get started with the Enbbox Framework in under 5 minutes. Define notification workflows in TypeScript, serve them via Next.js or Express, and trigger your first multi-channel notification.