OpsionDocs
ConsoleWebsiteSign in

Slack Notifications

Connect Opsion to any Slack channel using a Slack Incoming Webhook. Once configured, any alert rule with Slack enabled will post a message to that channel the moment a transaction matches.

How it works

Slack Incoming Webhooks give you a unique URL. Opsion posts an HTTP request to that URL whenever an alert fires. No bot installation or OAuth is required — just a webhook URL.

The webhook URL is configured once at the organisation level. All alert rules in your organisation that have Slack enabled share the same webhook.

Create a Slack Incoming Webhook

  1. Go to api.slack.com/apps and click Create New App → From scratch. Give it a name (e.g. Opsion Alerts) and choose your workspace.
  2. In the left sidebar, click Incoming Webhooks and toggle the switch to Activate Incoming Webhooks.
  3. Click Add New Webhook to Workspace, select the channel you want alerts posted to, and click Allow.
  4. Copy the webhook URL — it looks like:
    text
    https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
✦

Use a dedicated channel

Create a dedicated #opsion-alerts channel to keep notifications separate from normal conversation. You can always set up additional rules pointing to other channels via separate webhook URLs.

Add the webhook to Opsion

  1. Open the Opsion console and go to Settings → Notifications.
  2. Paste your webhook URL into the Slack Webhook URL field.
  3. Click Save.

The webhook URL is stored securely in your organisation settings in the database.

Enable Slack on alert rules

Saving the webhook URL does not automatically enable Slack for every rule. For each rule where you want Slack notifications:

  1. Open Alerts → Rules and click the rule you want to configure.
  2. In the Notification channels section, toggle Slack on.
  3. Save the rule.
💡

Plan requirement

Slack notifications require the Team plan or above. The channel toggle is disabled and shows an upgrade prompt on the Free plan.

Message format

Slack messages follow this format:

text
*Large transfer detected on asset*
Tx 0x27b037ae | -1.5 ETH | ethereum
<https://etherscan.io/tx/0x27b037ae...|View on explorer>
<https://console.opsion.xyz/transactions?hash=0x27b037ae...|Open in Opsion>

The transaction link opens the relevant block explorer (Etherscan, Basescan, BscScan, etc.) directly. For chains without a known explorer the link is omitted.

Alert EventsLark