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-docxtemplater-pdf-converter

v0.1.7

Published

n8n node to convert DOCX templates to populated DOCX and PDF files

Readme

n8n-nodes-docx-to-pdf

This is an n8n community node that provides functionality to convert DOCX templates to populated DOCX and PDF files. It allows users to fill in template variables in DOCX files with real data and then convert the resulting document to PDF format.

Features

  • Load DOCX templates with placeholders/variables
  • Populate templates with JSON data
  • Save the populated DOCX files
  • Convert the populated DOCX files to PDF format
  • Comprehensive error handling for all operations

Installation

Follow these steps to install this custom node:

Local Installation (Development)

  1. Clone this repository:

    git clone https://github.com/yourusername/n8n-nodes-docx-to-pdf.git
  2. Navigate to the project directory:

    cd n8n-nodes-docx-to-pdf
  3. Install dependencies:

    pnpm install
  4. Build the code:

    pnpm build
  5. Create a symbolic link in your n8n installation:

    npm link
  6. In your n8n installation directory:

    npm link n8n-nodes-docx-to-pdf

Global Installation (Production)

Once published, you can install this node globally using npm:

npm install n8n-nodes-docx-to-pdf -g

Or if you use n8n desktop app, install it through the Community Nodes tab.

Usage

  1. Add the DocxToPdf node to your workflow.
  2. Configure the following settings:
    • Template File: Path to your DOCX template file with variables in the format {{ variableName }}
    • Output DOCX File: Path where you want to save the populated DOCX file
    • Output PDF File: Path where you want to save the converted PDF file
    • JSON Data: JSON object with key-value pairs that match the variables in your template

Example Template

Your DOCX template might include variables like:

Dear {{ name }},

Thank you for your {{ product }} order.
Your order number is {{ orderNumber }}.

Best regards,
{{ companyName }}

Example JSON Data

{
  "name": "John Doe",
  "product": "Premium Subscription",
  "orderNumber": "ORD-12345",
  "companyName": "Your Company Name"
}

Publishing to npm

To publish this node to npm, follow these steps:

  1. Update package.json with your information:

    • Update the name, author, repository, and homepage fields
    • Make sure the version is correct
  2. Build the package:

    pnpm build
  3. Login to npm:

    npm login
  4. Publish the package:

    npm publish

License

This project is licensed under the MIT License - see the LICENSE.md file for details.