n8n
The pdfforge node in your no-code workflows.
n8n-nodes-pdfforge is a community node for n8n: drop a
PDFForge node into a workflow and turn HTML or a stored template into a
PDF — then email it, upload it to a drive, attach it to a CRM record.
Install
In n8n: Settings → Community nodes → Install, package name:
n8n-nodes-pdfforgeCredentials
Create a PDFForge API credential:
| Field | Value |
|---|---|
| API Key | Your pf_live_... / pf_test_... key. |
| Base URL | https://api.pdf-forge.dev (override for staging/self-hosted). |
n8n verifies the credential with a call to GET /v1/usage.
Operations
The node has two operations:
Generate From HTML
Renders an HTML string (expressions welcome — build it from previous nodes):
| Parameter | Description |
|---|---|
| HTML | The markup to render. Tailwind classes are supported. |
| Compile Tailwind (JIT) | Enable for arbitrary/custom Tailwind classes (sends tailwindMode: "jit"). |
Generate From Template
Renders a stored template with data:
| Parameter | Description |
|---|---|
| Template ID or Slug | e.g. invoice. |
| Data (JSON) | The data object injected into the template variables — map fields from previous nodes. |
Common parameters
| Parameter | Default | Description |
|---|---|---|
| Format | A4 | Page format (A4, A5, Letter, Legal...). |
| Margin | 1.6cm | Uniform page margin. |
| Output Binary Field | data | Binary property the PDF is written to. |
| File Name | document.pdf | Name of the produced file. |
Output
Each item comes out with the PDF as binary data (in the configured
binary field) plus { success, bytes, fileName } in the JSON — ready to
feed into Send Email, Google Drive, Dropbox or any node that accepts
binaries.
Typical flow
Webhook (order received) → PDFForge (Generate From Template,
invoice + order data) → Send Email (attach the binary). Three nodes,
zero code.
Next steps
- Templates & variables — build the template the node fills.
- HTML to PDF — everything the HTML operation supports.
- MCP server — agent-driven automation instead.