Adding New Alert Destinations

Intro

Whenever an Alert triggers, it sends a blob of related data (called the Alert Template) to its designated Alert Destinations. Destinations can use this blob of data to fire off emails, Slack messages, or custom web hooks. You can set up new Alert Destinations from the settings screen.

Only Admins can add new alert destinations. Destinations are available to all users once configured.

Add A New Alert Destination

There are a few types of destinations to choose from:

• Email

• Discord

• Twitter

• Twitter Private

• Telegram

The default destination for any alert is the email address for the user who created it. If you made an alert and need to be notified by email then you don’t need to setup a new Alert Destination. Instead, toggle the switch beside your email address on the alert setup screen.

To configure one, select it from Create a New Alert Destination dialogue and follow its prompts.

Discord

To set up a new Alert Destination for Discord:

1. Create a Webhook in Discord:

   • Go to your Discord server settings.

   • Click on the 'Integrations' tab.

   • Click the 'New Webhook' button and configure its settings like name and channel where alerts will be posted.

   • Copy the Webhook URL provided by Discord.

2. Configure in Inverse Finance App:

   • From the 'New Alert Destination' dialogue, choose 'Discord'.

   

   • Paste the copied Webhook URL into the field provided.

   • Optional: Test the alert destination to ensure it's working correctly.

   • Save your settings.

Once set, the application will send alerts to the designated Discord channel when they are triggered.

Twitter

To set up a new Alert Destination for Twitter:

1. Create a Twitter Developer Account:

   • If you don’t have a Twitter Developer account, apply for one at Twitter Developer Portal.
   • Create an App under your developer account to get the API Key, API Secret Key, Access Token, and Access Token Secret.

2. Configure in Inverse Finance App:

   • From the 'New Alert Destination' dialogue, choose 'Twitter'.

   • Fill in the API Key, API Secret Key, Access Token, and Access Token Secret into the respective fields.

   • Optional: Specify whether the alerts should be published as a tweet (public) or sent as a Direct Message. For private alerts, choose 'Twitter Private'.

   • Optional: Test the alert destination to ensure it's working correctly.

   • Save your settings.

Once set, the application will send alerts to the specified Twitter account when they are triggered, either as tweets or direct messages based on your preference.

Twitter Private

This destination type is exactly as the latter, at the difference that it sends the content of the template to the twitter user her/himself as a direct message.

This is particularly useful if you want to test twitter alert destination without spaming all your subscribers.

---