Push Notification + any website
Read a table, a price or a listing on the page you're on and send it to Push Notification.
Send a push notification to your phone from any workflow, via ntfy or Pushover — straight from your browser to the push service you pick.
Each action is a node you drop on the canvas. Pair it with any of the 10 triggers — a schedule, a right-click, a page change.
This node has no fixed list of actions — the docs explain what it can do. Read the docs ↗
Read a table, a price or a listing on the page you're on and send it to Push Notification.
Classify, summarise or rewrite with a model that runs in your browser before it reaches Push Notification.
Be first to apply — get a push notification when new jobs appear on a careers page.
Checks the forecast each morning and only pings you when rain is on the way — so you grab an umbrella just in time.
A public ntfy.sh topic needs no credential. For a private ntfy server or Pushover, add a credential.
Point it at the address or service you want — the node settings explain each field.
Press Run in the editor to check the result before you put it on a trigger.
No. Your browser sends it to ntfy or Pushover, whichever you choose; AWFlow's servers never relay it. On a public ntfy.sh topic, anyone who knows the topic name can read it, so pick a long random one.
No. Local mode works without an account and keeps the Push Notification credential in this browser. Signed in, you choose per credential: this browser or your account. Installing a template from the Marketplace needs sign-in.
No. Workflows run while your browser is open. A Wait of a minute or more in the extension survives closing the tab and picks up where it left off, for up to 30 days.
No. Workflows run in your browser, so there are no per-task fees. Push Notification applies its own usual limits.