From 7e2662545489a6442a6b6f73d7873d772133e0fe Mon Sep 17 00:00:00 2001
From: Rebecca Wheeler <rebecca.wheeler@wisc.edu>
Date: Wed, 4 Jan 2023 10:39:36 -0600
Subject: [PATCH] email alerting best practices doc

---
 docs/best-practices/email-alerting.md | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 docs/best-practices/email-alerting.md

diff --git a/docs/best-practices/email-alerting.md b/docs/best-practices/email-alerting.md
new file mode 100644
index 0000000..bedf129
--- /dev/null
+++ b/docs/best-practices/email-alerting.md
@@ -0,0 +1,11 @@
+# Email Alerting
+
+It's important to know when your integration fails and why.  If no email is entered, no one will be alerted that an integration fails and it may be very inconvenient if things start falling apart. 
+
+## Tutorial
+
+Informatica has created a [knowledgebase article located here](https://knowledge.informatica.com/s/article/496185?language=en_US) to help you through the process in adding your email into your tasks and task flows.
+
+## Confirmation
+
+Success alerts can also be configured in this way, letting you know your integration ran without issue.
-- 
GitLab