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-scribetools

v0.1.1

Published

n8n nodes for ScribeTools: OCR, editable Word, tables, translation and custom data extraction for Arabic-script and multilingual documents.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ssraza21ssraza21

Keywords

n8n-community-node-packageocrarabicpdfdocument-extractiontranslation

Readme

n8n-nodes-scribetools

This is an n8n community node. It lets you use ScribeTools in your n8n workflows.

ScribeTools turns scanned and digital documents, with a focus on Arabic-script languages (Arabic, Urdu, Persian), into editable Word files, plain text, spreadsheets of tables, translations, searchable PDFs, EPUB eBooks, and structured JSON with the fields you choose.

Installation · Operations · Credentials · Compatibility · Usage · Resources

Installation

Follow the installation guide in the n8n community nodes documentation. The package name is n8n-nodes-scribetools.

Operations

ScribeTools node

  • Document → Process: upload a PDF or image from a binary field and start a job. With Wait for Result on, the node waits for the job and returns the result files as binary data, plus text (TXT results) or data (JSON results) on each result. Outcomes: Editable Word Document, Extract Text, Extract Tables, Translate Document, Searchable PDF, EPUB eBook, Extract Custom Data (fields from a JSON Schema).
  • Job → Get, Get Many, Get Results, Cancel
  • Result → Download (binary), Get Content (TXT/JSON as data, up to 1 MiB)
  • Account → Get (plan and available pages)

ScribeTools Trigger node

  • Polls for jobs that finished (completed and partially completed by default).

Long documents can take 20 minutes or more. For those, turn Wait for Result off and either use the ScribeTools Trigger in a second workflow, or set Options → Callback URL to {{ $execution.resumeUrl }} and follow the node with a Wait node set to On Webhook Call.

Credentials

You need a ScribeTools API key. Sign in to ScribeTools, open Settings → API keys and create one (API keys are available on paid accounts). In n8n, create a ScribeTools API credential and paste the key. Leave API URL as https://api.scribetools.com.

Compatibility

Built and linted with @n8n/node-cli 0.51 against n8n-workflow 2.x (n8n 1.x and later). No runtime dependencies.

Usage

Example: a Google Drive Trigger (new file in a folder) → Google Drive: Download → ScribeTools: Document → Process (Editable Word Document) → Google Drive: Upload (the data binary field) to an "Output" folder.

Pages are charged as in the ScribeTools app: one page per processed page, held when the job starts and settled when it finishes. Failed pages are not charged.

Resources