📣 Notification Node – User Guide

Use the Notification node to alert people (or whole groups) from inside your workflow. It supports two flavours:

Type	Appears Where	Lifetime	Typical Use-case
Toast	Corner pop-up	5–10 sec	Quick “job finished” banner – no history
Notification	Bell menu	Permanent until read	Anything the recipient might need to revisit

---

1. When to use each option

Ask yourself …	Choose
Does the user need to find this later?	Notification
Do I just want an FYI banner?	Toast
Should I track “unread” counts?	Notification
Speed and noise over permanence?	Toast

---

2. Fields & what they do

UI Field	Visible When	Meaning
Notification Type	Always	Select Toast or Notification. Drives which other fields appear.
Header	Toast	Big bold line on the toast banner.
Subject	Notification	Title shown in the bell drop-down.
Body	Always	Main message text. Markdown is allowed.
Toast Type	Toast	Visual colour: Success (green) or Error (red).
Recipients (Groups)	Always	Pick one or more security groups. All members receive the message.
Recipients (Users)	Always	Pick individual users.

Tip: You can mix groups and users. Duplicates are filtered automatically.

---

3. Step-by-step: sending a toast

1. Drag the Notification node onto your workflow canvas.

2. In Notification Type, choose Toast.

3. Fill in:

   • Header – e.g. “Build Complete”.
   • Body – e.g. “The nightly build finished successfully.”
   • Toast Type – Success or Error.

4. Select recipients:

   • Recipients (Groups) – “Developers”.
   • Or Recipients (Users) – “Alice Smith”.

5. Save the workflow and run it.

6. Recipients see a green pop-up for ~8 seconds. No bell entry is created.

---

4. Step-by-step: sending a persistent notification

1. Notification Type → Notification.

2. Complete:

   • Subject – “Quarterly Report Available”.
   • Body – “The Q2 report is ready for review in SharePoint.”

3. Choose users/groups as above.

4. On execution, recipients get:

   • A bell badge with an unread count.
   • The message stays until they open it (status toggles to read).

---

5. Runtime behaviour

• Deduplication – If a user is selected directly and belongs to a selected group, they receive one message.
• Downstream data – The node stores the final recipient ID list in workflow data → . Subsequent nodes can reference it.
• Failure handling – If no recipients are chosen the workflow fails with “At least one recipient must be provided”.

---

6. Practical tips

• Alert hygiene – Reserve Error toasts for failures; over-using red banners leads to alert fatigue.
• Groups first – Prefer groups where possible; user lists drift over time.
• Testing – Create a “Sandbox” group with only you in it to test flows without spamming others.

---

7. Troubleshooting

Symptom	Likely cause & fix
Node fails with “Unsupported NotificationType”	Check Notification Type spelling; must be Toast or Notification.
Toast colour wrong	Ensure Toast Type is set to Success or Error.
No one receives anything	Verify at least one recipient field has values and the IDs are valid.

---

That’s it!

Add the Notification node to your next workflow to keep your users (or whole teams) instantly informed – whether it’s a fleeting heads-up or a message they can come back to later.