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

# Workflow notifications

Users can get notified (on a [notification channel](/administration/notifications.md#channels)) whenever a workflow has finished its execution. This way you can inform customers, departments, or project owners when their configured workflow has finished successfully or with a failed status.\
\
These are the steps to configure a Workflow notification:

{% hint style="info" %}
This tutorial teaches you how to create notifications for yourself, but you can also [create them for other users](/administration/notifications.md#creating-notifications-for-other-users) if you have admin rights.
{% endhint %}

\
\
1\. [Create a Workflow](/data-pipelines/workflows.md#creating-a-workflow) or choose an existing one.

2\. Click on your username at the top right corner of the screen, then select **My Notifications**.

3\. Fill in the details (**Name**, **Title** and **Description**) and make sure the **Trigger** is set to *Workflow Ended*:

![Example of a notification for a Successful Workflow](/files/dSWCkj4kBGKHySMCeRp1)

4\. Select one or more Workflows.

5\. You can apply a trigger for a successfully finished workflow, a failed workflow, or both:

![Workflow triggers](/files/RlehMpOHyAw4KLfJUPf4)

###

6\. In the **Filenames** section, it is possible to use [regular expressions](https://en.wikipedia.org/wiki/Regular_expression) to select which files to export.

7\. You can opt for sending a file along with the notification only if the file was created/modified after the start time of that workflow. To achieve this, tick the **Enabled** box next to **Since workflow start time**.

8\. It is possible to compress the files by ticking the **Enabled** box next to **Compress** **Attachments**.

9\. Finally, click the **Create** button.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://olddocs.exivity.io/administration/notifications/workflow-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.