programmatic-doc-generation

Interactive onboarding for the Programmatic Doc Generation plugin — pick a default rendering engine, fetch its reference docs, and persist the choice so other skills reuse it.

Batch-render N PDFs from a directory of JSON data files against a Typst template. Use when the user wants to render many documents at once (e.g. a month of invoices, a batch of certificates) using a Typst template they already have or just scaffolded.

Capture the user's brand identity — colour palette, fonts, logo, business name and registered address, tax/VAT IDs, contact details — into a reusable brand profile that every other skill in this plugin consumes. Use when the user wants to set up branding for their document templates, define their colour palette, or store business identity for invoice/letter generation.

Visit a user-supplied website URL and infer brand identity from it — colour palette, typography, logo, business name, address, contact details — then write a brand profile the plugin's other skills consume. Use when the user says something like "use the brand from our site", "extract our palette from the website", or supplies a URL and asks to set up branding.

Take an existing document sample (PDF/image/Word) — typically an invoice, receipt, statement, or business letter — and convert it into a Typst template plus a JSON schema describing its variable fields. Use when the user says they have an example document they want to "templatise", "convert to Typst", "extract a schema from", or use as the basis for programmatic generation.

Scaffold a parameterised Typst template for batch document rendering. Use when the user asks to create a Typst template, build an invoice/receipt/statement/report/letter template, or set up a JSON-data-driven Typst document for batch CLI rendering. Produces a `.typ` template that consumes a JSON sidecar so N documents can be rendered from N data files.

Recommend a document rendering engine or service for the user's stack and constraints, and produce a worked integration example for the chosen one. Covers Typst CLI, Carbone, PDFMonkey, APITemplate.io, DocRaptor, Docmosis, Adobe Document Generation API, and contextually surfaces Templafy and PandaDoc when fit. Use when the user asks "what should I use to render PDFs?", "which doc-gen service fits n8n?", or wants a comparison before committing.

Generate an n8n workflow JSON that takes a webhook payload, renders a document via the user's chosen rendering engine, and stores or returns the resulting PDF. Use when the user wants to "set up automated invoicing in n8n", "build an n8n doc-gen workflow", or otherwise wire programmatic document generation into an n8n pipeline.

Given multiple samples of the same document type (e.g. five different invoices), infer a unified JSON schema covering every variable field across all samples. Use when the user wants to design a robust template that handles real-world variation rather than a single example.