Nintex

Orchestration spans the systems a process touches, with workflows moving data and triggering actions across the organization through connectors to Microsoft Teams, SharePoint and others, deep Microsoft ecosystem coverage through Nintex Workflow and Forms for Office 365, and DocGen for Salesforce and eSign as first-party integrated products.

Sourcenintex.com/platforms/cloud-automation/workflow-automationread 2026-09-17

Nintex Orchestration replaces the linear start-to-finish workflow with a modular phase-based model in which a process moves forward, jumps back and repeats steps as conditions demand without restarting, and it coordinates workflows, AI agents and human decision-makers in the same case-based execution, with agents routing, reasoning and adjusting in real time. The deterministic rules-based layer runs beside the probabilistic one in one platform rather than replacing it.

Sourcenintex.com/learn/agentic-business-orchestrationread 2026-09-17

The customer's own mapped and approved process documentation lives in Nintex Process Manager and is the body of knowledge agents operate against, and six prebuilt AI actions add document processing intelligence on top of it. No retrieval layer, index, vector store or citation surface is documented as a product capability, and nothing published says which sources can be indexed, refreshed and permissioned or which documents influenced an output. The one documented route from an assistant into that process knowledge is the Process Manager MCP connector.

Sourcenintex.com/learn/agentic-business-orchestrationread 2026-09-17

Oversight is built around the deterministic layer: Nintex states agents route, reason and adjust in real time with humans in control, that orchestration coordinates agents with human decision-makers inside governed processes, and that humans remain central for oversight, judgment and exception handling, with policies and role-based access embedded in every process.

A solution can combine forms, approval workflows and an agent as one unit. Approvals are documented as a step in the surrounding workflow rather than as a review and approve gate on what the agent itself proposes, and no policy check on agent behavior before execution is published.

Sourcenintex.com/learn/agentic-business-orchestrationread 2026-09-17

SOC 2 Type 2 and SOC 3 reports are published for Nintex Workflow, Process Manager, DocGen for Salesforce and eSign, and Nintex Workflow and DocGen for Salesforce hold FedRAMP Moderate authorization, listed on the FedRAMP Marketplace.

The customer-facing controls sit alongside them: privileged accounts held separately from primary domain accounts with mandatory multi-factor authentication, least-privilege access with change requests audit logged, role-based access embedded in every process, formal data classification tiers, static code scanning before every release, annual third-party penetration testing and OWASP Top 10 protections. These controls are documented in the Nintex Platform Security, Privacy and Organizational Overview, version 1.8 of 27 January 2026.

Sourcenintex.com/wp-content/uploads/2024/11/nintex-platform-security-privacy-organizational-overview.pdfread 2026-09-17

Policies, audit trails and role-based access are embedded into every process to maximize visibility and control, according to Nintex, and orchestration coordinates workflows, agents and human decision-makers within governed processes. Step by step inspection of prompts, tool calls, retrieved knowledge and outputs is not documented, and no agent reasoning trace, run level inspection view, retention term, export path or audit log kept apart from runtime traces is published.

Sourcenintex.com/learn/agentic-business-orchestrationread 2026-09-17

State lives in the process, not in the agent: orchestration is described as case-based execution that carries a process forward, back and around as conditions change, so what persists is the case record the platform already keeps. No agent memory, shared context store or retention of context between runs is documented, and no surface for viewing or clearing what an agent retains is described.

Sourcenintex.com/learn/agentic-business-orchestrationread 2026-09-17

Two delivery models are published. The cloud platform runs on Microsoft Azure with a per-product hosting region matrix spanning the United States, the European Union, the United Kingdom, Canada, Japan, Australia and the United Arab Emirates, with backups geo-replicated and encrypted at rest.

On-premises runs through Nintex K2, which gained built-in AI for the first time in 2026 alongside simplified identity management, marketed for organizations that need the workload to stay inside their own environment. A third-party forum comment had raised a possible K2 end-of-life; Nintex's own news and roadmap pages show continued investment in it.

Sourcenintex.com/news/nintex-debuts-new-on-premises-ai-simplifed-identity-management-nintex-k2read 2026-09-17

Six prebuilt AI actions for document processing shipped with the agentic launch, alongside an AI process generator and the packaged first-party products DocGen and eSign that drop into a process as ready-made components. From the Q3 2026 release, Nintex Solutions is the packaging unit: related workflows, forms, integrations, agents and documents bundled as one governed solution that a team deploys as a coherent whole and then reuses as a template, so a proven approval chain or intake process is picked up and used elsewhere rather than rebuilt.

Sourcenintex.com/blog/nintex-q3-2026-automation-ce-nintex-solutionsread 2026-09-17

Entry points are documented at the product level: attended bots are activated on demand by a person from the desktop, unattended bots operate independently with no human involvement and run processes around the clock, and forms, eSignature flows and workflow steps give human and system entry points across the platform. No schedule, webhook or event inventory for agents or bots is published, so the autonomous side is asserted rather than specified.

Sourcenintex.com/platforms/cloud-automation/rparead 2026-09-17

Built-in AI is marketed across the cloud platform and, since 2026, on premises through K2, and Nintex describes agents that reason and adjust in real time, but no model provider choice, model menu, routing configuration or bring-your-own-key capability is published, and no provider is named.

Sourcenintex.com/learn/agentic-business-orchestrationread 2026-09-17

Nintex ships an MCP server for Process Manager and documents connecting it from an external assistant: paste the MCP URL into a custom connector and authenticate, either per user or added once centrally by an owner for the whole organization, or register it as a Model Context Protocol tool in an agent's tools page with a server name and description the orchestrator uses to decide when to call it. Once added it is switched on per conversation rather than running by default.

Sourcenintex.com/blog/nintex-process-manager-mcp-ai-health-checkread 2026-09-17

Changes reach production through built-in application lifecycle management, which handles versioning and approvals: Nintex Solutions packages related assets, workflows, forms, integrations, agents and documents, into one governed unit that moves across environments in a single step, so a change is reviewed before it goes live. Testing agents with fixtures, mocks or datasets before production is not documented, nor is scoring output quality over time, and the product pages show no test set, simulation or scoring surface.

Sourcenintex.com/blog/nintex-q3-2026-automation-ce-nintex-solutionsread 2026-09-17

Nintex sells robotic process automation as a first-party product: patented machine learning and optical character recognition let the bots use applications the way a person would, in any software environment, with over two hundred advanced commands and a drag-and-drop bot designer that needs no code. Attended bots are activated on demand from the desktop to help with a task in progress, and unattended bots operate independently with no human involvement, running processes around the clock. That is documented control of a real interface rather than a lower-fidelity route to one.

Sourcenintex.com/platforms/cloud-automation/rparead 2026-09-17