Providers
A notification target’s protocol selects its provider. Compare the built-in integrations below, then open a provider page for tested URL formats, query parameters, and direct-call options. For runtime and browser security constraints, see Compatibility.
Send notifications to collaboration platforms, communities, and bot conversations.
- SlackUse incoming webhooks or a bot token to notify Slack channels.
- DiscordPost webhook notifications to Discord channels.
- Lark and FeishuDeliver text and cards to Lark or Feishu incoming webhooks.
- QQ BotNotify QQ users and groups through an official bot.
- TelegramSend bot messages to chats, channels, and forum topics.
Deliver alerts directly to personal devices through dedicated push services.
- BarkPush notifications directly to Apple devices through Bark.
- Server ChanForward alerts through Server Chan v3 or Turbo.
Specialized
Section titled “Specialized”Connect notifications to SMTP, generic HTTP endpoints, or local console output.
- EmailDeliver email through SMTP from the Node.js runtime.
- JSON endpointsPost notification payloads to HTTP or HTTPS endpoints.
- LoggerWrite formatted notifications to local console output.
Target security
Section titled “Target security”Most provider targets contain credentials. Keep complete URLs in environment variables or secret stores, redact them in errors and logs, and rotate a credential immediately if it is exposed.
Runtime APIs and direct calls
Section titled “Runtime APIs and direct calls”Use top-level send() or createNotifier() for protocol routing and consistent batch errors. Import a named provider when you need provider-specific options:
import { slack } from 'statocysts'
await slack.send(process.env.SLACK_TARGET!, notification, { fetchOptions: { timeout: 5000 },})