Node: Notification

What does the Notification node do?

The Notification node sends a message to one or more people.

Use the Notification node when someone needs to know something. If they need to do something, use a Task node instead — a notification is not tracked and cannot be completed.

When should I use the Notification node?

• Work anniversary. The manager is notified of a milestone.
• Onboarding welcome. The new joiner gets a welcome message with practical details ahead of their first day.
• Repeated short-term absence. HR is notified when an employee reaches a set number of separate short absences within a period.

What settings does the Notification node have?

• Recipients: Who receives the notification. You can send it to a named person, to a role relative to the employee the run is for (most commonly their manager), or to the employee themselves. A notification can go to more than one recipient.
• Subject and message: The content. You can include information from the employee’s record, such as their name, title, or manager, so the message reads specifically rather than generically.
• Channel: How the notification is delivered — email, Slack, or Teams message.

What happens when a Notification node runs?

The message is composed using the employee’s record as it is at that moment, and sent to each recipient. The automation then continues immediately to the next node — a notification never waits for anything, because there is nothing to wait for.

Note: The run history records that the notification was sent, and when. It records the sending, not the delivery: whether the message arrived, and whether anyone read it, is outside Simployer One’s control.

What are common mistakes and limitations with the Notification node?

• Notifications are not tracked. Nobody has to acknowledge a notification, and nothing records whether it was acted on. If the step matters, it should be a Task node instead.
• Message text is seen widely. Recipients often include managers and employees. Be particularly careful in automations triggered by compensation or sensitive-data changes — the existence of a notification can itself reveal that something changed, even if the message does not say what.
• Role-based recipients follow the record. “The employee’s manager” is resolved when the run starts. If the manager field is empty, there is no recipient.
• Editing the automation does not recall messages already sent.