Nintex Workflow

Name: Nintex Workflow
Brand: Nintex
Rating: 4.2 (2198 reviews)

We help businesses power endless possibilities.

Est 2006|Valuation $460M|Raised $21M

LinkedIn 61K|Website|Web traffic 61K|FTEs 1,179|HQ Bellevue, Washington, US

MarketsBusiness Process Management (BPM)Workflow Automation Agent Builder Platforms

Published Oct 2, 2026

01Common complaints

(Required) Consider alternative solutions when: 1. The organization's workflows are mostly simple M365 automations (approvals, notifications, file routing) and existing Microsoft licensing covers the needs: Microsoft Power Automate may be sufficient and more cost-effective. 2. The organization requires highly predictable, transparent pricing with minimal negotiation: vendors with clear per-user or flat platform tiers may be easier to budget. 3. The organization operates SharePoint on‑prem with frequent cumulative updates and limited administrative bandwidth: community reports indicate workflow regressions can occur after some updates, which may require manual fixes. 4. The organization requires developer-centric orchestration with BPMN/DMN and code-level control: platforms like Camunda may be better suited. 5. The organization is actively trying to reduce tool sprawl and has standardized on the Microsoft Power Platform: adding another automation vendor can increase platform overlap and operational complexity.

Deal disqualifiers (poor fit)

The organization only needs a very small number of simple workflows and prefers simpler, lower-cost licensing.
The organization is highly sensitive to vendor lock-in and requires open-standards portability (BPMN/DMN) without significant migration effort.
The environment is heavily impacted by SharePoint on-prem patching cycles and the organization lacks bandwidth for periodic troubleshooting after updates.

Release/change-management risk

Reviews and community threads indicate that updates can sometimes change behavior and require troubleshooting.

SharePoint on‑prem considerations

Community reports describe instances of workflow failures after SharePoint cumulative updates, with some requiring manual remediation or specific configuration changes.

Feature gating and tiering

Release notes and product materials indicate new AI features, connectors, and advanced admin features may be restricted to higher tiers or beta programs. Buyers should validate which features are included in the contracted tier.

Security/compliance transparency gaps

While SOC reports are referenced in vendor materials, many detailed security artifacts are available by request rather than published publicly. If procurement requires public attestations or certificates, plan to initiate a formal security review early in the process.

02Why they buy

Observed from customer feedback and product capabilities

Usability for workflow/forms building: Several customer reviews note the menu/layout structure and the platform's ability to support routine process automation without extensive developer involvement.
SharePoint heritage: Community commentary indicates historical strength for SharePoint-based workflows and forms, especially in older on‑prem contexts.

Differentiation details

Integrated capabilities across workflow, forms, document generation, and process management may be of interest to organizations seeking a single vendor for these functions.
Administrative and governance features (e.g., publishing approvals, granular permissions, identity sync) are present in product materials and release notes.

Areas where competitors have clear advantages

Power Automate: native Microsoft integration and clearer public pricing.
Kissflow: simpler commercial packaging and potentially faster adoption for some non-SharePoint-centric teams.

Why customers chose Nintex (recurring reasons)

Across review sources and community commentary, customers commonly cited:

Historical strength for SharePoint-based list/library workflows.
A visual, low-code workflow designer and forms tooling enabling faster delivery than custom development in many scenarios.
A broad suite of modules (workflow, forms, document generation, analytics, RPA) available from the same vendor.

03Field reports

Review-platform sentiment (high level)

- **G2:** A G2 product page snapshot showed an average rating in the four-star range based on a large volume of reviews during the period reviewed; G2’s category placement characterized Nintex as a contender in no-code development platform categories. Interpret placement cautiously because methodologies vary by analyst/review site. - **TrustRadius:** TrustRadius listed a favorable score within its scale and included narrative comments highlighting flexibility, UI, and scalability. - **Capterra:** Capterra listings showed generally positive average ratings in the four-star range with both positive comments (deployment speed, usability) and negative comments (breakages after updates, maintenance overhead, pricing concerns). - **PeerSpot:** PeerSpot summaries highlighted areas for improvement including UI, reporting/logging, performance with complex workflows, and licensing costs.

Representative sentiment and excerpts (paraphrased)

- Multiple Capterra reviews praised the user interface layout and structure and noted the platform's effectiveness for automating routine business processes. - Some Capterra and community reviews reported occasional breakages after updates and operational burdens for high-volume SharePoint workflows (for example, the need to manage workflow history lists and related data). - Several reviews mentioned pricing increases or licensing model changes as a reason for evaluating alternatives. - Peer community threads included instances where administrators reported challenges during SharePoint cumulative updates and mixed experiences with vendor support responsiveness.

Why some customers leave (recurring reasons)

Pricing increases and licensing model changes (for example, shifts from one licensing basis to another).
Breakages after platform or upstream updates (for example, SharePoint cumulative updates) and related troubleshooting burdens.
Microsoft-native capabilities (Power Platform improvements) reducing perceived ROI for simpler workflows.

Forrester TEI (vendor-commissioned)

Nintex publishes a Forrester Total Economic Impact (TEI) report for its workflow platform. - **Strength:** TEI reports can help build a benefits framework and identify cost categories relevant to procurement. - **Limitations:** TEI studies are typically commissioned by the vendor and use modeled assumptions for a composite organization. Buyers should treat ROI, payback, and productivity assumptions as directional and validate them against their own baseline metrics.

Vendor collateral and buyer guides

Vendor buyer guides and platform brochures are useful for feature discovery but should be validated against:

Specific connector and integration requirements
Governance and administrative processes
Admin overhead and lifecycle management needs
The actual licensing terms applicable in a contract

04Best fit

Company sizes

Mid-market to enterprise — typically larger organizations where automation is being implemented as a platform initiative.
Smaller organizations can be a fit if they have heavy SharePoint reliance and sufficient workflow volume to justify platform overhead.

Strong-fit industries

Based on vendor marketing and industry review distributions:

Government / public sector
Financial services
Manufacturing
IT services
Regulated and document-heavy workflows (HR / legal / contracting)

Roles and personas

Decision makers: CIO/IT Director, Head of Business Applications, Process Excellence leader, VP Operations.
Champions: SharePoint/M365 administrators, automation COE leads, business analysts.
End users: approvers, frontline managers, HR/finance operations staff.

Qualification criteria (good fit)

The organization requires governed automation across departments with auditability.
There is an existing Nintex footprint (forms/workflows/docgen) and a preference to modernize rather than replace.
The organization has resources for platform administration and lifecycle governance.

05The pitch

What the product does (core value proposition)

Nintex Workflow is a low-code/no-code workflow automation product (part of the broader Nintex platform) focused on building, running, and governing business process automations across common enterprise systems (notably Microsoft 365/SharePoint, but also broader SaaS and on‑prem via connectors and gateways). The product functions as a governed orchestration layer for approvals, routing, data capture, document generation, and integrations. It is positioned as an alternative to custom development intended for business users to implement operational workflows without coding. Vendor messaging references "agentic business orchestration" and includes AI-assisted building and operations features (e.g., AI actions/connectors and "assistant" capabilities). Official materials describe the platform as combining process intelligence, workflow orchestration, and AI-assisted solution building within a governed environment. **Key official positioning:** The vendor frames Cloud Automation as combining process intelligence, workflow orchestration, and AI-assisted solution building within a governed platform.

Target market and market positioning

- **Primary buyers:** IT (workflow platform owners), operations excellence / process teams, and line-of-business automation leads. - **Primary users:** Non-developer business users (often called "citizen developers"), plus power users and administrators. - **Common environments:** Microsoft-centric organizations (SharePoint Online / Microsoft 365; also SharePoint Server for legacy/on‑prem), plus enterprises needing cross-system integration and governance. - **Positioning:** Mid-market to enterprise digital process automation (DPA) / workflow management, with adjacent modules for forms, document generation, RPA, process mapping/management, and analytics.

Get a comprehensive analysis of Nintex Workflow including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 2, 2026

01Common complaints

(Required)

Consider alternative solutions when:

The organization's workflows are mostly simple M365 automations (approvals, notifications, file routing) and existing Microsoft licensing covers the needs: Microsoft Power Automate may be sufficient and more cost-effective.
The organization requires highly predictable, transparent pricing with minimal negotiation: vendors with clear per-user or flat platform tiers may be easier to budget.
The organization operates SharePoint on‑prem with frequent cumulative updates and limited administrative bandwidth: community reports indicate workflow regressions can occur after some updates, which may require manual fixes.
The organization requires developer-centric orchestration with BPMN/DMN and code-level control: platforms like Camunda may be better suited.
The organization is actively trying to reduce tool sprawl and has standardized on the Microsoft Power Platform: adding another automation vendor can increase platform overlap and operational complexity.

Deal disqualifiers (poor fit)

The organization only needs a very small number of simple workflows and prefers simpler, lower-cost licensing.
The organization is highly sensitive to vendor lock-in and requires open-standards portability (BPMN/DMN) without significant migration effort.
The environment is heavily impacted by SharePoint on-prem patching cycles and the organization lacks bandwidth for periodic troubleshooting after updates.

Release/change-management risk

Reviews and community threads indicate that updates can sometimes change behavior and require troubleshooting.

SharePoint on‑prem considerations

Community reports describe instances of workflow failures after SharePoint cumulative updates, with some requiring manual remediation or specific configuration changes.

Feature gating and tiering

Release notes and product materials indicate new AI features, connectors, and advanced admin features may be restricted to higher tiers or beta programs. Buyers should validate which features are included in the contracted tier.

Security/compliance transparency gaps

While SOC reports are referenced in vendor materials, many detailed security artifacts are available by request rather than published publicly. If procurement requires public attestations or certificates, plan to initiate a formal security review early in the process.

02Why they buy

Observed from customer feedback and product capabilities

Usability for workflow/forms building: Several customer reviews note the menu/layout structure and the platform's ability to support routine process automation without extensive developer involvement.
SharePoint heritage: Community commentary indicates historical strength for SharePoint-based workflows and forms, especially in older on‑prem contexts.

Differentiation details

Integrated capabilities across workflow, forms, document generation, and process management may be of interest to organizations seeking a single vendor for these functions.
Administrative and governance features (e.g., publishing approvals, granular permissions, identity sync) are present in product materials and release notes.

Areas where competitors have clear advantages

Power Automate: native Microsoft integration and clearer public pricing.
Kissflow: simpler commercial packaging and potentially faster adoption for some non-SharePoint-centric teams.

Why customers chose Nintex (recurring reasons)

Across review sources and community commentary, customers commonly cited:

Historical strength for SharePoint-based list/library workflows.
A visual, low-code workflow designer and forms tooling enabling faster delivery than custom development in many scenarios.
A broad suite of modules (workflow, forms, document generation, analytics, RPA) available from the same vendor.

03Field reports

Review-platform sentiment (high level)

G2: A G2 product page snapshot showed an average rating in the four-star range based on a large volume of reviews during the period reviewed; G2’s category placement characterized Nintex as a contender in no-code development platform categories. Interpret placement cautiously because methodologies vary by analyst/review site.
TrustRadius: TrustRadius listed a favorable score within its scale and included narrative comments highlighting flexibility, UI, and scalability.
Capterra: Capterra listings showed generally positive average ratings in the four-star range with both positive comments (deployment speed, usability) and negative comments (breakages after updates, maintenance overhead, pricing concerns).
PeerSpot: PeerSpot summaries highlighted areas for improvement including UI, reporting/logging, performance with complex workflows, and licensing costs.

Representative sentiment and excerpts (paraphrased)

Multiple Capterra reviews praised the user interface layout and structure and noted the platform's effectiveness for automating routine business processes.
Some Capterra and community reviews reported occasional breakages after updates and operational burdens for high-volume SharePoint workflows (for example, the need to manage workflow history lists and related data).
Several reviews mentioned pricing increases or licensing model changes as a reason for evaluating alternatives.
Peer community threads included instances where administrators reported challenges during SharePoint cumulative updates and mixed experiences with vendor support responsiveness.

Why some customers leave (recurring reasons)

Pricing increases and licensing model changes (for example, shifts from one licensing basis to another).
Breakages after platform or upstream updates (for example, SharePoint cumulative updates) and related troubleshooting burdens.
Microsoft-native capabilities (Power Platform improvements) reducing perceived ROI for simpler workflows.

Forrester TEI (vendor-commissioned)

Nintex publishes a Forrester Total Economic Impact (TEI) report for its workflow platform.

Strength: TEI reports can help build a benefits framework and identify cost categories relevant to procurement.
Limitations: TEI studies are typically commissioned by the vendor and use modeled assumptions for a composite organization. Buyers should treat ROI, payback, and productivity assumptions as directional and validate them against their own baseline metrics.

Vendor collateral and buyer guides

Vendor buyer guides and platform brochures are useful for feature discovery but should be validated against:

Specific connector and integration requirements
Governance and administrative processes
Admin overhead and lifecycle management needs
The actual licensing terms applicable in a contract

04Best fit

Company sizes

Mid-market to enterprise — typically larger organizations where automation is being implemented as a platform initiative.
Smaller organizations can be a fit if they have heavy SharePoint reliance and sufficient workflow volume to justify platform overhead.

Strong-fit industries

Based on vendor marketing and industry review distributions:

Government / public sector
Financial services
Manufacturing
IT services
Regulated and document-heavy workflows (HR / legal / contracting)

Roles and personas

Decision makers: CIO/IT Director, Head of Business Applications, Process Excellence leader, VP Operations.
Champions: SharePoint/M365 administrators, automation COE leads, business analysts.
End users: approvers, frontline managers, HR/finance operations staff.

Qualification criteria (good fit)

The organization requires governed automation across departments with auditability.
There is an existing Nintex footprint (forms/workflows/docgen) and a preference to modernize rather than replace.
The organization has resources for platform administration and lifecycle governance.

05The pitch

What the product does (core value proposition)

Vendor messaging references "agentic business orchestration" and includes AI-assisted building and operations features (e.g., AI actions/connectors and "assistant" capabilities). Official materials describe the platform as combining process intelligence, workflow orchestration, and AI-assisted solution building within a governed environment.

Key official positioning: The vendor frames Cloud Automation as combining process intelligence, workflow orchestration, and AI-assisted solution building within a governed platform.

Target market and market positioning

Primary buyers: IT (workflow platform owners), operations excellence / process teams, and line-of-business automation leads.
Primary users: Non-developer business users (often called "citizen developers"), plus power users and administrators.
Common environments: Microsoft-centric organizations (SharePoint Online / Microsoft 365; also SharePoint Server for legacy/on‑prem), plus enterprises needing cross-system integration and governance.
Positioning: Mid-market to enterprise digital process automation (DPA) / workflow management, with adjacent modules for forms, document generation, RPA, process mapping/management, and analytics.

Get a comprehensive analysis of Nintex Workflow including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →