# Alerts contact points

To manage contact points, click the Alerts tab, and select **Contact points** sub-menu.

The **Contact points** interface appears.

Contact points interface

1. **Selectors** are for bulk actions, such as **Delete**.  
2. **List** of all alerts in the system.

Includes:

1. **[Selectors](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#selectors)** for bulk actions
2. **[Contact point name](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#contact-point-name)** that you define when you [Add a contact point](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#add)
3. **[Type](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#contact-point-type)** of contact point you choose when you [Add a contact point](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#add)

The options are:

-  (Email)
      -  (PagerDuty)
      -  (Slack)
      -  (Microsoft Teams)
      -  (Webhook)
      -  (Google Chat)
      -  (OpsGenie)

3. For specific contact points, hover over the table row, and:
4. Click  (Edit) to change the definition of an existing contact point.
5. Click  (Delete) to remove the contact point from the system; see [Delete contact point](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#delete).

## Add a contact point

To add a new contact point, follow these steps:

1. Click  (Add New Contact Point).
2. The **Create Contact points** interface appears.

3. Start by specifying the **Contact point name**.
4. [Optional] Specify **Choose mute timing** from the drop-down; see [Suppress Schedule for Alerts](https://docs.kloudfuse.com/platform/3.5.0/alerts-suppress-schedule/) for details.
5. **Choose contact point type**.

By default, the contact point is an **[Email](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#email)**. The other options are **[PagerDuty](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#pagerduty)**, **[Slack](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#slack)**, **[Microsoft Teams](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#ms-teams)**, **[Webhook](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#webhook)**, **[Google Chat](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#google-chat)**, and **[OpsGenie](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#opsgenie)**.

6. Depending on the contact point type, specify the settings.

To format subject, body of message, and similar fields, you can use the [GO Templating Language](https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/using-go-templating-language/).

### Contact Point Types

- Email
- PagerDuty
- Slack
- Microsoft Teams
- Webhook
- Google Chat
- OpsGenie

**Required field:**

Addresses

Use one or more email addresses.

For multiple addresses, separate using a comma (,), a semicolon (;), or end of line (\n). Avoid spaces.

**Optional fields:**

- Single email
  - Select to have all recipients on the **To** line.
- Message
  - Plain text, or format with [GO Templating Language](https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/using-go-templating-language/).
  - A custom message in the **Alert** configuration replaces this default.
- Subject
  - Plain text, or format with [GO Templating Language](https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/using-go-templating-language/).

**Required field:**

Integration Key

This is the PagerDuty integration key for your account.

**Optional fields:**

- Severity
  - Severity of the event: **critical** (default), **error**, **warning**, or **info**
  - Can use templates; see [GO Templating Language](https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/using-go-templating-language/).
- Class
  - The class or type of event, such as "cpu load", "ping failure", and so on
- Component
  - Component of the source responsible for the event, such as "mysql", "eth0", and so on
- Group
  - Logical grouping of service component, such as "app-stack"
- Summary
  - Summarize content. Can use templates in [GO Templating Language](https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/using-go-templating-language/).
- Source
  - Location of the affected system, such as hostname or FQDN
- Client
  - Monitoring client that triggers this event
- Client URL
  - URL of the monitoring client
- Details
  - A set of key/value pairs that provide further details about the incident.

**Required fields:**

To authenticate, use either a combination of [Recipient](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#recipient) and [Token](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#token), or the [Webhook URL](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#webhook-url).

- Recipient
  - Channel, private group, or IM channel (encoded ID or name)
- Token
  - Slack API token that starts with `xoxb`
- Webhook URL
  - Incoming webhook URL for sending messages

**Optional fields:**

- Username
- Icon emoji
- Icon URL
- Mention Users
- Mention Groups
- Mention Channel
- Endpoint URL
- Title
- Text Body

**Required field:**

URL

Teams incoming webhook URL

**Optional fields:**

- Title
- Second Title
- Message

**Required field:**

URL

The URL of the alert

**Optional fields:**

- HTTP Method
- HTTP Basic Authentication - Username
- HTTP Basic Authentication - Password
- Authorization Header - Scheme
- Authorization Header - Credentials
- Max Alerts
- Title
- Message

**Required field:**

URL

Google Chat incoming webhook URL

**Optional fields:**

- Title
- Message

**Required fields:**

API Key

OpsGenie API key

Alert API URL

The URL of the alerts, such as `https://api.opsgenie.com/v2/alerts`

**Optional fields:**

- Message
- Description
- Auto close incidents
- Override priority
- Send notification tags as
- Responders

6. Click  (Test) to validate the configuration of the contact point.
7. Finalize the configuration by clicking  (Save contact point).

## Add another configuration to the contact point

Organizations often have several communication methods, so you can establish multiple contact point types, or different alerting options depending on the roles of users, and teams or groups. You can therefore create several different contact point implementations, configure them differently, and have Kloudfuse group and manage them as a set, under the same contact point name.

1. Click  (Add another) to begin configuring another contact point, as described in the section [Add a contact point](https://docs.kloudfuse.com/platform/3.5.0/alerts-contact-points/#add).
2. Click  (Test) to ensure that the contact point works.
3. Click  (Save contact point).
4. [Optional] When working with multiple contact point definitions at the same time, a  (Delete) option appears for each contact point definition.
5. The new contact point appears in the list, with all specified types.

## Delete contact point

When you click **Delete**, you must confirm your action in the Delete Contact Point confirmation dialog by clicking