This is the smallest n8n path for the spreadsheet formula problem: write an input, recalculate formulas, and verify the computed output without opening Excel, LibreOffice, Google Sheets, or a browser spreadsheet UI.
The importable workflow uses only built-in n8n nodes:
- Manual Trigger
- Code
- HTTP Request
- Code
Workflow JSON:
https://github.com/proompteng/bilig/tree/main/examples/n8n-workpaper-formula-readback
Hosted proof endpoint:
POST https://bilig.proompteng.ai/api/workpaper/n8n/forecast
Example request:
{
"sheetName": "Inputs",
"address": "B3",
"value": 0.4
}
Expected proof shape:
{
"verdict": "verified",
"editedCell": "Inputs!B3",
"beforeExpectedArr": 60000,
"afterExpectedArr": 96000,
"targetGap": 5600,
"checks": {
"formulasPersisted": true,
"restoredMatchesAfter": true,
"computedOutputChanged": true
}
}
This is not a replacement for the Microsoft Excel 365 node, and it does not mutate an existing OneDrive workbook session. It is for workflows where n8n owns the generated workbook/calculation state and needs a readback check before export, approval, email, or another downstream step.
The scoped community-node package is being prepared separately. This issue is intentionally about the no-install workflow first, because it is easier to inspect and does not ask anyone to install unverified code.
This is the smallest n8n path for the spreadsheet formula problem: write an input, recalculate formulas, and verify the computed output without opening Excel, LibreOffice, Google Sheets, or a browser spreadsheet UI.
The importable workflow uses only built-in n8n nodes:
Workflow JSON:
https://github.com/proompteng/bilig/tree/main/examples/n8n-workpaper-formula-readback
Hosted proof endpoint:
Example request:
{ "sheetName": "Inputs", "address": "B3", "value": 0.4 }Expected proof shape:
{ "verdict": "verified", "editedCell": "Inputs!B3", "beforeExpectedArr": 60000, "afterExpectedArr": 96000, "targetGap": 5600, "checks": { "formulasPersisted": true, "restoredMatchesAfter": true, "computedOutputChanged": true } }This is not a replacement for the Microsoft Excel 365 node, and it does not mutate an existing OneDrive workbook session. It is for workflows where n8n owns the generated workbook/calculation state and needs a readback check before export, approval, email, or another downstream step.
The scoped community-node package is being prepared separately. This issue is intentionally about the no-install workflow first, because it is easier to inspect and does not ask anyone to install unverified code.