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-openbox-hook

v0.0.8

Published

OpenBox governance community node for n8n

Readme

n8n-nodes-openbox-hook

OpenBox governance community node for n8n.

This package provides an OpenBox: Agent node that wraps n8n LangChain chat models, memory, and tools with OpenBox governance — policy evaluation, PII redaction, HITL approval, and audit traces — without changing your existing workflow structure.

Install

In n8n, open Settings > Community Nodes, choose Install, and enter:

n8n-nodes-openbox-hook

Restart n8n if prompted.

Credentials

Create an OpenBox API credential in n8n with:

| Field | Required | Description | |---|---|---| | API Key | Yes | Your OpenBox API key. Live keys start with obx_live_; test keys with obx_test_. | | Agent DID | No | Agent decentralised identifier (did:aip:<uuid>). Required only for agents with signing_required = true. | | Agent Private Key | No | Base64-encoded raw 32-byte Ed25519 seed. Paired with Agent DID for signed requests. |

Get your API key from dashboard.openbox.ai.

Usage

Basic setup

  1. Add an OpenBox: Agent node to your workflow.
  2. Connect a Chat Model sub-node (e.g. OpenAI Chat Model, Anthropic Chat Model) to the Chat Model input.
  3. Optionally connect Memory and Tool sub-nodes.
  4. Attach your OpenBox API credential to the node.
  5. Configure the Agent Name (used to identify this agent in OpenBox governance traces) and the Task Queue.

The node exposes the same inputs and outputs as the standard n8n AI Agent node, so it is a drop-in replacement.

Example workflow

[Chat Trigger]
      │
      ▼
[OpenBox: Agent]  ←──  [OpenAI Chat Model]
      │            ←──  [Window Buffer Memory]
      │            ←──  [Calculator Tool]
      ▼
[Set node / downstream steps]

OpenBox: Agent node settings:

  • Agent Name: customer-support-bot
  • Task Queue: n8n
  • Governance: Enabled (default)

When the agent runs, OpenBox evaluates each LLM call and tool invocation against your configured policies. If a call requires approval (HITL), the node pauses and polls until a decision is received.

Advanced: Agent DID signing

For agents configured with signing_required = true in OpenBox, fill in the Agent DID and Agent Private Key fields in the credential. Every request to the OpenBox API will be signed with an Ed25519 signature automatically.

Local development

npm install
npm run build
npm test
npm run lint

To verify the package scan passes before publishing:

npx @n8n/scan-community-package n8n-nodes-openbox-hook