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
Pinglet is a verified community node: n8n has reviewed it, and it appears in the nodes panel with the built-in nodes. Only the instance owner and admins can install it. Once it’s installed, every member of the instance can use it.
n8n Cloud
- Open a workflow, then open the nodes panel with + or by pressing N.
- Search for Pinglet. It appears under More from the community at the bottom of the panel.
- Select it and select Install.
n8n Cloud only allows verified community nodes, and only installs them from the nodes panel. If Pinglet doesn’t show up, the instance owner may have turned verified community nodes off in the Cloud Admin Panel.
Self-hosted
Install from the nodes panel as above, or go to Settings > Community Nodes, select Install and enter n8n-nodes-pinglet as the npm package name.
A few settings affect community nodes on a self-hosted instance:
- If Pinglet doesn’t show up in the nodes panel, check that
N8N_COMMUNITY_PACKAGES_ENABLEDandN8N_VERIFIED_PACKAGES_ENABLEDaren’t set tofalse. - Community nodes are installed into n8n’s
.n8nfolder (/home/node/.n8nin the Docker image), so keep that folder on a persistent volume or the node disappears when the container is recreated. - To use Pinglet as an AI Agent tool, you may need to set
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true.
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.
Use it as an AI Agent tool
The Pinglet node can be attached to n8n’s AI Agent node as a tool, so the agent decides for itself when to notify you. Describe when it should in the agent’s prompt, for example “if the email is from a customer and sounds urgent”. On self-hosted n8n, Pinglet may not appear in the agent’s tool list until you set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true.
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. The error workflow only runs for automatic executions, not when you test a workflow by hand in the editor.
For more recipes, including form submissions and a daily digest, see Push notifications from n8n workflows.
Without the node
If community nodes are switched off on your instance, 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.