Notification Channels

Notification Channels serve as reusable delivery endpoints for automation rules. Once configured, multiple automations can send alerts through the same channel. A Webhook channel also serves as the connection for an automation’s HTTP Request action, which calls an external API and can keep parts of its response on a record.

---

1. Supported Channel Types

Channel Type	Credentials / Setup Requirements	Description & Capabilities
Telegram	Bot Token	Sends formatted markdown messages to Telegram groups, channels, or private chats via a Telegram bot.
Webhook	Base/Target URL + Auth (None, Bearer Token, Basic Auth) + Custom Headers	Delivers HTTP requests (POST, PUT, PATCH, GET, DELETE) to external APIs, Zapier or n8n. Also the base URL and credentials for HTTP Request actions.
Push Notification	Channel Name only (Zero Credentials)	Delivers native Android mobile push notifications via Firebase Cloud Messaging to team members’ registered mobile devices.

---

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).
   • For Webhook:
     • Base/Target URL: Enter destination URL (e.g. https://api.example.com or full webhook URL).
     • Authorization Type: Select None, Bearer Token (Authorization: Bearer <token>), or Basic Auth (Authorization: Basic <base64(user:pass)>).
     • Custom Headers: Define reusable key-value HTTP headers applied to all requests on this channel (e.g., X-API-Key, X-System-Source).
   • For Push: Enter a channel name. Members who install and log into the Omnismith Android app are automatically registered to receive notifications.
4. Rate limit: the most messages the channel sends per minute (1–1000, default 20). See the Rate limit note below.
5. Click Run Test to verify endpoint connectivity.
6. Click Save Channel.

---

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.

---

Rate limit

Every message sent through a channel counts against its per-minute rate limit, whichever automation or record it is for. The count restarts at the top of each minute. Once the limit is reached, further sends that minute fail and are recorded as failed actions in the automation’s execution log; they are not queued or retried.

The default of 20 matches Telegram’s limit for messages to one group. Raise it on Webhook channels that carry high-volume HTTP Request traffic. Tests with Run Test do not count.

💡 Webhook delivery

• Body: a Webhook action sends the JSON rendered from its Payload Template ({} when empty) for POST, PUT and PATCH; GET and DELETE send no body. The URL path is appended to the channel’s base URL unless it is a full https:// URL.
• Outcome: a 2xx answer counts as delivered. Any other status, a timeout (10 seconds) or a connection error is recorded as a failed action in the automation’s execution log. It is not retried, so check the log for failed deliveries.
• Private networks: requests, including Run Test, to private or internal addresses such as localhost, 10.x.x.x or 192.168.x.x are refused with Target resolves to a private network address.

---

Next Steps

• Attach notification channels to trigger rules, or call APIs with HTTP Request actions, in Automations.
• Manage project team members and mobile devices in Projects & Members.