Stage 12 · Click to deploy

Deployment control center

Push the certified TO-BE workflows directly into the customer's operating system. Each integration generates the schema + workflow payload and pushes via the provider API.

Approved SOPs · ready to deploy
Loading…
Available targets
Henry (Ask Henry)
Live

Push approved SOPs as workflows + tasks into a Henry tenant. The fastest path — no ERP required, AI handles the steps.

Henry tenant must be subscribed and the customer must have a Henry API key.

NetSuite
Coming soon

Generates SuiteScript + custom-field migrations + workflow XML mapped from the BPMN swimlanes and the SOP step systems.

Customer authenticates via OAuth; we generate the bundle and hand it to their NetSuite admin to apply.

Odoo
Coming soon

XML-based workflow + custom-field push via Odoo XML-RPC. Same shape as the NetSuite path, different schema mapper.

Salesforce
Coming soon

Approval-process + custom-field metadata generation via the Metadata API. Operator deploys via SFDX.

Google Workspace
Coming soon

Auto-generates a structured Google Sheet with Apps Script macros enforcing data validation + approval routing — for transitional clients without an ERP.

How click-to-deploy works:The system reads the approved SOP's sop_json(steps + roles + systems) and the BPMN swimlanes, translates them into the target platform's schema (workflow XML, custom fields, approval routing rules), and pushes via the provider API. The operator reviews the payload preview before authorising the push so nothing lands in production blind.