Source: https://cryptanio.com/wiki/crypto-transaction-notifications-slack/
Language: en

# How to get crypto transaction notifications in Slack

Connect Slack to Cryptanio\, route Monitoring events to the right channel\, choose confirmed receipts\, and check message delivery\.

Updated: 2026-11-14

You can send cryptocurrency transaction notifications to a selected Slack channel through a connection in the Cryptanio dashboard\. First\, you authorize messages to be sent to Slack\, then choose which project events should go there\. Ordinary notifications do not require your own server or an API key\.

Consider a team monitoring incoming USDT transfers to a business address and wanting to see confirmed receipts in one channel\. [USDT](<https://cryptanio.com/wiki/what-is-usdt/>) and the [transfer network](<https://cryptanio.com/wiki/network-and-token/>) must be selected consistently\: the same ticker does not mean the same blockchain\.

## What you need {#what-you-need}

You need a Cryptanio account with owner or administrator permissions\, a project with an active Monitoring service\, and access to the relevant Slack workspace\. For a private channel\, the person connecting the app must already be a member\.

Installing apps may require approval from a Slack administrator\. This depends on workspace rules rather than transaction settings\. The requirements are explained in [Slack\'s app approval rules](<https://slack.com/help/articles/222386767-Manage-app-approval-for-your-workspace/>)\. Slack\'s external rules were checked on November 13\, 2026\.

## 1\. Connect the address to Monitoring {#1-connect-the-address-to-monitoring}

Open Monitoring and the relevant project\. In the address list\, click “Add addresses\,” choose the network\, and add the address you want to monitor\. For this scenario\, enable incoming transfers and select the required USDT asset\. Use the options available for the chosen network\.

Check that the address is active and the service is running\. The address book stores entries\; saving an address there does not start monitoring\. If the address is already in the book\, connect it to Monitoring for the selected project\.

Pausing monitoring and pausing message delivery are separate settings\. An active Slack channel cannot provide events for an address whose monitoring has stopped\.

## 2\. Connect the Slack channel {#2-connect-the-slack-channel}

Open “Settings” → “Notifications” and the Slack tab\. Click “Connect Slack\.” The dashboard redirects you to Slack\: select the workspace and channel\, review the requested permissions\, and authorize the connection\.

After returning to Cryptanio\, check the workspace and channel names in the connection row\. This helps catch an incorrect selection before configuring the project\. If necessary\, rename the connection so that colleagues can understand its purpose\.

If a message says Slack authorization is unavailable instead of showing the button\, the connection is not currently configured for that service environment\. Do not substitute addresses from unrelated guides\; ask Cryptanio support about availability\.

## 3\. Test message delivery {#3-test-message-delivery}

Click “Test” in the connection row\. The dashboard reports that a test notification has been queued\; wait for the actual message in the selected Slack channel\. After successful delivery\, the connection shows its latest delivery\.

The test checks the message delivery path\. It does not create a USDT transfer\, prove that address monitoring works\, or mean that a particular order has been paid\. Address events require the next step\.

## 4\. Enable the connection for the project {#4-enable-the-connection-for-the-project}

Open “Notifications” for the relevant project\. At the top is “Use account notification settings\.” When inheritance is enabled\, the project uses account channels and its own routes cannot be edited\.

Turn inheritance off to use the project’s own routes\. Find the connection in the Slack card\. If its route is absent\, click the plus button “Use … for this project”\; otherwise\, go straight to event selection\. If no custom settings have been saved yet\, switching copies the shared routes\. A new connection is also added to shared account notifications\. Changing one project does not stop delivery to this channel for other projects inheriting the shared settings\; check those separately if needed\.

The account connection and project route have different purposes\: the first determines where messages are sent\, while the second determines which project\'s events go there\. For another channel\, use “Connect another Slack” in account settings\.

## 5\. Choose events {#5-choose-events}

“Confirmed payments” suits this scenario\. To also see when a previously detected receipt is reversed by a chain rollback\, select “Confirmed and rolled back\.” The meaning of confirmations is explained in the [reference article](<https://cryptanio.com/wiki/transaction-confirmations/>)\.

“All project events” may generate more messages\. Use “Choose event types” to select a specific set\. For example\, outgoing transfers have their own “Outgoing transfer confirmed” event\; the confirmed\-payments policy does not include it automatically\. The address must also be configured to monitor the required direction of transfers\.

Route and event\-selection changes are saved when you perform the action\. Check the result and the “Active” status\. Account security and service\-billing notifications on the “Notification types” tab do not replace project event settings\.

## How to test the complete scenario {#how-to-test-the-complete-scenario}

After setup\, wait for a new matching transaction\. Find it in “Events\,” then check the corresponding entry in “Deliveries” and the Slack message\. Do not rely on an old transaction as a guaranteed way to resend a notification\: enabling a route does not replay history by itself\.

If the event exists but no message arrives\, check the selected policy\, the route pause\, and whether the connection is paused at account level\. Look at attempts and the error in “Deliveries\.” If Slack access has been revoked or the channel is unavailable\, use “Reconnect” and test again\.

## Limitations and security {#limitations-and-security}

The connection uses [Slack incoming webhooks](<https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/>)\, which are tied to the selected channel\. Do not publish the secret webhook URL\; in this scenario\, Cryptanio handles the authorization exchange\. For a different channel\, create a separate connection and assign the appropriate route\.

The Slack channel\'s membership determines who can see payment messages\. Choose a business channel with suitable access\. A transfer notification is for the team\; automatic fulfillment of a paid order is configured separately through [webhook and invoice\-status verification](<https://cryptanio.com/wiki/confirm-orders-with-crypto-payment-webhooks/>)\.

Tags: [Monitoring](https://cryptanio.com/wiki/tag/monitoring/), [USDT](https://cryptanio.com/wiki/tag/usdt/), [Slack](https://cryptanio.com/wiki/tag/slack/)

## Related articles

- [What is USDT](https://cryptanio.com/wiki/what-is-usdt/)
- [How networks and tokens differ](https://cryptanio.com/wiki/network-and-token/)
- [What transaction confirmations mean](https://cryptanio.com/wiki/transaction-confirmations/)