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

@org21/n8n-nodes-org21

v0.1.0

Published

n8n community node that sniffs workflow metadata, logs, timing, and errors, then triggers a sub-flow via webhook or n8n API.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ofekdekelofekdekel

Keywords

n8n-community-node-packagen8nworkflowobservabilitymetadatatriggersub-flowmonitoring

Readme

@org21/n8n-nodes-org21

n8n community node that sniffs workflow metadata, logs, timing, and errors from any flow — then triggers a sub-flow via webhook or n8n API.

Use it for observability, auditing, debugging, or orchestrating complex multi-workflow pipelines.

Installation

Community Nodes (recommended)

  1. Go to Settings > Community Nodes in your n8n instance
  2. Select Install a community node
  3. Enter @org21/n8n-nodes-org21
  4. Agree to the risks and click Install

Manual

cd ~/.n8n/nodes
npm install @org21/n8n-nodes-org21

Nodes

Flow Sniffer

Drop this node into any workflow to capture execution data and trigger a sub-flow.

What it captures

| Toggle | Data | Default | |--------|------|---------| | Metadata | Workflow ID/name, execution ID, node name, timestamp | On | | Item Data | The actual JSON items passing through the node | On | | Timing | Execution timing, input/output item counts | On | | Errors | Error details from items with errors | On | | Environment | Process environment variables (filtered for safety) | Off |

Trigger modes

  • Webhook POST — POST sniffed data to any URL (typically a sub-flow's Webhook trigger)
  • n8n API — Trigger a specific workflow via the n8n REST API (requires API key)

Options

  • Pass Through — When enabled (default), original items pass through unchanged so the main flow continues normally. When disabled, the node outputs the sniffed payload instead.
  • Additional Headers — Add custom HTTP headers to the trigger request.

Credentials

Org21 API (n8n API Key)

Required only when using n8n API trigger mode. Enter your n8n instance API key.

Generate one at: Settings > API > Create API Key in your n8n instance.

Example use cases

  1. Audit trail — Sniff every execution and POST to a logging sub-flow that writes to a database
  2. Error monitoring — Capture errors and trigger an alerting workflow (Slack, email, PagerDuty)
  3. Pipeline orchestration — Chain workflows together by sniffing completion data and triggering the next stage
  4. Cost tracking — Capture execution metadata and aggregate it in a reporting workflow

Compatibility

  • n8n >= 1.0.0
  • Node.js >= 22

License

MIT