# Microsoft Teams alerts

{% hint style="info" %}
Paradime integrates natively with Elementary CLI to enable you to generate report and/or send alerts using the Bolt scheduler out of the box. **No additional installation required.**
{% endhint %}

## Configure Microsoft Teams  <a href="#execute-the-cli" id="execute-the-cli"></a>

### 1. Create a new team and/or channel

First, create a new Team or add a new channel to an existing team to receive the alerts. Ensure the channel's type is set to *Standard.*

### 2. Create Teams Webhook

To setup an incoming webhook in our channel:

1. Go to a channel in your Team and choose `Manage channel.`&#x20;
2. Choose `Edit` connectors.
3. Search for `Incoming webhook` and choose `Add`.&#x20;
4. Choose `Add` again and add name your webhook `Paradime` (or any other name you prefer).&#x20;
5. &#x20;*(Optional)*  You can add the Paradime logo for the Bot. **Download this** [**here**](https://20146536.fs1.hubspotusercontent-na1.net/hubfs/20146536/logo-no-text-light-transparent-3x.png)**.**&#x20;

When done, click on `Create` the webhook. Now copy the URL of the webhook, you will need this later when configuring the alerts.

{% @arcade/embed flowId="8mLJfUvsATtpy1XWakN4" url="<https://app.arcade.software/share/8mLJfUvsATtpy1XWakN4>" %}

## Configure a Bolt schedule with Elementary CLI <a href="#execute-the-cli" id="execute-the-cli"></a>

{% hint style="info" %}
You can use a runtime environment variable to pass your Teams webhook to the `edr` command at runtime. Check our docs here.
{% endhint %}

### Alert on tests and models <a href="#alert-on-source-freshness-failures" id="alert-on-source-freshness-failures"></a>

Configure a Bolt schedule with the `edr monitor` CLI command at the end. Ideally this should be the command after your dbt runs and tests:

```bash
dbt run
dbt test
edr monitor --teams-webhook <your_teams_webhook>
```

### Alert on source freshness failures <a href="#alert-on-source-freshness-failures" id="alert-on-source-freshness-failures"></a>

To alert on source freshness, you will need to run `edr run-operation upload-source-freshness` right after each execution of `dbt source freshness`. This operation will upload the results to a table, and the execution of `edr monitor` will send the actual alert.

```bash
dbt source freshness
edr run-operation upload-source-freshness --project-dir .
edr monitor --teams-webhook <your_teams_webhook>
```

{% hint style="info" %}

#### Note:

* `dbt source freshness` and `upload-source-freshness` needs to run from the same machine.
* `upload-source-freshness` requires passing `--project-dir` argument.
  {% endhint %}