Channel providers (email · Telegram · Discord)

Generated from mcp/patterns.registry.json — do not edit by hand; change the registry and run bun run patterns:build.

Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.

Category: Notifications · Tier: light · Risk: low — outbound sends only, credentials encrypted at rest

Email (Resend), Telegram (bot API), and Discord (OAuth2) each implement a common provider interface (send/validateConnection/getProviderName) behind their own connection and token-management flow.

When to use: Use when adding or maintaining an outbound notification channel that must plug into the shared router and outbox.

Docs

• docs/blueprint/notifications/channels.md (GitHub · GitLab)
• docs/stack/notifications/ (GitHub · GitLab)

Code

• src/lib/server/notifications/providers/ (GitHub · GitLab)

Proof

• /showcases/notifications/channels

Machine-readable record: notifications-channels in mcp/patterns.registry.json.