Skip to main content
Node type: desktop_notification · Version: 1 · Category: System Show a native notification. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

​
When to use this node

  • Surface a local success, warning, or review reminder to the operator.
  • Finish a monitoring flow with a concise result that does not need an external connection.

​
Example: Notify after a report is parsed

Include a mapped row count in a local completion message.
Example settings
This shows the important settings, not a complete exported node.
  1. Give the notification a short, recognizable title.
  2. Map only the result the operator needs into the message.
  3. Keep detailed evidence in execution history rather than in the toast.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • The host asks the operating system to deliver the notification and returns delivered plus the title.
  • Delivery is a local side effect and may be subject to operating-system notification settings.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • Focus Assist or disabled notifications can hide a successfully delivered notification.
  • Do not include secrets or full sensitive payloads in text visible on the desktop.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.