Push Notification

Send a notification to your phone through ntfy or Pushover, so you hear about a change even when you are away from the browser.

Can use a Push Notification connection — 

Optional: pick a saved connection in the Credential field when the service needs one.

Create a connection →

Try it

workflow · job-postings-watch.awf 2 steps

New Job Postings Watch: a workflow with 2 steps, starting with Watch the job list and ending with Send a push notification.

1. 1 Watch the job list(Element Change — open its doc page) Element Change
2. 2 Send a push notification(Push Notification — open its doc page) Push Notification

Open in AWFlow Copy .awf

What it does

Pick a Provider and the node sends one notification with your Message, an optional Title, a Priority and a Click URL that opens when you tap the notification.

• ntfy is free and open source, and needs no account: the node publishes to a topic, and every phone subscribed to that topic in the ntfy app gets the message. It uses https://ntfy.sh unless you set Server to your own ntfy server. Tags add emoji icons, for example warning or tada.
• Pushover is a paid app (one-time purchase) that delivers to your own devices. It needs an application token and your user key.

The node sends one notification each time it runs. To send one summary for many items, collect them first with Digest or Aggregate.

When to use it

• Get pinged on your phone when a price or a stock status changes on a page you watch.
• Know when a long workflow has finished, or failed.
• Send yourself a short daily summary built by earlier nodes.

For a desktop notification without an account, use Browser Notification. To post to a team channel, use Slack, Discord or Telegram.

Inputs and settings

For every choice

Setting	Type	What it does
Credential	Credential	Optional. ntfy public topics need none. For a protected ntfy server use a Bearer Token; for Pushover use a Basic Auth credential with the application token in Username and your user key in Password.

2 choices · pick provider to see its settings

ntfyPushover

Settings for ntfy

Setting	Type	What it does
Topic REQ(required)	Text	The ntfy topic to publish to (anyone who knows it can read it — pick something unguessable).
Message REQ(required)	Text	The notification body.
Title	Text	The notification title.
Priority	Choice	ntfy priority. Options: Min, Low, Default, High, Max.
Tags	List	ntfy tags — emoji shortcodes (e.g. warning, tada) show as icons.
Click URL	Text	Open this URL when the notification is tapped — e.g. the page it is about.
Server	Text	ntfy server (defaults to https://ntfy.sh; use your self-hosted URL for a private instance).

Showing settings for ntfy

Need an operation that isn't listed? — 

Call the Push Notification API yourself with the HTTP Request node, and pick the same connection in its Credential field.

Use HTTP Request →

• Topic works like a password on the public ntfy server: anyone who knows it can read your notifications. Pick something long and random, like my-alerts-7f3k9q.
• Priority changes how insistently the phone alerts. On Pushover, Lowest (no alert) delivers without a sound or vibration.
• Click URL should be a full address starting with https://. Use an expression such as {{ $input.url }} to open the page the alert is about.

Outputs

• Output

The output is the provider’s reply. ntfy returns the published message, including its id, time and topic. Pushover returns status: 1 and a request id. Most workflows end here, or continue without using these fields.

Dependencies and credentials

• Credential (connection): optional. See Create a connection.

• ntfy on ntfy.sh, public topic: leave Credential empty.
• ntfy server with access control: use a Bearer Token credential with an access token from that server.
• Pushover: create an application at pushover.net to get an application token, and copy your user key from your Pushover dashboard. Save them as a Basic Auth credential: the application token as Username, your user key as Password.

See Create a credential.

Example workflow

1. An Element Change trigger watches CSS Selectors .price on a product page, limited by URL Patterns to that page.
2. Push Notification, Provider ntfy, Topic my-alerts-7f3k9q, Title Price changed, Message Now {{ $input.matchedText }}, Priority High, Tags moneybag, Click URL {{ $input.url }}.
3. On your phone, subscribe to my-alerts-7f3k9q in the ntfy app.

Common issues

• The ntfy notification never arrives. The phone is subscribed to a different topic or server. Check the exact Topic spelling and that the app uses the same Server (https://ntfy.sh by default).
• “Pushover needs a Basic Auth credential with the application token in Username and your user key in Password.” No credential is selected, or it is not a Basic Auth credential with both fields filled.
• “Pushover Error: 400 …” followed by a message about the token or user key. The two values are swapped or mistyped. The application token goes in Username, the user key in Password.
• “ntfy Error: 403 Forbidden” or “401”. The ntfy server needs an access token. Add a Bearer Token credential.
• The run is blocked in the web app. Push Notification runs through the browser extension. Install it, or run the workflow from the extension. In the web app with the extension installed, only ntfy.sh and Pushover can be used, not your own ntfy server.

Recipes with this node

Get a phone alert when a careers page lists new jobs beginner · 6 min Needs a connection

Related nodes

• Browser Notification: a desktop notification, no account needed.
• Digest: bundle several changes into one notification.
• Element Change: watch a page for the changes to alert on.
• Telegram: send the alert to a Telegram chat instead.