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

activepieces-polydoc

v0.1.3

Published

PolyDoc connector for Activepieces: convert HTML or a URL to PDF, capture screenshots, and generate EU e-invoices (Factur-X / ZUGFeRD).

Downloads

545

Readme

activepieces-polydoc

An Activepieces community piece for PolyDoc, a REST API that converts HTML or URLs to PDF, captures screenshots, and generates EU-compliant e-invoices (Factur-X / ZUGFeRD hybrid PDF/A-3).

One piece, three actions:

  • Convert to PDF - layout, margins, page format, page ranges, bookmarks, accessible/tagged PDFs.
  • Capture Screenshot - PNG / JPEG / WebP, full page, viewport and device-pixel-ratio control, file or base64 output.
  • Generate E-Invoice - Factur-X or ZUGFeRD, profiles from minimum to extended.

Each action takes content from a URL, an inline HTML string, or a saved template (with Liquid templateData). The result is returned as a file by default, or uploaded to your cloud storage (presigned URL) or delivered to a webhook.

Installation

In Activepieces: Settings -> My Pieces -> Install Piece, then enter the npm package name activepieces-polydoc.

For a self-hosted instance you can also upload a built tarball via Platform Admin -> Setup -> Pieces.

Connection

Create a PolyDoc connection with an API key from dashboard.polydoc.tech (API Keys). The key is sent as Authorization: Bearer <key>. Toggle Sandbox to test against sandbox quota (output is watermarked). The connection test runs a tiny forced-sandbox screenshot, so it never touches production quota.

Anything not in the UI?

Every action has an Advanced (JSON) field that is deep-merged into the request body, so any API capability not surfaced as a control (e.g. pdf.watermark, pdf.pdfa, pdf.encryption, render.*, request.*) is still reachable. See the full request schema at docs.polydoc.tech.

Example flows

Importable flow templates live in examples/, one per use case. Import them via Flows -> Import Flow:

  • pdf-from-template-webhook.json - invoice PDF from a saved template, triggered by a webhook.
  • url-screenshot-scheduled.json - scheduled full-page screenshot of a URL.
  • einvoice-webhook-to-pdf.json - ZUGFeRD / EN 16931 e-invoice from a webhook payload.

Development

npm install
npm run build       # tsc -> dist/
npm run lint        # eslint
npm test            # unit tests (request body builder)
npm run scrub:check # fail on em-dashes in UI/customer text

Live smoke test against the real API (uses sandbox quota, needs network access to api.polydoc.tech):

POLYDOC_API_KEY=api_xxx POLYDOC_TEMPLATE_ID=jlE-whg npm run test:integration

License

MIT