Migrating from Nintex approvals to DueReason
Nintex gates a process with an Assign a task approval step inside a bigger cloud-and-on-prem automation platform. See what a signed, verifiable grant changes.
Updated · 9 min read
In short
- Nintex is an enterprise process automation/orchestration platform, available as cloud (Nintex Automation Cloud) or on-premises, with approvals as one capability among many rather than its core product.
- Its **Assign a task** action pauses a workflow for an express-approval or form-based response, then resumes the workflow with the outcome - the same "the workflow just continues" shape [the Power Automate migration guide](guide:migrating-from-power-automate) describes for a cloud flow's own approval step.
- Nintex is also the one named competitor here with a genuinely comparable self-hosted deployment model - an on-premises license, at enterprise, custom/quote pricing - which is exactly where DueReason's own self-host path is the direct, far simpler alternative.
- What changes moving a task over is what happens after someone responds: a signed, single-use grant bound to the exact payload, verified before anything acts on it, recorded on a hash-chained ledger from the start.
If an approval step in your organization lives inside a Nintex workflow, it almost certainly runs through the Assign a task action - available whether that workflow runs in Nintex's cloud product or on your own servers. This walks through what that action does today, and what changes if you move just the approval step to @duereason/sdk.
What Nintex does today
Nintex is a broad process automation and orchestration platform: workflows are built from a library of actions - data lookups, document generation, integrations with SharePoint, Salesforce and dozens of other systems - with approval as one action type among many rather than a dedicated product. Add an Assign a task action (or Assign a task to multiple users for more than one approver) and the workflow pauses until the assigned person responds, using either an "express approval" task type with outcomes you define (typically Approve/Reject) or a form-based task that collects more than a yes/no. Nintex ships in two deployment shapes: Nintex Automation Cloud, and an on-premises install for organizations that keep workflow execution inside their own infrastructure - a hybrid path Nintex itself has offered SharePoint on-premises customers since 2021. Nintex does not publish a public per-seat price list; quotes are custom to the deployment and module mix, so any specific figure - third parties have reported ranges anywhere from roughly $15,000 to $40,000 a year for a small cloud deployment, climbing into six figures for larger enterprise rollouts - should be treated as [UNVERIFIED] until quoted directly for your organization.
That breadth is also why a Nintex approval task is a feature of the workflow engine rather than a decision with its own identity: it is one action type a workflow can include, built to fit whatever process you modeled, not an object with a signature or a lifecycle independent of the workflow instance that contains it.
What happens after a task is approved
Nintex's own documentation describes the assigned task completing with an outcome - the task object variable the workflow can then reference - and the workflow resuming from there, continuing to whatever action runs next: an email, a status update, a write back to SharePoint or another connected system. It does not describe a signed or otherwise independently verifiable object the next action checks before it runs: whoever built the workflow is trusted to have wired the right action after the task, and the task and the action that follows it share the same trust boundary inside the same workflow instance. That is the same shape the Power Automate migration guide describes for "Start and wait for an approval," and the same gap the Kissflow migration guide describes for an approval step inside a low-code BPM process.
The same shape in DueReason
Nintex's workflows are general-purpose, so no single DueReason template replaces a whole workflow - DueReason answers the approval question one task asks, not the orchestration around it. Map the task, not the workflow: a task that gates spend, access or a vendor relationship has a close match in Payments and refunds, Access requests or Vendor onboarding from Settings → Templates; for a task with no close template match, a custom DueReason action models the same approve/reject question with its own approver group in place of the task's assignees, and its own evidence field in place of whatever the form-based task type collected.
Whichever action models the task, once a request is decided DueReason issues a signed, single-use grant bound to the exact payload - the amount, the recipient, the change being requested - which whatever runs next verifies, rather than trusting that a task object variable says "approved" inside the right workflow instance.
What changes, not just what moves
- A grant the acting system checks, not a task outcome trusted at the source. DueReason's signed grant is bound to a hash of the exact payload and verified by whatever executes the decision, so a changed amount or target after approval is refused rather than carried out because a task happened to complete with the right outcome.
- A hash-chained ledger, not a workflow's own history log. Every step of a request - filed, each answer, what happened after - is a ledger event from the start, checkable on its own without opening the workflow instance that hosted the task.
- A self-host path built for one organization, not an enterprise on-premises license. Nintex's on-premises deployment is the one named competitor here with a genuinely comparable self-hosted model, but it is sold as a custom-quoted enterprise license. DueReason self-hosts as one pre-built image and one Postgres database started with Docker Compose - free for one organization with up to five members, all core features included, with a yearly Ed25519-signed license key, verified entirely offline, lifting those limits rather than gating access to the product at all.
- An agent-native surface, not a workflow that only advances when its own engine runs the next action. The same actions are reachable from
@duereason/sdk, the MCP server, the GitHub Action or the REST API, so a script, a pipeline or an agent canrequestApproval()andwaitForApproval()without a Nintex workflow instance involved at all.
Moving one approval task over
- Pick the one Assign a task step you want to move - not the whole workflow - and find the closest DueReason template (Payments and refunds, Access requests, Vendor onboarding) or define a custom action if nothing close exists yet.
- Recreate the task's assignees as members of the action's approver group, and recreate whatever the form-based task type collected as the action's
reasonand evidence field. - For workflows started by hand today, the console request form replaces reaching the task: pick the action, attach whatever the form used to collect, write a reason.
- For workflows your integrations start automatically,
requestApproval()immediately followed bywaitForApproval()from@duereason/sdk(or the no-code webhook recipe if you would rather not write a backend) replace the point where the workflow reached the Assign a task action. - Replace whatever reads the task's outcome variable back into the rest of the workflow or a downstream connector with a check of
decided.statusand a verification ofdecided.grantbefore the action that actually acts - the system doing the work should check the grant, not just the task outcome.
What has no direct equivalent
DueReason has no workflow canvas, no action library for SharePoint, Salesforce or the dozens of other systems Nintex connects to, and no document-generation engine - it is not a Nintex replacement and does not try to be. If the real value you get from Nintex is the whole orchestrated process - the actions before and after the approval task, the connectors, the generated documents - keep Nintex for that and add DueReason around the one task that needs a signed, independently verifiable decision rather than expecting a native replacement for the orchestration engine itself. The Power Automate migration guide covers the same trade-off for a lighter-weight cloud-flow platform, if that is the comparison you are also making.
Questions
- Does Nintex's Assign a task action really have no verification step?
- Nintex's own documentation describes the task completing with an outcome available to the workflow as a task object variable, and the workflow resuming from there - it does not describe a signed or independently verifiable decision object the next action checks before it runs. Whoever built the workflow is trusted to have wired the right thing after the task.
- Can I keep my existing Nintex workflow and only replace the approval task?
- Yes. Call requestApproval() from an HTTP action (or a short script step) in place of Assign a task, and either poll the request or use the no-code webhook recipe to resume your workflow once approval.approved fires, so everything upstream and downstream in Nintex stays as it is.
- Nintex has an on-premises option like DueReason's self-host path - how do they actually compare?
- Both run on your own infrastructure, but Nintex's on-premises deployment is sold as a custom-quoted enterprise license with no public per-seat price list - [UNVERIFIED], third parties report small cloud deployments alone running $15,000-$40,000 a year. DueReason self-hosts as one pre-built image and one Postgres database behind Docker Compose, free for one organization with up to five members and all core features, with a yearly license key lifting those limits rather than gating the product.
- What does this cost, compared to Nintex?
- Nintex does not publish a public per-seat price list; quotes are custom to the deployment and module mix, so treat any figure you see as [UNVERIFIED] until quoted directly. DueReason is free today for one organization with up to five members, with all core features available; a yearly license key lifts those limits, verified entirely offline with no phone-home.
- Do I have to rebuild my whole workflow to move one approval task?
- No. DueReason answers one question - is this action approved, by whom, with what evidence - rather than orchestrating a process end to end, so a Nintex workflow that does other things with its action library, connectors or document generation can keep doing them; only the Assign a task step and whatever reads its outcome need to change.
Move one approval task to DueReason
Keep Nintex for the workflow around it - point requestApproval() and waitForApproval(), or the console request form, at the one task that needs a signed, verifiable decision.
Create your accountSources
- Nintex Help: Assign a task (express approval vs. form-based task types)
- Nintex Help: Assign a task to multiple users
- Nintex: on-premises strategy for SharePoint customers
- @duereason/sdk: requestApproval and waitForApproval reference
This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.