n8n: a push notification from any workflow

The HTTP Request node

Add an HTTP Request node as the final step of your workflow:

• Method: POST
• URL: your Webhooky endpoint (https://api.webhooky.app/YOUR_KEY)
• Body Content Type: JSON

{
  "title": "🎯 New lead",
  "message": "{{ $json.name }} · {{ $json.email }}",
  "sound": "level_up_1"
}

Expressions work inside the JSON, so the notification carries real data from earlier nodes. title, message, sound and vibrate all override the endpoint's defaults per run.

The killer feature: an error workflow

Automations fail silently – that's their most dangerous property. n8n has a built-in answer: create a new workflow starting with the Error Trigger node, add the HTTP Request node from above with:

{
  "title": "🚨 Workflow failed",
  "message": "{{ $json.workflow.name }}: {{ $json.execution.error.message }}",
  "sound": "error_1"
}

Then set this as the Error Workflow in the settings of your important workflows. From now on, any failure anywhere rings your phone with the workflow name and error message.

Works the same in Make, Zapier & friends

The pattern is identical everywhere: Make has the HTTP module, Zapier has Webhooks by Zapier, and AI agent tools that can call HTTP endpoints (or webhooks as “tools”) can notify you the same way. If it can send a POST request, it can ring your phone.

Self-hosted note

Self-hosted n8n needs outbound HTTPS to api.webhooky.app – that's it. No inbound ports, no API keys to rotate.

Get Webhooky

Free for your first 100 notifications – set up your endpoint in two minutes.