n8n Push Notifications

Updated on November 20, 2026 n8n Repository n8n Documentation

Send n8n workflow results and error alerts to iPhone, Android, and the web
using Signalgrid and the built-in HTTP Request node.

Notifications for your automations

Receive a push notification when an n8n workflow finishes an import, processes a new order, generates an AI result, or needs your attention. Use a separate error workflow to send failure details to your phone without keeping the n8n editor open.

This guide uses n8n's built-in nodes and the Signalgrid Push API. It works with n8n Cloud and self-hosted n8n; no community node or extra package is required.

Prerequisites

  • An n8n instance with access to https://api.signalgrid.co.
  • A Signalgrid account and the app installed on your iPhone or Android device, or an enabled web client.
  • Your Signalgrid client key and a channel token. Use the token, rather than the channel name, in requests.

Configure the HTTP Request node

Add an HTTP Request node after the workflow step whose result you want to receive. For an initial test, connect a Manual Trigger directly to it.

Setting
Value
Method
POST
URL
https://api.signalgrid.co/v1/push
Authentication
None
Send Body
Enabled
Body Content Type
Form URLencoded
Specify Body
Using Fields Below

Add these body parameters. Authentication is provided by the client key in the request body.

Body parameter
Fixed value
client_key
YOUR_CLIENT_KEY
channel
YOUR_CHANNEL_TOKEN
title
n8n notification test
body
Your n8n workflow can now send notifications with Signalgrid.
type
INFO
critical
false

Replace both placeholders with your own values. Execute the test workflow and check the HTTP Request output and your Signalgrid device. A successful API response includes text: OK and code: 200.

Send a workflow completion notification

Place the notification node after the final processing step on the success path. Keep the same request settings and credentials, set type to SUCCESS, and switch the title and body values to Expression.

For the notification title, paste:

JavaScript
{{ $workflow.name + ' completed' }}

For the notification body, paste:

JavaScript
{{ 'Workflow finished successfully. Execution: ' + $execution.id }}

For a message about the result itself, use fields from the preceding node. For example, if it outputs an orderId field, the body can be:

JavaScript
{{ 'Order ' + $json.orderId + ' has been processed.' }}

The HTTP Request node normally sends one request for each incoming item. If you want one summary notification per run, enable Execute Once in the node's Settings. Ensure the preceding step produces an output item so the notification node runs. For workflows with several branches, connect it after the steps that must finish before you announce completion.

Set up n8n error notifications

Create and save a separate workflow named Signalgrid Error Alerts. Start it with an Error Trigger and connect an HTTP Request node configured as above. Set type to WARN.

Use this title expression:

JavaScript
{{ ($json.workflow?.name || 'n8n workflow') + ' failed' }}

Use this body expression. It handles execution errors and trigger errors:

JavaScript
{{ [ $json.execution?.error?.message || $json.trigger?.error?.message || 'Workflow failed', $json.execution?.lastNodeExecuted ? 'Node: ' + $json.execution.lastNodeExecuted : '', $json.execution?.url || '' ].filter(Boolean).join('\n') }}

Publish the error workflow. In each workflow you want to protect, open Settings, select Signalgrid Error Alerts as the Error workflow, and save. One error workflow can serve multiple workflows.

Testing error notifications

The Error Trigger runs for failed automatic executions, not manual editor runs. To test, create a temporary workflow with a Schedule Trigger followed by Stop And Error, select your error workflow in its settings, and publish it. After the scheduled failure produces a notification, unpublish the temporary workflow.

Critical workflow alerts

For failures that require immediate attention, set critical to true and type to CRIT. Critical delivery and the visual notification type are separate settings: changing the type alone does not enable critical delivery.

Enable the relevant notification permissions on your device. See Critical Notifications for iOS Critical Alerts and Android Do Not Disturb behavior. Keep routine workflow results non-critical.

Troubleshooting

  • The API rejects the request: verify your client key, channel token, POST method, and Form URLencoded body. Check the response body as well as the HTTP status.
  • Expressions appear as plain text: switch that parameter from Fixed to Expression and confirm the preview contains the expected value.
  • The completion node never runs: check its incoming connection and the preceding node's output items.
  • You receive duplicate notifications: check how many items enter the node and enable Execute Once for a single summary. Retries can also repeat a request.
  • No error alert arrives: verify the error workflow is selected and test with an automatic execution. A node configured to continue after an error may let the workflow finish without triggering the error workflow.
  • The API accepts the request but the phone stays silent: check the target channel, device registration, notification permissions, and device notification settings.
  • A busy workflow hits rate limits: aggregate events or reduce notification frequency. Signalgrid allows 100 requests per minute per account.

For n8n configuration details, see the official HTTP Request node and Error Trigger documentation.