Skip to main content

Documentation Index

Fetch the complete documentation index at: https://frimty.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Alius delivers notifications through four hubs: Slack, Email, Telegram, and Discord. Each must be connected before it can be selected in a trigger. Connections are managed on the Integrations page.

​
Slack

Slack is connected via OAuth 2.0. Alius installs a bot in your workspace that posts messages to selected channels.

​
Connecting Slack

  1. Go to Integrations in the sidebar.
  2. Click Connect to Slack.
  3. You’ll be redirected to Slack’s OAuth authorization page. Select your workspace and click Allow.
  4. After authorization, Alius stores the bot token and the status changes to Connected.

​
Enabling Channels

Once connected, a list of your workspace’s public channels appears.
  1. Toggle on the channels where Alius should be allowed to post.
  2. Click Save — the bot automatically joins each enabled channel.
Only enabled channels appear in the trigger form’s channel picker. The bot must be a member of a channel to post messages to it.

​
Sending a Test Message

Click Send test notification to post a test message to all enabled channels. This confirms the token is valid and the bot has channel access.

​
Disconnecting Slack

Click Disconnect to remove the Slack integration. This clears the bot token, disables all channel mappings, and stops all Slack notifications. Your triggers are preserved and will resume sending once Slack is reconnected.
Alius uses a Slack bot token with permission to read channels and post messages. It does not read your team’s private messages.

​
Email

Email notifications are sent via Resend. You manage a list of verified recipient addresses — only verified and active recipients receive notifications.

​
Adding a Recipient

  1. Go to Integrations → Email section.
  2. Enter an email address and click Add Recipient.
  3. Alius sends a verification email to that address.

​
Verifying a Recipient

The recipient must click the verification link in the email. Until verified, the address will not receive notifications.
Verification tokens expire. If the link is not clicked in time, you can regenerate the token by editing the recipient and changing the email address, then re-entering it.

​
Managing Recipients

Each recipient has two states that can be toggled independently:
StateDescription
VerifiedSet automatically after the recipient clicks the link
ActiveControls whether this address receives notifications
A recipient must be both verified and active to receive notifications. To remove a recipient, click the delete icon next to their address.

​
Telegram

Telegram notifications are sent via a Telegram bot. The bot is linked to a specific chat (personal chat, group, or channel) using a connection token.

​
Connecting Telegram

  1. Go to Integrations → Telegram section.
  2. Click Generate Connection Token. A token is displayed — it is valid for 15 minutes.
  3. Open your Telegram chat (where you want to receive notifications) and send: 
    /connect <token>
    to the Alius bot.
  4. The bot confirms the connection and the status changes to Connected.

​
Sending a Test Message

Click Send test notification to post a test message to the connected chat. This confirms the bot token is valid and the chat ID is correctly linked.

​
Disconnecting Telegram

Click Disconnect to unlink the chat. This stops all Telegram notifications. Reconnect at any time by generating a new token.

​
Rate Limiting

Telegram enforces message rate limits. If Alius receives a rate-limit response (HTTP 429), it automatically retries the message up to 3 times with backoff. If all retries fail, the notification is logged as Failed in Notification History.

​
Discord

Discord notifications are sent via an incoming webhook — no OAuth or bot setup is required. You create the webhook inside Discord and paste the URL into Alius.

​
Creating a Discord Webhook

  1. In Discord, open the channel where you want to receive notifications.
  2. Go to Channel Settings → Integrations → Webhooks.
  3. Click New Webhook, give it a name, and click Copy Webhook URL.

​
Connecting Discord

  1. Go to Integrations → Discord section.
  2. Paste the webhook URL into the Webhook URL field.
  3. Click Connect. Alius validates the URL format and saves it.
  4. The status changes to Connected.
The webhook URL must start with https://discord.com/api/webhooks/ or https://discordapp.com/api/webhooks/. Any other URL is rejected.

​
Sending a Test Message

Click Send test message to post a test notification to the connected channel. This confirms the webhook is valid and the channel is accessible.

​
Enabling and Pausing

Once connected, use the Enable notifications toggle to pause and resume Discord messages without disconnecting. Toggling it off stops all Discord notifications while preserving the webhook URL.

​
Disconnecting Discord

Click Disconnect to remove the integration. This clears the webhook URL and stops all Discord notifications. Your triggers are preserved and will resume sending once Discord is reconnected.

​
Message Format

Discord messages are posted as embeds by Alius, using Shopify green (#008060) as the accent color. The username shown in the channel is “Alius”. If the trigger’s content includes an admin link, the embed title links directly to the relevant resource in Shopify Admin.

​
Rate Limiting

Discord enforces webhook rate limits. If Alius receives an HTTP 429 response, it reads the retry_after value from Discord’s response and waits before retrying — up to 3 times. If all retries fail, the notification is logged as Failed in Notification History.