Pinglet Start free
Docs menu
Start here
Getting started
Core concepts
Publishing Message anatomy Subscribing & the app
Guides
Generic webhook Apprise Gatus GitHub Actions Heartbeats Home Assistant Komodo n8n Prometheus Alertmanager Proxmox VE Uptime Kuma
Reference
API reference Plans & errors

n8n

The n8n-nodes-pinglet community node adds a Pinglet node to n8n, so any workflow can end in a push notification on your phone. Anyone who should receive them just opens your topic’s share link; no n8n access needed.

Install

On a self-hosted n8n instance:

  1. Go to Settings > Community Nodes and select Install.
  2. Enter n8n-nodes-pinglet as the npm package name, accept the prompt, and select Install.

Credentials

Mint an API key in your dashboard, then create a Pinglet API credential in n8n and paste the key (it starts with pinglet_).

Send a message

Add a Pinglet node wherever the workflow should notify you, select your credential, and fill in:

Field Notes
Namespace Your namespace slug, for example acme
Topic For example deploys. Created on the first publish
Message The notification body. Expressions work: ={{ "Deployed " + $json.version }}
Title Optional; defaults to the topic name
Level info, success, warning or error
Priority silent, normal or urgent (urgent breaks through Do Not Disturb)

Under Additional Fields you can add up to three badges and, on Pro plans, a metadata bag that shows on the message’s detail sheet.

The node outputs the publish response, including url (the topic’s share link) and delivered, so later steps can use them.

Subscribe to the topic in the Pinglet app via the share link from your dashboard.

Alert on failed workflows

Create a workflow that starts with an Error Trigger and ends with a Pinglet node, then pick it as the Error workflow in the settings of the workflows you want watched. For the message, use ={{ $json.workflow.name + " failed: " + $json.execution.error.message }}, set Level to error and Priority to urgent.

Without the node

On n8n Cloud, or anywhere you’d rather not install community nodes, an HTTP Request node does the same job: POST to https://pinglet.dev/acme/deploys with the header Authorization: Bearer pinglet_<your key> and a JSON body such as {"title": "Deploy done", "message": "v1.4 is live", "level": "success"}. See Publishing for every field.