Nintex Automation Cloud
Evaluate a Nintex Automation Cloud export, review action mappings and dependencies, and separate generated output from the configuration and testing your team completes.
Free account required for your own analysis. Package generation depends on workflow support and your export allowance.
Export a workflow you understand from Nintex Automation Cloud. Export-based analysis reads that definition; it does not require a live NAC tenant connection. Review a copy for sensitive literal values before uploading it.
Review data handling before uploadingMake the scope explicit
Record what starts the workflow, its input values, variable defaults, and expected output. Check how the destination trigger and connections will be configured.
Review native and Xtension actions against the current compatibility reference. Database, API, custom form, and Nintex Tables behavior may need configuration or a different implementation.
Identify child workflows, approvals, loops, and expected run volume. Review the analysis findings before deciding whether to convert, split, or rebuild a pattern.
Choose one typical workflow with known inputs and outputs. Record the required settings, generated artifacts, manual changes, and test results before applying the approach to a larger set.
The public Cloud fixtures include three log actions mapped to Compose and an approval with outcome branches, a SharePoint write, and a counted loop. They have passed local artifact checks; live import and execution have not been performed.
Inspect the evidence and worksheetUse the analysis report, remaining-work list, pilot results, and current commercial terms to explain the proposed scope. The buyer’s brief brings those decisions together.
Share the buyer’s brief
