n8n community node

n8n-nodes-docjet is an n8n community node for DocJet: render branded PDFs (invoices, reports, certificates) and PNG/OG social images from stored templates or raw HTML, directly inside your workflows. Zero runtime dependencies — all HTTP goes through n8n’s declarative routing engine.

Install

In n8n:

1. Go to Settings → Community Nodes.
2. Select Install, enter n8n-nodes-docjet, and confirm.

For a self-hosted instance you can also install from the CLI:

npm install n8n-nodes-docjet

See the official guide for installing community nodes.

Credentials

The node uses a single DocJet API credential:

Field	Value
API Key	Your DocJet API key (binfra_ prefix), issued at signup

Get a key (free tier, no card required):

curl -X POST https://api.docjet.dev/v1/signup \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com"}'

The key is sent as Authorization: Bearer <key> on every authenticated request. The credential test calls GET /v1/keys/usage.

Operations

Operation	Endpoint	Description
Render PDF	POST /v1/render?response=url	Render a PDF from a template ID or raw HTML; returns { "url": "..." } (signed download URL)
Render Image	POST /v1/image?response=url	Render a PNG image from a template ID or raw HTML; returns { "url": "..." }
List Templates	GET /v1/templates	Fetch the public template catalog (id, name, description, outputType)

For Render PDF / Render Image:

• Source — Template ID (a stored template) or Raw HTML (inline HTML, max 512 KB).
• Data — Handlebars template variables as a JSON object (e.g. { "invoice_no": "INV-001" }).

Typical workflow

1. Trigger (webhook, schedule, new order in your shop…)
2. DocJet node — Render PDF with template_id: invoice-en and data mapped from the trigger item.
3. Next step — the output item contains a signed url; attach it to an email, post it to Slack, or store it.

Errors surface as standard n8n node errors carrying the DocJet error code — see Errors & limits.