npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-mercury

v0.1.2

Published

n8n community node for Mercury banking.

Readme

n8n-nodes-mercury

This is an n8n community node that provides webhook-based triggers for Mercury banking events. It lets you automatically start n8n workflows when transactions or account balances change.

n8n is a fair-code licensed workflow automation platform.

Installation | Credentials | Trigger Events | Usage | Architecture | Compatibility | Resources

Installation

Follow the installation guide in the n8n community nodes documentation.

Credentials

  1. In Mercury, go to Settings > API Tokens.
  2. Click Create token and give it a name (e.g., "n8n").
  3. Copy the token — it's only shown once.
  4. In n8n, go to Credentials > Add Credential and search for Mercury API.
  5. Paste the token into the API Token field and save.

Trigger Events

The Mercury node starts your workflow when one of the following events occurs:

| Trigger Type | Description | |---|---| | Transaction Created | A new transaction is created on any account | | Transaction Settled | A transaction status changes to settled | | Transaction Failed | A transaction status changes to failed | | Transaction Cancelled | A transaction status changes to cancelled | | Transaction Updated | Any update to a transaction (all status and metadata changes) | | Account Balance Updated | A checking or savings account balance changes |

Usage

  1. In n8n, create a new workflow.
  2. Add the Mercury node (search for "Mercury" in the nodes panel).
  3. Select your Mercury API credential.
  4. Choose a Trigger Type from the dropdown (e.g., "Transaction Created").
  5. Connect any downstream nodes to process the data (e.g., send a Slack message, update a spreadsheet).
  6. Activate the workflow.

Once active, the workflow runs automatically whenever the selected event occurs in Mercury. The trigger outputs the full resource — for transaction events, this is the complete transaction object; for balance events, the complete account object.

To stop receiving events, deactivate the workflow. The webhook is cleaned up automatically.

Architecture

This node uses Mercury's webhook API with automatic lifecycle management:

  • Activate workflow — n8n registers a webhook with Mercury for the selected event type.
  • Receive event — Mercury sends a webhook notification. The node verifies the HMAC-SHA256 signature, then fetches the full resource (transaction or account) from the Mercury API.
  • Deactivate workflow — n8n deregisters the webhook from Mercury.

You don't need to create or manage webhooks manually. The node handles registration and cleanup.

All incoming webhooks are verified using HMAC-SHA256 signatures (Mercury-Signature header). Webhooks with missing, invalid, or expired (>5 minutes) signatures are rejected.

Compatibility

Requires n8n >= 1.60.0.

Resources