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

@stabrise/n8n-nodes-pdf-redaction

v0.1.8

Published

n8n community node for detecting and redacting PII in PDF documents via the PDF Redaction API (api.pdf-redaction.com)

Readme

n8n-nodes-pdf-redaction

This is an n8n community node. It lets you detect and redact PII (Personally Identifiable Information) in PDF documents using the PDF Redaction API in your n8n workflows.

PDF Redaction is an AI-powered service that automatically finds and redacts sensitive information in PDFs — both digital and scanned (image-based) documents. See the pdf-redaction-api documentation for the underlying REST API, and example notebooks.

Installation Operations Credentials Compatibility Usage Resources

Installation

Follow the installation guide in the n8n community nodes documentation, or the step-by-step PDF Redaction install & setup tutorial for a walkthrough with screenshots.

Operations

  • Anonymize — redact PII in a PDF, choosing which PII types (tags) to detect and redact (dates, names, emails, addresses, credit cards, etc.)
  • Anonymize with Custom Prompt — redact information described by a free-text prompt instead of predefined tags (e.g. "Redact all dates, names, and email addresses")
  • Detect PII — scan a PDF for PII and return the detected entities without redacting the document

All operations read the input PDF from a binary property on the input item and, for the anonymize operations, write the redacted PDF back to a binary property on the output item. Every operation also returns detected_pii (entities with bounding boxes) and processing_time metrics in the output JSON.

What it can detect and redact

Dates, person names, organizations, locations, emails, phone numbers, IDs, account numbers, zip codes, addresses, IP addresses, URLs, SSNs, driver licenses, passports, passwords, ages, credit card numbers, money amounts, signatures, QR codes, and faces — plus your own custom tags. Detection works on both digital PDFs and scanned/image-based PDFs (via OCR, with support for multiple languages), including rotated text.

Limits

Only the first 10 pages of a document are processed per request, and free-tier accounts are additionally capped (at the time of writing: 10 pages/request, 100 requests/month, 5 requests/minute) — check your plan at pdf-redaction.com/apikeys for current limits.

Credentials

This node uses an API key credential (PDF Redaction API):

  1. Go to pdf-redaction.com/apikeys and generate an API key.
  2. In n8n, create a new PDF Redaction API credential and paste the key into the API Key field.

Once your key is active, the API Usage tab on the same page tracks consumption against your plan — a running total plus a day-by-day breakdown — so you can see how close you are to your monthly cap before a workflow starts failing.

Compatibility

Compatible with [email protected] or later

Usage

The example below wires up a small workflow that pulls a PDF from a URL and blacks out any faces it contains, then inspects what came back.

1. Fetch a file. An HTTP Request node (GET, Response Format set to File) grabs the source PDF and hands it downstream as binary data on its data field.

2. Configure the node. Drop a PDF Redaction node after it, pick your credential, leave Operation on Anonymize, and add Face under Additional Fields → Tags. Since both nodes default to a data binary field, no field mapping is needed.

3. Run it. Executing the node returns a processed file plus a JSON payload describing every match — here, the two faces it located, each with a bounding box, alongside a per-stage timing breakdown.

4. Check the result. Opening the output file confirms both faces are blacked out on the page.

5. The finished workflow. Three nodes, each with a green checkmark after a successful run.

Any node that produces binary data works as the source — a webhook payload, Read/Write File from Disk, an email attachment, or a cloud-storage node — as long as its output field name matches the Input Binary Field you set on PDF Redaction.

For the full step-by-step tutorials this walkthrough is based on, see:

Resources