> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incredibuild.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> Get notified by email or webhook when builds start, end, or fail.

Create alert rules under **Settings → Alerts** to notify your team about build activity across
your grids.

<Note>Managing alerts requires **Admin** permission.</Note>

## Create an alert

<Steps>
  <Step title="Open Alerts">
    In **Settings → Alerts**, click **Create alert**.
  </Step>

  <Step title="Name it">
    Enter an **Alert name** and an optional **Description**.
  </Step>

  <Step title="Choose a trigger">
    Pick when the alert runs: **Build starts** or **Build ends**.
  </Step>

  <Step title="Add conditions (optional)">
    Narrow the alert with up to 20 conditions, combined with **All** or **Any** logic. Leave this
    empty to fire on every build that matches the trigger.
  </Step>

  <Step title="Choose how to be notified">
    Under **Notify via**, enable **Email**, **Webhook**, or both.
  </Step>

  <Step title="Save">
    Click **Create alert**.
  </Step>
</Steps>

## Conditions

Available condition targets depend on the trigger - result, duration, and core-count data only
exist once a build has finished, so they're unavailable on **Build starts**.

* **Build result** - is / is not **Succeeded**, **Failed**, or **Cancelled**.
* **Build name** - is exactly / contains / does not contain / starts with / ends with.
* **Grid** - is / is not one of up to 50 grids.
* **Duration** - longer than / shorter than / between (seconds, minutes, or hours).
* **Peak helper cores used** / **Average helper cores used** - more than / fewer than / at least /
  at most / between.

<Note>
  Switching the trigger on an existing alert automatically removes any conditions that no longer
  apply, and tells you which ones were dropped.
</Note>

## Notify via

* **Email** - enter up to 25 recipient email addresses directly on the alert. Each notification
  includes a one-click unsubscribe link, scoped to that alert or to all alerts for your tenant.
* **Webhook** - send the alert to a destination configured under
  [Settings → Webhooks](/console/notifications/webhooks). If the alert doesn't have a webhook to
  choose from yet, create one first.

## Manage alerts

From the alerts list you can toggle an alert **Active**/inactive, edit, or delete it. An alert
whose webhook destination was deleted shows a **broken destination** warning - it still fires by
email (if configured) until you assign a new webhook.