Integration · n8n Beta
Convert files inside your n8n workflows.
Add PrivConvert’s privacy-first conversion engine to any automation. Drop the node between a trigger and an action, pick from 330+ conversions, and get the file back — processed in memory, never stored.
Install the node
In n8n go to Settings → Community Nodes → Install and add n8n-nodes-privconvert.
Add your API key
Create PrivConvert credentials and paste your pk_live_ key. The Test button confirms it instantly.
Drop it in a workflow
Pick a conversion, wire in a file, and PrivConvert returns the converted file — processed in RAM, never stored.
n8n-nodes-privconvert Self-hosted n8n: Settings → Community Nodes → Install. Verified availability on n8n Cloud is rolling out — ask for early access.
Why the node
Everything you need to automate conversions.
Live tool catalog
The conversion picker loads 330+ tools straight from our API, so it is always in sync — no hard-coded lists that go stale.
Binary in, binary out
Feed any file from a previous node; get the converted file back as binary, ready to save, upload, or email.
Zero data retention
Every file is processed entirely in memory and wiped the instant the conversion finishes. Nothing ever touches disk.
Works as an AI tool
The node is exposed as a callable tool, so an n8n AI Agent can convert files on its own as part of a larger automation.
Three operations
Convert File, List Tools, and Get Usage — enough to build, discover, and monitor conversions from any workflow.
Enforced server-side
Plan, quota, file size and rate limits are all enforced on our servers — the node is a thin, secure client.
A thin client for a private engine.
The node never enforces anything itself — it just forwards your file with your key. Your plan, quota, file-size and rate limits are all enforced on our servers, so nothing can be bypassed by editing a workflow. And because every conversion runs in RAM and is wiped instantly, sensitive documents never sit on a third-party disk.
- In-memory processing, zero disk writes
- Files deleted the instant a conversion completes
- All limits enforced server-side, not in the node