nodes / extension
Browser Notification
Show a system notification through the OS notification center, visible even when no tab is focused.
Show a system notification through your computer’s notification center, visible even when no browser tab is in view.
What it does
Section titled “What it does”Browser Notification shows a native notification with a Title, a Message, an icon and a Priority, and can add up to two buttons. The notification comes from the operating system, so it reaches you whatever you are looking at, and stays in the notification center like any other alert.
- With Icon URL empty, the AWFlow icon is used.
- Buttons: only the first two are shown. Firefox shows the notification without buttons.
- The node does not wait for you: the workflow continues as soon as the notification is shown. Clicking the notification or a button does not send anything back to the workflow yet; buttons are for display only.
When to use it
Section titled “When to use it”- Tell yourself that a scheduled or background workflow has finished, while you work in another app.
- Alert on something a workflow found: a price drop, a new message, a failed check.
- If you need a notification you can replace later, kept on screen until dismissed, or silent, use Show Notification. If the workflow must wait for your answer, use In-Page Form or Wait For Approval.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Title (required) | Text | |
| Message (required) | Long text | |
| Icon URL | Text | |
| Priority | Choice | Options: Low, Normal, High. Default: Normal |
| Buttons | List of entries | Up to two action buttons, per the Chrome notifications API limit. Chrome only: Firefox shows the notification without buttons. |
| Buttons (each entry) › Button Title (required) | Text |
Title and Message accept expressions, for example Message = {{ $input.count }} new items found.
Outputs
Section titled “Outputs”-
Output
Each output item has these fields:
| Field | Type | What it holds |
|---|---|---|
| notificationId | Text | |
| shown | Always true |
{ "notificationId": "…", "shown": true}notificationId: the id of the notification that was created.shown:trueonce the notification has been created.
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
No credential and no extra permission is needed. Notifications must be allowed for your browser in your operating system’s settings.
Example workflow
Section titled “Example workflow”- A Schedule trigger runs every day at 8:00.
- RSS Feed Read and Limit pick the 5 newest posts of a feed.
- Aggregate combines them into one item.
- Browser Notification with Title =
Your morning digestand Message =5 new posts are waiting.
Common issues
Section titled “Common issues”- Nothing appears. Notifications for your browser are turned off in the operating system’s settings, or a focus / do-not-disturb mode is on. Allow them and run the node again.
- “Notification title and message are required”. Title or Message is empty, often because an expression resolved to nothing. Check the previous node’s output.
- The custom icon does not show. Icon URL must point to an image the browser can load. Leave it empty to use the default icon.
- Clicking a button does nothing. Buttons are display-only for now. To let the user choose and resume the run, use In-Page Form.
Related nodes
Section titled “Related nodes”- Show Notification: a system notification you can replace, keep on screen or make silent.
- In-Page Form: ask the user and wait for the answer.
- Display Markdown: show a longer result on the page itself.