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

@relayfile/provider-n8n

v0.1.4

Published

Relayfile connection provider for self-hosted n8n instances.

Readme

@relayfile/provider-n8n

Relayfile connection provider for self-hosted n8n instances.

This package wraps the n8n REST API with two layers:

  • A Relayfile-compatible provider class that extends IntegrationProvider
  • A convenience layer for credentials, workflows, executions, node discovery, and webhook ingestion

Install

npm install @relayfile/provider-n8n @relayfile/sdk

Configure n8n

This provider targets self-hosted n8n instances. Set baseUrl to your own deployment URL, for example https://n8n.example.com or http://localhost:5678.

API key auth

  1. Log in to your n8n instance.
  2. Go to Settings > n8n API.
  3. Enable the public API if it is not already enabled.
  4. Create an API key and store it in an environment variable such as N8N_API_KEY.

Basic auth

If your self-hosted deployment protects n8n with HTTP basic auth, pass username and password to the provider instead of an API key. A common local setup looks like:

export N8N_BASE_URL="http://localhost:5678"
export N8N_BASIC_AUTH_ACTIVE="true"
export N8N_BASIC_AUTH_USER="relay"
export N8N_BASIC_AUTH_PASSWORD="file"

Usage

import { RelayFileClient } from "@relayfile/sdk";
import { createN8nProvider } from "@relayfile/provider-n8n";

const relayfile = new RelayFileClient({
  baseUrl: process.env.RELAYFILE_BASE_URL!,
  token: process.env.RELAYFILE_TOKEN!,
});

const provider = createN8nProvider(relayfile, {
  baseUrl: process.env.N8N_BASE_URL!,
  apiKey: process.env.N8N_API_KEY,
});

const credentials = await provider.listCredentials({ type: "githubApi" });
const workflow = await provider.activateWorkflow("workflow-123");
const proxyResponse = await provider.proxy({
  method: "GET",
  baseUrl: "https://api.github.com",
  endpoint: "/user",
  connectionId: "credential-123",
});

Basic-auth configuration:

const provider = createN8nProvider(relayfile, {
  baseUrl: process.env.N8N_BASE_URL!,
  username: process.env.N8N_BASIC_AUTH_USER!,
  password: process.env.N8N_BASIC_AUTH_PASSWORD!,
});

Webhooks

n8n Webhook nodes expose both production and test URLs:

  • Production: {N8N_URL}/webhook/{path}
  • Test: {N8N_URL}/webhook-test/{path}

N8nProvider.ingestWebhook() normalizes the incoming webhook payload and forwards it to Relayfile using a canonical path derived from the normalized event.

Scripts

npm run build
npm test