How to install Claix in n8n? Easy in 3 minutes
Install the n8n-nodes-claix community node, configure the Claix API credential, and extract PDF, Word, or Excel to typed JSON without manual HTTP Request.
Why install the native Claix node in n8n?
Previously you had to wire up a generic HTTP Request node: multipart/form-data, x-api-key header, schema_id, and the binary by hand. The community node n8n-nodes-claix makes it native: it appears in the node panel with its own icon, secure credentials, and three ready-made operations (PDF, Word document, and Excel/CSV → JSON). It aligns with Claix public documentation and the OpenAPI spec at https://www.claix.dev/openapi.yaml.
| Approach | Manual HTTP Request | Claix node (n8n-nodes-claix) |
|---|---|---|
| Setup time | 10–20 min per workflow | Under 3 minutes |
| Credentials | Headers pasted by hand | Claix API stored securely |
| Operations | Different URLs and bodies per type | Visual selector: PDF / Doc / Excel |
| Maintenance | Breaks the flow if the API changes | Update the npm package |
Prerequisites
- n8n instance with Community nodes enabled (Cloud, self-hosted, or Docker).
- Claix account with at least one schema created (PDF, document, or Excel → JSON).
- API key from the Claix dashboard (https://www.claix.dev).
- Package published on npm: n8n-nodes-claix — https://www.npmjs.com/package/n8n-nodes-claix
Step 1: Install the community node (1 minute)
In your n8n instance open Settings → Community nodes → Install. Enter the package name exactly:
- Package name: n8n-nodes-claix
- Click Install and accept the community node installation.
- Wait for n8n to download the package from npm and restart nodes if prompted.
Official n8n docs on community nodes: https://docs.n8n.io/integrations/community-nodes/installation/. npm package page: https://www.npmjs.com/package/n8n-nodes-claix
Step 2: Create the Claix API credential (1 minute)
Go to Credentials → Add credential → search for Claix API. Paste your API key from the Claix dashboard. The node sends the key as the x-api-key header, as documented at https://www.claix.dev/en/documentation/excel-to-json.
- Display name: whatever you prefer (e.g. Claix production).
- API Key: your secret key from the Claix panel.
- Save the credential; n8n encrypts it and reuses it across all workflows.
Step 3: First workflow in 60 seconds
3.1 Trigger with binary file
Use IMAP Email (attachment), Webhook, Google Drive, or S3. n8n must receive the file as Binary Data; by default the property is called data.
3.2 Claix node
- Add the Claix node from the search panel (transform category).
- Select the Claix API credential you created earlier.
- Operation: Extract PDF to JSON, Extract Document to JSON, or Extract Excel to JSON.
- Schema ID: UUID of the schema you created in the Claix dashboard.
- Input Binary Field: data (or your binary property name).
3.3 Destination
Connect PostgreSQL, Supabase, Airtable, or Slack. The output JSON already matches your schema (strings, numbers, arrays). Drag keys into the next node without a Code node or Regex.
Operations and endpoints (quick reference)
| Node operation | Claix endpoint | Accepted formats |
|---|---|---|
| Extract PDF to JSON | POST https://www.claix.dev/api/pdf-json | PDF (max. 15 MB) |
| Extract Document to JSON | POST https://www.claix.dev/api/doc-json | .docx, .txt, .md, .rtf (max. 10 MB) |
| Extract Excel to JSON | POST https://www.claix.dev/api/excel-json | .xlsx, .csv |
All endpoints send multipart/form-data with file and schema_id. Full details at https://www.claix.dev/en/documentation/excel-to-json and OpenAPI spec at https://www.claix.dev/openapi.yaml.
Local installation (developers)
If you contribute or test before publishing to npm:
- Clone the repo and enter the n8n-nodes-claix folder.
- npm install && npm run build
- npm link in the package and npm link n8n-nodes-claix in n8n's custom directory.
- Restart n8n and verify the Claix node appears in the panel.
Common troubleshooting
- Node not showing: confirm Community nodes is enabled and you installed n8n-nodes-claix (not another name).
- 401/403 error: check the API key in Credentials → Claix API.
- 400 schema error: schema_id must be a valid UUID from the Claix dashboard.
- No binary: the previous node must expose Binary Data on the indicated property (default data).
- Update version: in Community nodes, uninstall and reinstall, or update from npm if your instance allows it.
Useful links
- npm package n8n-nodes-claix: https://www.npmjs.com/package/n8n-nodes-claix
- Claix API documentation: https://www.claix.dev/en/documentation/excel-to-json
- OpenAPI: https://www.claix.dev/openapi.yaml
- Install community nodes (n8n): https://docs.n8n.io/integrations/community-nodes/installation/
- PDF → JSON guide in n8n: /blog/pdf-a-json-n8n-ia-api
- Word → JSON guide in n8n: /blog/doc-a-json-n8n-ia-api
Conclusion
In three minutes you have Claix inside n8n without a generic HTTP Request: install n8n-nodes-claix, configure the credential, pick operation and schema_id, and route typed JSON to the rest of the flow. It's the fastest way to go from chaotic documents to data ready for your database or CRM.
Frequently asked questions (FAQ AEO)
- How do I install Claix in n8n?
- Settings → Community nodes → Install → enter n8n-nodes-claix → Install. Then create the Claix API credential with your API key.
- What is the npm package name for Claix in n8n?
- n8n-nodes-claix — https://www.npmjs.com/package/n8n-nodes-claix
- Do I need an HTTP Request node?
- No. The Claix community node sends multipart/form-data, x-api-key, and schema_id for you. You only need binary + schema_id.
- What file types does the Claix node support in n8n?
- PDF, documents (.docx, .txt, .md, .rtf), and Excel/CSV, depending on the operation you choose in the node.
- Where do I get schema_id?
- In the Claix dashboard when creating or editing a PDF, document, or Excel → JSON schema. Copy the UUID and paste it into the node's Schema ID field.