n8n-nodes-anh

This is an n8n community node. It lets you use Azure Notification Hubs in your n8n workflows.

Azure Notification Hubs is a cross-platform push notification routing service that lets you send messages from a single backend to millions of devices. It handles platform-specific formatting and supports targeting through tags and templates.

n8n is a fair-code licensed workflow automation platform.

Table of Contents

1. Installation
2. Operations
3. Credentials
4. Compatibility
5. Usage
6. Resources
7. Development

Installation

Follow the installation guide in the n8n community nodes documentation. This module is named n8n-nodes-anh.

Operations

This node supports the following Send types:

|Send Type|Description| |:-|:-| |Audience|Sends to a specific audience using tags.| |Broadcast|Sends to all registered devices.| |Direct|Sends to a specific device handle.| |Scheduled|Sends at a specified future time.|

NOTICE This module only supports raw template notifications at this time.

Credentials

To use this node, you need credentials. To acqure credentials, you must:

1. Sign up for an Azure account if you do not already have one.
2. Follow the Azure Notification Hub Quickstart to create a namespace and notification hub.
3. In the Azure Portal, go to Notification Hubs → select your hub → Overview → copy the Hub Name.
4. In the Azure Portal, go to Notification Hubs → select your namespace → select your hub → Access Policies → copy the connection string.

PERMISSIONS: The access policy must have Manage and Send permissions for this node to work. Listen is not required, but will not prevent this node from working.

Once you've acquired Azure Notification Hub credentials, use them to create a new n8n credential. Select Azure Notification Hubs as the credential type:

Compatibility

This node was written and tested in the following environment:

• n8n v1.108.1
• platform: npm
• Node.js v24.0.0
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community

Usage

Azure Notification Hubs supports many different platforms:

• Apple Push Notification Service (APNS)
• Firebase Cloud Messaging (FCM)
• Windows Notification Service
• Many others

Each of these platforms have specific notification formats. At this time, this node does not support GUI creation of these types of messages.

This node supports Notification Hubs templates.

Your client application implements templates with device registration. For example a Windows notification template may look like:

<toast>
  <visual>
    <binding template="ToastText01">
      <text id="1">$(tempC)</text>
    </binding>
  </visual>
</toast>

In your Azure Notification Hubs workflow node, provide JSON to populate this template. In this example, that would look like:

{
  "tempC": "24.0"
}

A successful send will return the following output:

{
  correlationId,
  trackingId,
  notificationId, // Only available in Standard and above (not Free/Basic)
  successCount,
  failureCount,
  results,
  state
}

Audience Send

This module supports sending to audiences through the use of tags and expressions. You can add as many tag groups as needed. Each tag group can be a single tag, a comma separated list of tags, or expression(s).

When multiple groups (tag items) are provided, they are treated as an "OR" operation. In other words, the notificaiton will be sent to members of "group 1" OR "group 2" OR "group 3". This translates to (group 1) || (group 2) || (group 3). If you need to use more complex logic, you can use a single group to provide a complete tag expression.

Resources

• n8n community nodes documentation

Development

I created this node because I needed native push notification capabilities in n8n, which does not exist. It currently only supports template notifications because that provides the broadest support for all use cases.

Ideally, this node would provide more visual ways to construct notifications for each platform. I added some inert placeholders in the input form during my initial development as I experimented with this. However; I do not have time to fully flesh this out and test it.

I am open to PRs that add more support for individual platforms. However; I request that anyone considering this open a discussion or issue to briefly discuss it beforehand. You'll find I'm pretty amenable, but there are a few high level standards to adhere to.

Ideally, if anyone from the Azure Notification Hubs team finds this, I would be more than happy to transfer this repo to you. I feel this is a missing piece in the n8n ecosystem, and it would be best to have the team behind it supporting it.

Copyright © 2025, Corey Butler. MIT License.