> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/administration/alerts-and-notifications.md).

# Alerts and Notifications

Learn about alerting and notifications in Couchdrop

## Overview

Couchdrop can send alerts and notifications when file transfer, account, or system events occur.

There are three separate ways to configure notifications in Couchdrop:

* **Global Alerting** for account-wide events
* **Folder Notifications** for activity within a specific folder
* **Automation Notifications** for automation success or failure

Each mechanism is configured independently, so you can use one or combine them depending on the events you need to monitor.

### File Activity Alerts

File Activity Alerts notify you when file or storage events occur.

Supported events include:

* Upload
* Download
* Failure
* Storage failure
* Deletion
* Rename

Depending on the event, alerts can be configured globally or for a specific folder.

Global alerts are configured under **Admin Mode > Alerting**.

Folder-specific alerts are configured from **File Browser > Manage Folder > Notifications**.

For more information, see [**File Activity Alerts**](/administration/alerts-and-notifications/file-activity-alerts.md).

### Missing Upload Alerts

Missing Upload Alerts notify you when Couchdrop detects that an expected upload has not occurred.

Couchdrop compares the previous completed hour with the same hour over the previous seven days. If there were uploads during that hour on each of the previous seven days but none during the most recent completed hour, Couchdrop sends a notification.

Missing Upload Alerts can apply to:

* Users
* Mailboxes
* Webhooks
* AS2 Stations

For more information, see [**Missing Upload Alerts**](/administration/alerts-and-notifications/missing-upload-detection.md).

### User Alerts

User Alerts notify you about user-related events.

Supported alerts include:

* **Login** — send a webhook notification when a user logs in
* **User expiry** — send an email notification when a user account expires

These alerts are configured under **Admin Mode > Alerting**.

For more information, see [**User Alerts**](/administration/alerts-and-notifications/user-alerts.md).

### Workflow Notifications

Workflow Notifications report the outcome of an Automation.

You can send notifications to multiple recipients by separating email addresses with commas.

For more information, see [**Workflow Notifications**](/automations/notifications.md).

### Notification delivery

Couchdrop supports two main notification channels:

* **Email**
* **Webhook**

The available channel depends on the alert type.

{% hint style="info" %}
Webhook endpoints must return an HTTP `200` response. If a webhook does not return `200`, Couchdrop retries the request up to 15 times using exponential backoff.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/administration/alerts-and-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.