{"product_id":"foundry-api-docustruct-extract-json-from-documents-in-n8n","title":"Foundry API DocuStruct Extract: JSON from Documents in n8n","description":"\u003ch3\u003eExtract structured JSON from documents with Foundry—directly inside n8n\u003c\/h3\u003e\n\u003cp\u003eThis n8n workflow runs manually to send a Base64-encoded document plus a text snippet to Foundry’s DocuStruct Extract and JSON Forge endpoints—then returns normalized, schema-aligned JSON for fast downstream automation.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cp\u003eDesigned for n8n users, automation engineers, and SaaS operators, it performs two coordinated extraction\/normalization steps:\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eManual trigger:\u003c\/strong\u003e The workflow starts when you run it manually in n8n.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSet your input payload:\u003c\/strong\u003e You provide \u003cem\u003efilename\u003c\/em\u003e, \u003cem\u003emimeType\u003c\/em\u003e, the document as \u003cem\u003eBase64 file content\u003c\/em\u003e, a target \u003cem\u003eJSON schema\u003c\/em\u003e, and an optional \u003cem\u003etext\u003c\/em\u003e string.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFoundry DocuStruct Extract API call:\u003c\/strong\u003e The workflow sends your Base64 document and the schema to extract structured JSON from the document.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFoundry JSON Forge API call:\u003c\/strong\u003e It then normalizes the provided text into structured JSON that matches the \u003cem\u003esame schema\u003c\/em\u003e.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDocument-to-JSON ingestion:\u003c\/strong\u003e Convert uploaded documents into consistent, schema-ready JSON for indexing, review, or storage.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eHybrid extraction \u0026amp; normalization:\u003c\/strong\u003e Use document extraction (DocuStruct Extract) alongside text normalization (JSON Forge) to standardize outputs.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSchema-driven workflows:\u003c\/strong\u003e Apply a custom schema to ensure extracted\/normalized data stays compatible with your existing systems.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eAuthentication:\u003c\/strong\u003e Create an n8n HTTP Header Auth credential that sends your Foundry API key as \u003ccode\u003eX-API-Key\u003c\/code\u003e, and select it in both Foundry HTTP Request steps.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNodes used:\u003c\/strong\u003e \u003ccode\u003eManual Trigger\u003c\/code\u003e, \u003ccode\u003eSet\u003c\/code\u003e, \u003ccode\u003eSticky Note\u003c\/code\u003e, and \u003ccode\u003eHTTP Request\u003c\/code\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSetup:\u003c\/strong\u003e Replace \u003ccode\u003eREPLACE_WITH_AUTHORIZED_BASE64_FILE\u003c\/code\u003e with your document’s Base64 content and set correct \u003cem\u003efilename\u003c\/em\u003e and \u003cem\u003emimeType\u003c\/em\u003e. Update the \u003cem\u003eschema\u003c\/em\u003e (and optional \u003cem\u003etext\u003c\/em\u003e) to match the structure you want Foundry to extract\/normalize.\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":45738618192051,"sku":"N8N-17521","price":32.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/9eqqCiGVifICJRnGg_2RF_AUuiXVfV.png?v=1785230363","url":"https:\/\/buyflowscripts.com\/products\/foundry-api-docustruct-extract-json-from-documents-in-n8n","provider":"N8N Commerce","version":"1.0","type":"link"}