Notify: One Platform for Email, Slack, LINE, Webhooks
Discover how a unified notification platform called notify was built to handle email, Slack, LINE, and webhooks in just two and a half months.
Stock photo for illustration only, not from the actual event
- Consolidated notification code for email, Slack, LINE, and webhooks into a single platform
- Architected response bodies to handle non-error outcomes like skips and opt-outs in 200 responses
- Grew to 13 registered projects by September 2026 with continuous feature requests
- Migrated to AWS Amplify hosting after tunnel connection drops in August 2026
As companies scale their product lineup, core features like login, billing, and notifications inevitably become shared necessities. Having already unified authentication into ELN ID and billing into a dedicated billing platform, the engineering team introduced the third pillar of this lineup: a notification platform named notify.
The initiative began when the team audited notification code across their support product, monitoring product, and corporate site. Each had independently implemented email via Amazon SES and webhooks for Slack. Because different people wrote these components at different times, behavioral inconsistencies were widespread across the codebase.
Stock photo for illustration only, not from the actual event
[[IMAGE_ai-insight]]
Centralizing notifications into a dedicated micro-service or shared platform is a common architectural pattern to eliminate code duplication, enforce security policies, and standardize error handling. Offloading notification delivery logic frees individual product teams from managing disparate third-party API integrations.
The extraction started in late June 2026 when the email-sending logic was pulled out of the corporate site as a library. By July 16, an architecture decision record formalized that notify would become a standalone product equipped with its own screens and API. The very next day, the team deployed four-channel support, a send orchestrator, an admin console, and an SDK in a single push.
From a consuming product's perspective, notifications produce outcomes that are neither standard successes nor communication errors. Examples include duplicates skipped because the same send ID was already processed, or messages withheld due to user opt-outs. Rather than treating these as HTTP 4xx anomalies, the platform returns them inside standard 200 response bodies using a fixed vocabulary.
"A countermeasure that is designed but not deployed protects nothing."
Dev.to
The company's cost-monitoring product demonstrates why this distinction matters in practice, treating duplicate responses as delivered but not fresh. This granular tracking is only possible because outcome data survives inside the response payload rather than being lost to generic error statuses.
By September 2026, 13 distinct projects were integrated into the platform. Ongoing consumer demand continuously drives new capabilities, such as UI-based Slack channel selection and localized authentication emails for international users.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment