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

@statewavedev/connectors-n8n

v0.1.0

Published

n8n connector for Statewave — workflow executions, failures, and per-node errors as normalized episodes

Readme

@statewavedev/connectors-n8n

n8n connector for Statewave — turns workflow executions, failures, and per-node errors into normalized episodes under workflow:<id>.

Part of the Statewave Connectors ecosystem.

What it ingests

| Source event | Episode kind | |---|---| | Successful workflow run | n8n.workflow.executed | | Failed / crashed workflow run | n8n.workflow.failed | | Errored node (one per failed node within a failed run) | n8n.node.errored |

Pull-mode against your n8n instance's REST API (GET /api/v1/executions?includeData=true). Per-node errors are extracted from the execution's runData blob without an extra round-trip.

Quickstart

export N8N_API_KEY=...
statewave-connectors sync n8n \
  --workflows "Daily ETL,42" \
  --instance-url https://n8n.example.com \
  --since 2026-01-01 \
  --dry-run

--workflows accepts ids (visible in the n8n URL) or names. At least one is required so you don't accidentally walk every execution in the instance on first run.

Options

--workflows LIST      comma-separated ids or names (required)
--instance-url URL    base URL of the n8n instance (required, or set N8N_INSTANCE_URL)
--subject SUBJECT     override the default `workflow:<id>` subject
--since YYYY-MM-DD    earliest execution to consider
--max-items N         cap mapped episodes
--include LIST        allow-list: executions, node_errors (default: both)
--exclude LIST        deny-list (e.g. --exclude executions for failure-only ingestion)
--dry-run             preview mapped episodes without ingesting (recommended for new use)

Auth

API key only (read-only). Mint one in the n8n UI: Settings → API → Create new API key. The connector reads the key from N8N_API_KEY and the instance URL from N8N_INSTANCE_URL (or --instance-url). The key is sent only as X-N8N-API-KEY to your own n8n instance — never anywhere else.

Status

v0.1.0 — pull-mode ingestion. See RELEASE_NOTES.md.

Out of scope for v0.1 (planned):

  • Live ingestion via n8n's webhook node (workflow runs would push to Statewave directly)
  • Captured input/output snippets per node, redacted by default
  • Per-instance correlation when one connector covers multiple n8n instances