@pixldocs/n8n-nodes-pixldocs
v0.1.3
Published
n8n community node for PixlDocs — render invoices, certificates, tickets and social images from templates + JSON, right inside your workflows.
Maintainers
Readme
@pixldocs/n8n-nodes-pixldocs
n8n community node for PixlDocs — render invoices, certificates, tickets and social images from your templates inside any n8n workflow. "New Stripe payment → render branded invoice → attach to Gmail" with zero code.
Install
In n8n: Settings → Community Nodes → Install → @pixldocs/n8n-nodes-pixldocs.
Create a PixlDocs API credential with an API key from Workspace Settings → API keys (the credential test verifies it instantly).
Operations
| Operation | What it does | |---|---| | Render Document | Synchronous render — the finished PDF/PNG/WebP arrives as binary data, ready for Gmail/Slack/Drive nodes | | Render Async | Enqueue a render job (pair with PixlDocs webhooks for completion) | | Get Async Render | Poll an async job by id | | List Templates | One item per template you can render | | Get Template Fields | The clean data keys a template accepts — build your Data JSON from these |
The template picker is a live dropdown of your workspace's templates. Data (JSON) accepts the same clean-key contract as the API: flat keys, nested section objects, repeatable arrays (line items). Unrecognized keys are surfaced in the output's unmatched_keys so silent mismatches can't hide.
Example
- Webhook node receives an order.
- PixlDocs → Render Document: template = your invoice, Data =
{ "client_name": "{{ $json.customer }}", "items": {{ JSON.stringify($json.line_items) }} } - Gmail node: attach the binary
dataproperty. Done.
