keystone

n8n community nodes for Keystone PII redaction/restoration

Package Information

Downloads: 61 weeklyĀ /Ā 358 monthly
Latest Version: 0.1.2
Author: Karan Tomar

Available Nodes

Keystone Redact icon
Keystone Redact
Detect and redact personally identifiable information (PII) from text before sending to LLMs
Keystone Restore icon
Keystone Restore
Restore original PII values after LLM processing using the vault token

Documentation

Keystone Logo

n8n-nodes-keystone

Zero-Knowledge PII Redaction & Restoration for n8n

n8n community node License: MIT Version TypeScript

An n8n community node package that integrates Keystone ā€” a privacy-first middleware that redacts personally identifiable information (PII) before it reaches any LLM, and restores it afterwards. Your sensitive data never leaves your infrastructure.

āœØ Why Keystone?

Problem Keystone Solution
LLMs see raw PII (names, emails, addresses) PII is replaced with safe placeholders before the LLM ever receives the text
Data privacy compliance complexity Zero-knowledge architecture ā€” sensitive data stays on your server
Manual redaction is error-prone AI-powered entity detection with vault-backed token storage
Restoration is a separate engineering task One-step restoration using encrypted vault tokens

šŸ“¦ Nodes Included

Node Description
Keystone Redact Scans text for PII entities (names, emails, phone numbers, etc.) and replaces them with deterministic placeholders like [PERSON_A]. Returns an encrypted vault token for later restoration.
Keystone Restore Takes redacted text and a vault token, then re-inserts the original PII values ā€” even after the text has been transformed by an LLM.

šŸš€ Installation

Via n8n Community Nodes (Recommended)

  1. Open your n8n instance
  2. Go to Settings ā†’ Community Nodes
  3. Enter n8n-nodes-keystone and click Install
  4. Restart n8n

Manual Installation

# Navigate to your n8n custom nodes directory
cd ~/.n8n/nodes

# Install the package
npm install n8n-nodes-keystone

āš™ļø Prerequisites

A running Keystone server is required. The quickest way to get started:

cd keystone_core
./start.sh

This launches both the Keystone API on port 8000 and n8n on port 5678.

šŸ”§ Configuration

1. Add Credentials

  1. In n8n, go to Credentials ā†’ Add Credential ā†’ Keystone API
  2. Fill in:
Field Value Notes
Server URL http://host.docker.internal:8000 Use this when n8n runs in Docker
http://localhost:8000 Use this when running locally
API Key ks_live_xxxxxxxxxxxx Obtain from the Keystone dashboard

2. Build Your Workflow

The typical pattern wraps your LLM call between a Redact and Restore step:

[Data Source] ā†’ Keystone Redact ā†’ [LLM / AI Agent] ā†’ Keystone Restore ā†’ [Output]

Example: Privacy-Safe Email Generator

Google Sheets ā”€ā”€ā†’ Keystone Redact ā”€ā”€ā†’ AI Agent ā”€ā”€ā†’ Keystone Restore ā”€ā”€ā†’ Update Sheet
                       ā”‚                                ā”‚
                  "Dear [PERSON_A],             "Dear John Smith,
                   your order #[ID_1]..."        your order #48291..."

The LLM only ever sees anonymised placeholders ā€” never the real data.

šŸ“– Node Reference

Keystone Redact

Detects and replaces PII in the input text.

Inputs

Parameter Type Required Description
text string āœ… The text to scan and redact
taskId string ā€” Optional identifier for audit / traceability

Outputs

Field Description
redacted_text Text with PII replaced by [PERSON_A]-style placeholders
vault_token Encrypted token mapping placeholders ā†’ original values
entities_redacted Number of PII entities that were redacted
entities_warned Number of entities flagged but not redacted
status Response status from the Keystone API

Keystone Restore

Re-inserts original PII values using a vault token.

Inputs

Parameter Type Required Description
redactedText string āœ… Text containing [PLACEHOLDER] tokens
vaultToken string āœ… Encrypted vault token from the Redact step

Outputs

Field Description
restored_text Fully restored text with original PII values
entities_restored Number of entities that were restored
status Response status from the Keystone API

šŸ—ļø Development

# Clone the repo
git clone https://github.com/karantomar11/n8n-nodes-keystone.git
cd n8n-nodes-keystone

# Install dependencies
npm install

# Build
npm run build

# Watch mode (auto-rebuild on save)
npm run dev

Project Structure

n8n-nodes-keystone/
ā”œā”€ā”€ credentials/
ā”‚   ā””ā”€ā”€ KeystoneApi.credentials.ts    # API key + server URL credential
ā”œā”€ā”€ nodes/
ā”‚   ā”œā”€ā”€ KeystoneRedact/
ā”‚   ā”‚   ā”œā”€ā”€ KeystoneRedact.node.ts    # Redaction node
ā”‚   ā”‚   ā””ā”€ā”€ keystone.svg              # Node icon
ā”‚   ā””ā”€ā”€ KeystoneRestore/
ā”‚       ā”œā”€ā”€ KeystoneRestore.node.ts   # Restore node
ā”‚       ā””ā”€ā”€ keystone.svg              # Node icon
ā”œā”€ā”€ gulpfile.js                       # Copies SVG icons into dist/
ā”œā”€ā”€ tsconfig.json
ā””ā”€ā”€ package.json

šŸ¤ Contributing

Contributions are welcome! Please open an issue or submit a pull request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

šŸ“„ License

Distributed under the MIT License. See LICENSE for details.

Built with ā¤ļø by Karan Tomar

Discussion