Integrate Unsiloed with n8n

Use the Unsiloed community node to read a document inside an n8n workflow. The Parse operation returns the document as Markdown. Extract returns fields defined by a JSON Schema, with confidence scores and source citations when available. The node handles job polling, so you don’t need separate HTTP or Wait nodes to check processing status. In this guide, we’ll download a sample invoice, parse it, then extract its vendor, invoice number, and total. The resulting values can feed a spreadsheet or database node. Here’s the finished workflow running:

The n8n workflow runs: Download invoice fetches the PDF, the Unsiloed node extracts it, and Map invoice values outputs the vendor, invoice number HV-2087, and total $11,557.22

Requirements for the n8n Integration

You need:

A self-hosted n8n instance with community node installation enabled
An Owner or Admin account on that instance
An Unsiloed API key from the Unsiloed dashboard

This guide was tested with n8n 2.36.7 and version 1.0.5 of the Unsiloed community node.

This package requires self-hosted n8n. n8n Cloud only installs verified community nodes, and the Unsiloed package is currently unverified. See the node installation requirements.

Install the Unsiloed Node

Install the package through n8n’s settings, then add it to a workflow.

Install the community package

Open Settings → Community nodes and click Install (or Install a community node if no packages are installed). Enter the following npm package name:

n8n-nodes-unsiloed

Select the community package acknowledgment and click Install. The package should appear in the installed list with one node named Unsiloed.

The n8n community node installation dialog with n8n-nodes-unsiloed entered as the npm package name

If Community nodes is missing, see the n8n installation guide.

Create a workflow

Create a blank workflow and add Manual Trigger (labeled When clicking Execute workflow on the canvas). This lets us test the document-processing steps before connecting an email or upload trigger.

Download the sample invoice

Connect an HTTP Request node after the trigger. Set Method to GET and enter the direct download URL for the sample invoice:

https://raw.githubusercontent.com/Unsiloed-AI/n8n-nodes-unsiloed/main/examples/sample-invoice.pdf

Under Options, add Response. Set Response Format to File and Put Output in Field to data. Rename the node Download invoice.

The HTTP Request node is configured to download the sample invoice from the Unsiloed GitHub repository, with Response Format set to File and Put Output in Field set to data

Click Execute step. The node’s Binary output should show data with the invoice file. Unsiloed needs the file bytes, so the HTTP response must be a file rather than text or JSON.

Parse the Invoice into Markdown

The Parse operation reads the whole document without a field schema. Use it when the next step needs the document’s text and tables.

Add Unsiloed and store the API key

Add a node after Download invoice, search for Unsiloed, and choose Parse a document into clean markdown.In the node’s credential selector, choose Create new credential. Paste your key into API Key and leave Base URL at its default:

https://prod.visionapi.unsiloed.ai

Click Save. n8n tests the key and should show Connection tested successfully. Close the dialog and check that the Unsiloed node’s Credential field shows the new credential.

The Unsiloed API credential dialog with a masked API key and the default document-processing API URL

Configure the Parse operation

Use these settings in the Unsiloed node:

Setting	Value
Resource	Document
Operation	Parse
Document Source	Binary Property
Input Binary Field	`data`
Force OCR	On
Output	Markdown

Force OCR reads the rendered page instead of relying on its embedded text layer. Leave it on for scans and PDFs whose text layer is missing or garbled.

Run the workflow and inspect the result

Click Execute workflow, then open the Unsiloed node. In its output, select JSON to inspect the markdown field.Each run of the Unsiloed node submits a new processing job, so rerunning the step processes the document again. For manual testing, use data pinning to reuse the node’s output while configuring later steps. Unpin it before changing the operation or processing another document.

The Unsiloed Parse node returns invoice text and a line-item table in the markdown field

In a downstream node’s expression editor, use the following expression to read the document text:

{{ $json.markdown }}

Choose Full JSON in the Unsiloed node’s Output setting instead if you need the complete parse response, including chunks and segments.

Extract Invoice Fields into JSON

Use Extract when a downstream node expects specific fields. We’ll reuse the same download step and change the Unsiloed operation. Extract reads the original file from Download invoice; it doesn’t use the Markdown returned by Parse.

Define the fields to extract

Set Operation to Extract. Keep Document Source set to Binary Property and Input Binary Field set to data.Replace Schema (JSON) with this schema:

{
  "type": "object",
  "properties": {
    "vendor": {
      "type": "string",
      "description": "Company that issued the invoice"
    },
    "invoice_number": {
      "type": "string",
      "description": "Invoice number or ID"
    },
    "total_due": {
      "type": "string",
      "description": "Grand total payable, including the currency symbol"
    }
  }
}

The descriptions tell Unsiloed which values to read. This example keeps the total as a string to preserve its currency symbol. The node uses the gamma extraction model and enables citations.

Run extraction and inspect each field

Execute the workflow again and open the Unsiloed output. Each extracted field contains a value, nested confidence scores under score, and a citation when Unsiloed can ground the value in the document.

The Unsiloed Extract node returns field objects such as vendor and total_due, each with a value, confidence scores, and a source citation

A citation can be null. Check the source invoice before using the values in a workflow that posts payments or updates accounting records.For this sample, the invoice number should be HV-2087 and the total should be $11,557.22. For your own documents, inspect the output for missing or empty values before mapping it. Adjust the schema’s field descriptions if they don’t match the document.

Map the values for the next node

Add Edit Fields (Set) after Unsiloed and choose Manual Mapping. Rename the node Map invoice values, then add three String fields and switch each value to Expression:

Field	Expression
`vendor`	`{{ $json.vendor.value }}`
`invoice_number`	`{{ $json.invoice_number.value }}`
`total_due`	`{{ $json.total_due.value }}`

Leave Include Other Input Fields off to output only the mapped values. Execute the step. For this sample, the output should contain the three invoice values shown below. These can map directly to columns in a Google Sheets or database node.

The Edit Fields node maps the nested extraction values into vendor, invoice_number, and total_due string fields

If a later step needs confidence scores or citations, include those in the mapping too. For example, the total’s grounding score is available through:

{{ $json.total_due.score.grounding_score }}

The completed extraction workflow has four nodes: a manual trigger, a document download, Unsiloed extraction, and a field mapping step. Each node passes one item to the next:

The complete n8n extraction workflow: Manual Trigger connects to Download invoice, Unsiloed Extract, and Map invoice values, with successful execution indicators on all four nodes

Extend the Document Workflow

The download and field mapping steps are where other n8n nodes connect. Connect external services using their own n8n credentials.

Connect a Document Source

These nodes can supply documents before Unsiloed:

Document Source	Nodes to Connect	What to Pass to Unsiloed
Email attachments	Gmail Trigger with Simplify off	`attachment_0` for the first attachment, rather than the email body
A shared folder	Google Drive Trigger and Google Drive → Download	The downloaded file’s binary property
A known S3 object	Schedule Trigger and AWS S3 → Download a file with Bucket Name and File Key configured	The object downloaded as a binary file
A file upload or another application	n8n Form Trigger or Webhook	The uploaded file’s binary property

For Gmail, turn Simplify off in the trigger, then enable Download Attachments under Options. With the default attachment prefix, files are stored as attachment_0, attachment_1, and so on. If an email contains several attachments, split them into separate workflow items before extraction, with one document in the binary field on each item. Inspect the source node’s Binary output and set Input Binary Field to the property containing the file. The property name may differ from data. The Unsiloed node also accepts a publicly reachable document URL. Set Document Source to URL and enter it in Document URL. Unsiloed fetches the file directly; a local path or a URL that requires your browser session won’t work.

Send Results to Other Services

After Unsiloed, choose a destination for the result:

Next Step	Nodes to Connect	Example Use
Add a spreadsheet row	Edit Fields, then Google Sheets	Map the invoice number, vendor, and total to sheet columns
Store document records	Edit Fields, then Postgres	Insert extracted fields into a database table
Route values for review	If, then Slack	Notify a reviewer when a required value is missing or a score falls below your chosen threshold
Update another application	Edit Fields, then HTTP Request	Send the mapped JSON to an application API
Summarize the document	Parse, then Basic LLM Chain with a chat model	Use the `markdown` field as the text to summarize

Troubleshoot the n8n Workflow

The Unsiloed node doesn't appear

Confirm that n8n-nodes-unsiloed appears under Settings → Community nodes, then reload the editor. Your instance administrator may need to enable community packages.

The input doesn't contain a binary file

Execute the previous step and inspect its Binary tab. Its property name must match Input Binary Field. For an HTTP Request node, set Response Format to File and Put Output in Field to data.

Unsiloed rejects the API key

Open the selected Unsiloed API credential and check its key and base URL. Use the credential’s connection test to check whether Unsiloed accepts the key. The document-processing URL is https://prod.visionapi.unsiloed.ai, not the dashboard URL.

Extraction reports invalid JSON

Check that Schema (JSON) contains valid JSON with double-quoted property names and no trailing commas. Start with the schema above, then change the property names and descriptions for your document.

The job doesn't finish within the time limit

The node polls up to 90 times, with four seconds between pending responses. Try a shorter document. Rerunning the node submits a new processing job.

Unsiloed n8n Node

Node source, installation instructions, and example workflows.

Parse Documents

Parsing options and document output formats.

Extract Typed Fields

Define schemas and inspect extraction results.

Google Sheets Integration

Call Unsiloed directly from a spreadsheet with Apps Script.

Getting Started

Document Processing

Integrations

FAQ

Integrate Unsiloed with n8n

Requirements for the n8n Integration

Install the Unsiloed Node

Parse the Invoice into Markdown

Extract Invoice Fields into JSON

Extend the Document Workflow

Connect a Document Source

Send Results to Other Services

Troubleshoot the n8n Workflow

Unsiloed n8n Node

Parse Documents

Extract Typed Fields

Google Sheets Integration

​Requirements for the n8n Integration

​Install the Unsiloed Node

​Parse the Invoice into Markdown

​Extract Invoice Fields into JSON

​Extend the Document Workflow

​Connect a Document Source

​Send Results to Other Services

​Troubleshoot the n8n Workflow

​Related Guides

Unsiloed n8n Node

Parse Documents

Extract Typed Fields

Google Sheets Integration

Requirements for the n8n Integration

Install the Unsiloed Node

Parse the Invoice into Markdown

Extract Invoice Fields into JSON

Extend the Document Workflow

Connect a Document Source

Send Results to Other Services

Troubleshoot the n8n Workflow

Related Guides