To send a push notification from n8n, add an HTTP Request node to your workflow and point it at your Hook.Notifier URL. When the workflow reaches that step, a native notification lands on your phone.
n8n is a powerful automation tool, self-hosted or cloud. The one thing it cannot do on its own is reach you outside the browser. Hook.Notifier is the last mile.
Add the HTTP Request node
- In your workflow, add an HTTP Request node where you want the ping.
- Set Method to GET (or POST).
- Set URL to your Hook.Notifier URL with an object and body:
https://hooknotifier.com/{IDENTIFIER}/{KEY}?object=Workflow%20done&body=Your%20n8n%20run%20finished
- Execute the node once to send yourself a test.
That single node turns any workflow into one that pings your phone when it matters.
First get your URL
Your Hook.Notifier URL is https://hooknotifier.com/{IDENTIFIER}/{KEY}. Create a free account to get yours, then paste it into the HTTP Request node.
Use real data from your workflow
The point of n8n is that the notification carries the actual result. Use expressions in the query so each run is specific:
https://hooknotifier.com/{IDENTIFIER}/{KEY}?object={{ $json.subject }}&body={{ $json.summary }}&tags=n8n
Now instead of "workflow done" you get "New lead: Acme Corp" or "Sync failed: 3 records rejected", straight from the data that flowed through your nodes.
Send it only on failure
Put the HTTP Request node on the error branch of a node (or use an Error Trigger workflow) and add priority=high, so you only hear about it when something breaks:
https://hooknotifier.com/{IDENTIFIER}/{KEY}?object=n8n%20workflow%20failed&body={{ $json.error.message }}&priority=high&color=%23EE6767
Why it matters
Automations are supposed to save you from watching a screen. But an automation you cannot hear about is one you end up babysitting anyway. One HTTP Request node gives every n8n workflow a voice that reaches your pocket, for free.
New to this? Start with how to send yourself a native push notification, or see the same idea in Make.