> 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/automations/notifications.md). # Notifications Learn about notifications as part of automations ## Overview Notifications let you send email alerts when a workflow succeeds or fails. They are useful when someone needs visibility into an automated process without reviewing the workflow execution logs. For example, you can notify an operations team when a transfer fails or confirm to a recipient that a scheduled process completed successfully. Notifications are always the final node in a workflow and report the outcome of the full workflow. ## Adding a notification In the Automation Builder, click the **+** icon, then select **Notifications**. Configure the notification using the following settings:

Setting	Description
Send email on success	Sends the notification when the preceding workflow action succeeds.
Send email on failure	Sends the notification when the preceding workflow action fails.
Recipient Email Address	The email address that will receive the notification. Enter multiple addresses as a comma-separated list.

You can enable both **Send email on success** and **Send email on failure** if the recipient should be notified regardless of the outcome. {% hint style="info" %} ## Branch-level notifications Standard notifications report the final result of the full workflow. They cannot notify recipients when a specific branch runs. To send an alert from a particular branch, add a [Custom Notification action](/automations/actions/notification-actions.md) to that branch. The notification is sent when the workflow reaches the action, giving you control over which condition triggers the alert. This is particularly useful with [error handling](/automations/error-handling.md). Add a Custom Notification action to an error branch to notify the appropriate recipients when that branch runs, rather than waiting for a general notification at the end of the workflow. {% endhint %} ### Recipient email addresses Enter the email address that should receive the notification in **Recipient Email Address**. To notify multiple recipients, separate each email address with a comma. For example: `operations@example.com, finance@example.com` ## Email template Couchdrop uses a pre-filled email template for workflow notifications. The exact content varies depending on the event, but notifications follow a structure similar to: **Subject:** `[Company name] - [Event] notification` > Hi there, > > Just wanted to let you know that your file `[full file path]` pulled by `[username]` has been `[event]` from `[directory]`. > > If you require support or assistance with this please email us on and someone will be in contact shortly. > > Thank you, > > Team @ Couchdrop The company name shown in the subject is taken from the company name configured in Couchdrop Admin settings. ## When to use notifications

Requirement	Use
Alert when a workflow fails	Notification with Send email on failure enabled
Alert when a workflow completes successfully	Notification with Send email on success enabled
Notify several stakeholders about the final workflow result	Notification with multiple addresses entered in Recipient Email Address
Send an alert when a specific workflow branch runs	Custom Notification action within that branch
Alert recipients when an error handling branch runs	Custom Notification action within the error branch

For more detailed information about an individual workflow run, use the **Automation execution logs**, which provide the full execution details and error information. --- # 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/automations/notifications.md?ask=&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.