Bilig can be used from Pipedream as a workflow action. The action writes one forecast input cell, asks Bilig WorkPaper to recalculate dependent formulas, and fails unless Bilig returns verified readback proof.
The public upstream review is:
gregkonush:bilig-workpaper-verify-readbackbilig_workpaperbilig_workpaper-verify-formula-readbackUse this path when a Pipedream workflow needs spreadsheet-style business logic without opening Excel, LibreOffice, Google Sheets, or a browser UI.
The action calls:
POST /api/workpaper/n8n/forecast
with:
{
"sheetName": "Inputs",
"address": "B3",
"value": 0.4
}
and requires:
{
"verified": true,
"checks": {
"formulasPersisted": true,
"restoredMatchesAfter": true,
"computedOutputChanged": true
}
}
The default hosted proof writes 0.4 to Inputs!B3, changes expected ARR from
60000 to 96000, and returns the edited cell plus before/after computed
values.
The upstream action uses the connected account’s base_url from $auth. It
does not expose Base URL as an action prop. This matches Pipedream maintainer
feedback and keeps the runtime input focused on workbook data:
The local staging artifact is under:
integrations/pipedream-bilig-workpaper
The upstream PR is the source of truth for the Pipedream registry review state and final app slug.
Pipedream should own workflow triggers, schedules, branching, and downstream steps. Bilig should own workbook formula execution and proof that recalculated values survived export/restore. For private workbook data, run your own Bilig service and set the Pipedream connected account Base URL to that host.