KSD Vietnam: n8n workflow automation across Microsoft 365 and HubSpot
KSD Vietnam is a tuna export business with real workflows around documents, purchase intake, warehouse intake, accounting, and production forms. OPERCEL used n8n as the orchestration layer across Microsoft Graph, SharePoint/OneDrive, HubSpot, Excel workbooks, internal APIs, and render/upload/update steps.
n8nworkflow orchestrator
GraphSharePoint/OneDrive API
PNMHpurchase intake forms
Challenge
Challenge
KSD had many files and tables behind purchase intake, raw-material intake, accounting, BOM lookup, production reports, and form lists. When each step lives in a workbook, shared folder, or separate system, the operations team has to read files, find pending items, create forms, upload documents, update links, sync accounting rows, and return results through many disconnected actions.
Approach
Approach
Used n8n as the orchestration layer, splitting work into webhook APIs, scheduled polling, UI HTML endpoints, and batch jobs.
Connected Microsoft Graph to read SharePoint sites, drives, folders, workbook tables, upload and download files, append batch rows, and update document links.
Connected HubSpot so deposit LC and stage changes could trigger document workflows across SharePoint and OneDrive.
Built internal APIs and form flows for PNMH, raw-material intake, BCSX, BOM lookup, history, form lists, and cached responses.
Automated PNMH rendering from HTML/Pandoc templates into PNG, then uploaded files, updated sheet links, and cleaned temporary files.
Standardized accounting sync with dry-run and commit branches, batch-result validation, deduplication, and explicit JSON responses.
Expected result
Expected result
File reads, pending checks, form creation, accounting-row appends, document uploads, and result responses became stateful workflows.
The team gained small API/UI surfaces for selecting PNMH records, creating forms, checking BOM data, reading BCSX/TN history, and retrieving form lists without opening multiple workbooks.
Accounting sync gained dry-run/commit branches and validation, reducing the risk of writing incorrect data.
HubSpot, SharePoint, and OneDrive became coordinated data sources instead of scattered files.
The workflow canvas now doubles as operating documentation: which node reads, renders, uploads, updates, notifies, and responds is visible.
Next case
Entana Inc: Supplier Buyer Collaboration Platform on AWS
Entana Inc needed a platform where buyers and suppliers could communicate, evaluate products, manage supplier information, and analyze costs in one system. The platform was built with React, Node.js/Express, PostgreSQL, and deployed on AWS for scalability, reliability, and security.