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

# Chevre Notifications: Configure Alerts Across Every Channel

> Configure in-app, email, Slack, and webhook notifications in Chevre to stay informed about the workspace activity that matters most.

Chevre sends notifications to keep you informed about activity in your workspace — via email, in-app alerts, Slack, or webhooks. You can configure notifications at the personal level to control exactly what you hear about and how often, or — if you're a workspace admin — define workspace-wide defaults that apply to everyone on your team. Notifications are opt-in by channel, so you're always in control of the signal-to-noise ratio.

## Notification channels

Chevre delivers notifications across four channels, each suited to different working styles and use cases.

| Channel     | Delivery method                    | Supported events                                 |
| ----------- | ---------------------------------- | ------------------------------------------------ |
| **In-App**  | Bell icon in the Chevre dashboard  | All events                                       |
| **Email**   | Sent to your account email address | All events; configurable frequency               |
| **Slack**   | Direct message or channel post     | Workflow events, billing alerts, member activity |
| **Webhook** | HTTP POST to a custom endpoint     | All events; ideal for custom tooling or logging  |

## Configuring your personal notification preferences

Your personal notification settings control what you receive and on which channels. These settings only affect your own account and don't change what other team members see.

<Steps>
  <Step title="Open Notification Settings">
    Click your avatar in the bottom-left corner of the sidebar, then select **Settings**. In the settings menu, click **Notifications**.
  </Step>

  <Step title="Choose your channels">
    At the top of the Notifications page, you'll see toggles for each delivery channel — **In-App**, **Email**, **Slack**, and **Webhook**. Enable the channels you want to receive notifications on. Disabling a channel turns off all notifications for that channel instantly.
  </Step>

  <Step title="Configure per-event preferences">
    Below the channel toggles, you'll find a list of all notification events. For each event, use the row controls to choose which channels should deliver it. For example, you might want **Workflow Run Failed** delivered via both Email and Slack, but **New Member Invited** only as an In-App alert.
  </Step>

  <Step title="Set your email frequency">
    If you have Email notifications enabled, choose how often you want them delivered:

    * **Immediate** — each event triggers an individual email as it happens
    * **Hourly digest** — events are batched and sent in a single email once per hour
    * **Daily digest** — events are batched and sent in one email at a time you choose

    Select your preferred frequency from the **Email Frequency** dropdown.
  </Step>

  <Step title="Save your preferences">
    Click **Save Preferences**. Your settings take effect immediately for all new events going forward.
  </Step>
</Steps>

## Notification events

<Accordion title="Workflow run completed">
  Fires when a workflow finishes executing all its steps without errors. Includes the workflow name, run duration, and a link to the run detail page in Chevre.
</Accordion>

<Accordion title="Workflow run failed">
  Fires when a workflow encounters an error and cannot complete. The notification includes the step that failed, the error message, and a direct link to the failed run so you can investigate and retry.
</Accordion>

<Accordion title="New member invited">
  Fires when someone is invited to join your workspace. Workspace admins receive this notification automatically; other members receive it if they've opted in.
</Accordion>

<Accordion title="Member role changed">
  Fires when a member's role is updated — for example, when someone is promoted from Member to Admin. The notification identifies the affected member and their new role.
</Accordion>

<Accordion title="Automation triggered">
  Fires each time an automation executes, including the automation name, the event or schedule that triggered it, and whether all actions completed successfully.
</Accordion>

<Accordion title="Billing alert">
  Fires when your workspace approaches or reaches a usage limit — such as the monthly automation run cap — or when a payment fails. Billing alerts are always sent via Email to workspace admins and cannot be disabled.
</Accordion>

## Configuring workspace-wide notifications

<Info>
  Workspace-wide notification settings require the **Admin** role. Members cannot change workspace defaults, only their own personal preferences.
</Info>

As an admin, you can set default notification preferences that apply to all workspace members who haven't customized their own settings. To configure workspace defaults:

1. Click your workspace name in the top-left corner and go to **Settings → Notifications**.
2. Adjust the default channel toggles and per-event preferences.
3. Click **Save Workspace Defaults**.

Members who have already saved their own preferences will not be affected by changes to workspace defaults. To reset a member's preferences to the workspace default, go to **Settings → Members**, click the member's name, and select **Reset notification preferences**.

## Registering a webhook for notifications

Webhook notifications let you receive Chevre events as HTTP POST payloads at any endpoint you control — your own server, a log aggregator, or a custom alerting pipeline. Register and manage notification webhooks using the Chevre REST API.

**Register a webhook to receive notification events**

```bash theme={null}
curl -X POST https://api.chevre.io/v1/webhooks \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-server.example.com/chevre-notifications",
    "events": ["workflow.run.failed", "billing.alert", "automation.triggered"]
  }'
```

Save the `signing_secret` returned in the response. Your server should validate the `X-Chevre-Signature` header on every incoming request to confirm the payload came from Chevre.

**List your registered webhooks**

```bash theme={null}
curl https://api.chevre.io/v1/webhooks \
  -H "Authorization: Bearer YOUR_API_TOKEN"
```

**Remove a webhook**

```bash theme={null}
curl -X DELETE https://api.chevre.io/v1/webhooks/wh_01hx3k9z \
  -H "Authorization: Bearer YOUR_API_TOKEN"
```

## Muting notifications for specific projects

If a project is particularly active and generating more notifications than you need, you can mute it without changing your global preferences.

1. Open the project in Chevre.
2. Click the **···** menu in the project header.
3. Select **Mute Notifications**.

While a project is muted, you won't receive any notifications from events in that project on any channel. A muted bell icon appears in the project header as a reminder. To unmute, follow the same steps and select **Unmute Notifications**.

<Tip>
  You can route webhook notifications directly to Zapier or your own custom service to build powerful alert pipelines. For example, post Chevre billing alerts to a dedicated ops Slack channel via a Zapier Zap, or log every workflow failure to your team's incident tracker automatically. To get started, connect the Webhook integration in **Settings → Integrations** and subscribe to the events you need — see [Connecting Integrations](/guides/integrations) for step-by-step instructions.
</Tip>