Skip to content
omnismith docs

Notification Channels

Notification Channels serve as reusable delivery endpoints for automation rules. Once configured, multiple automations can send alerts through the same channel.

1. Supported Channel Types

Section titled “1. Supported Channel Types”
Channel TypeCredentials / Setup RequirementsDescription & Capabilities
TelegramBot Token + Chat IDSends formatted markdown messages to Telegram groups, channels, or private chats via a Telegram bot.
WebhookHTTP POST URL + Secret HeadersDelivers JSON payload alerts to external endpoints (Slack, Discord, custom API backends, Zapier).
Push NotificationChannel Name only (Zero Credentials)Delivers native Android mobile push notifications via Firebase Cloud Messaging to team members’ registered mobile devices.

2. Managing Notification Channels

Section titled “2. Managing Notification Channels”
  1. Navigate to Automation → Notification Channels (or open Channel Settings from an Automation detail page).
  2. Click + Create Channel.
  3. Select Type:
    • For Telegram: Enter your Bot Token (from Telegram @BotFather) and Target Chat ID. Click Send Test Message to verify connectivity.
    • For Webhook: Enter the destination URL, select authentication headers, and test the payload delivery.
    • For Push: Enter a channel name. Members who install and log into the Omnismith Android app are automatically registered to receive notifications.
  4. Click Save Channel.

Notification channel management dialog showing test delivery results

3. Mobile Push Device Registration

Section titled “3. Mobile Push Device Registration”

Native Android device registration requires no manual API keys:

  1. Team members download and install the Omnismith Android application.
  2. Upon logging into the project, the app registers the device token with Firebase Cloud Messaging (FCM).
  3. In automation rules targeting a Push Channel, you can select specific project member accounts to receive the push notification.

💡 Developer Architecture Note

Section titled “💡 Developer Architecture Note”

[!NOTE] Payload Structure & Retry Queue: Webhook delivery payloads include event metadata (event_type, entity_id, template_id, timestamp, attribute_values). If an external webhook endpoint returns a non-2xx status, worker consumers perform exponential backoff retries.

Next Steps

Section titled “Next Steps”

[!TIP]