Nintex vs C TWO (2026)

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

C TWO builds no robots or agents of its own and works through the platforms a customer already owns, naming UiPath, SS&C Blue Prism, Automation Anywhere and Microsoft Power Automate beside custom AI agents and direct API calls. It acts inside them, starting, stopping and restarting processes, moving work between resources and, through the Bot Agent on each robot machine, rebooting a frozen or offline machine before resuming the work.

Its connector for Power Automate, Power Apps, Logic Apps and Copilot Studio runs both ways, so a flow starts when C TWO dispatches a session, and those platforms can create, lock, retry and defer items in C TWO's queues. Incidents open tickets in the customer's support tools. Beyond those four platforms, which others C TWO supports is shared with customers only.

Sourcectwo.com/amp/universal-orchestration, the C TWO Microsoft Marketplace listing, the C TWO Bot Agent post and the Microsoft Learn C TWO connector referenceread 2026-10-12

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 and is not replaced by it.

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

Universal Orchestration routes every work item on its own to whichever robot, AI agent, API, Power Automate flow, virtual machine or person fits best on live performance, availability, cost and SLA pressure, and reroutes it as conditions change.

Universal queues give each item a known state, priority and deadline, with custom states a team defines, and items can be locked, retried as a new attempt or deferred to a set time. When a step fails, the platform recovers it and moves the work elsewhere, and governance rules apply SLA priorities, security requirements and operational limits across every process. How a robot or agent carries out its step stays in the platform that runs it, since C TWO decides who does the work and when.

Sourcectwo.com/amp/universal-orchestration, ctwo.com/solutions-universal-orchestration and the Microsoft Learn C TWO connector referenceread 2026-10-12

Entry points exist 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 claimed but not specified.

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

Work starts on events and service levels, not a fixed timetable. Runs fire from API calls, time, Power Automate and human input, and the prioritization engine starts and stops processes to protect each deadline as volumes and priorities shift.

Outside systems add work by creating items in a universal queue through the API or the Power Automate connector, and a C TWO task exposed as a flow starts a Power Automate flow whenever C TWO dispatches a session.

Failures start their own path, so a frozen or offline machine, a terminated process or a session running too long sets off recovery, and a problem that persists raises an alert and bars the process from taking more work. Planned downtime moves work to other resources on its own.

Sourcectwo.com/amp/universal-orchestration, ctwo.com/amp/autonomous-operations and the Microsoft Learn C TWO connector referenceread 2026-10-12

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. There is no stated retrieval layer, index, vector store or citation surface, and nothing published says which sources can be indexed, refreshed and permissioned or which documents influenced an output. The one route from an assistant into that process knowledge is the Process Manager MCP connector.

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

C TWO holds operational data, not documents. Universal queues, item states, credentials, governance rules and execution history drive its routing, forecasting and reporting, and its process intelligence reads that telemetry to flag SLA risks and likely failures before they land. A customer has nowhere in C TWO to load documents for an agent to search, so any grounding belongs to the AI agents C TWO routes work to, which the customer builds elsewhere.

Sourcectwo.com/amp/real-time-intelligence and ctwo.com/amp/autonomous-operationsread 2026-10-12

State lives in the process, not in the agent. Orchestration runs 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. There is no stated agent memory, shared context store or retention of context between runs, and no surface for viewing or clearing what an agent retains.

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

What C TWO keeps is the record of the work. Each queue item carries its data, tags, attachments, item logs and every attempt, a retry resets the data to its original value under a new attempt, and history stays available for compliance and reporting. An agent picking up an item gets that item's data, and anything it remembers between items lives in the agent's own platform.

SourceMicrosoft Learn C TWO connector reference and ctwo.com/amp/enterprise-governance; learn.microsoft.com/en-us/connectors/ctworead 2026-10-12

Oversight is built around the deterministic layer. Agents route, reason and adjust in real time with humans in control, orchestration coordinates agents with human decision-makers inside governed processes, and 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 a step in the surrounding workflow, not a review and approve gate on what the agent itself proposes, and there is no published policy check on agent behavior before execution.

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

People share the queues with robots and agents, so a work item can be routed to a person as its handler. When a robot or flow needs help, it opens a human in the loop form in C TWO with a title, an introduction, the fields to fill and a deadline, tied to the work item, and assigns it to a user, who completes it before the digital worker carries on. Forms can be reassigned and searched by status, policies block unauthorized actions before they run, a process that keeps failing is barred from taking work until someone steps in, and every approval is logged.

SourceMicrosoft Learn C TWO connector reference, ctwo.com/amp/enterprise-governance and ctwo.com/amp/universal-orchestration; learn.microsoft.com/en-us/connectors/ctworead 2026-10-12

SOC 2 Type 2 and SOC 3 reports are published for Nintex Workflow, Process Manager, DocGen for Salesforce and eSign, and FedRAMP Moderate covers Nintex Automation GE, the edition that runs Workflow and DocGen for Salesforce in a government only cloud for public sector agencies and their contractors. The customer-facing controls include 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.

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

C TWO has held SOC 2 Type II since 2024. Access to the platform is role based, and a central store holds every robot, agent and system credential with rotation and an audit of its use. Policies enforce security requirements and operational limits across every process and block unauthorized actions before they run. Whether staff can sign in through the company's own identity provider is not public.

Sourcectwo.com/amp/enterprise-governance, ctwo.com/amp/autonomous-operations and the 2024 C TWO SOC 2 Type 2 announcementread 2026-10-12

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

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

Every action, change, execution, escalation and exception is logged across technologies, so each process and task carries an end to end trail, and flows write their own session and item logs into C TWO as they run.

Live session telemetry and SLA tracking sit beside a real time digital twin of how work moves across robots, APIs, AI agents and people, with throughput, success and failure rates and average handling time for every process. Hundreds of prebuilt dashboards can be tailored by audience, exported as CSV or PDF or sent by email on a schedule. What an agent reasoned inside its own platform stays in that platform's logs.

Sourcectwo.com/amp/enterprise-governance, ctwo.com/amp/real-time-intelligence and the Microsoft Learn C TWO connector referenceread 2026-10-12

Nintex offers two delivery models. 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, and Nintex's own news and roadmap show continued investment in it.

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

A customer runs C TWO in C TWO Cloud, on a C TWO hosted address, or on its own servers on premises, and each tenant's API is addressed by division in both shapes. The Bot Agent on each robot machine reaches the platform over outbound connections only, so robots in the cloud or on premises need no inbound firewall rules, and C TWO supports high availability for large estates. C TWO Cloud's hosting region is not public.

SourceMicrosoft Learn C TWO connector reference, the C TWO Bot Agent post and ctwo.com/amp/autonomous-operations; learn.microsoft.com/en-us/connectors/ctworead 2026-10-12

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, with 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 and not rebuilt.

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

C TWO ships orchestration, governance and intelligence as one platform, and the working parts are the customer's own, such as SLA requirements per process, governance rules, queue states and underperformance profiles. The reporting comes with hundreds of prebuilt dashboards. Beyond those dashboards, a team sets C TWO up from its own processes, with no ready made agents or automations to switch on.

Sourcectwo.com/amp, ctwo.com/amp/real-time-intelligence and the Microsoft Learn C TWO connector referenceread 2026-10-12

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

C TWO chooses which worker handles an item, and when that worker is an AI agent, the agent runs on whatever model its own platform uses. C TWO's prioritization and forecasting models are unnamed, and a customer cannot pick or swap the model behind them.

Sourcectwo.com/amp and ctwo.com/amp/autonomous-operationsread 2026-10-12

Nintex ships an MCP server for Process Manager that an external assistant can connect to. A customer pastes the MCP URL into a custom connector and authenticates, either per user or once centrally by an owner for the whole organization, or registers 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 and does not run by default.

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

C TWO exposes a REST API on each customer's own host, addressed by division, with bearer token authentication through service account tokens for production and personal access tokens for testing, both issued in the product and shown once. C TWO's own connector for Power Automate, Power Apps, Logic Apps and Copilot Studio, in preview, covers session triggers, completion and failure reporting, session logs, timeouts and graceful stop checks, universal queue items, states, tags and attachments, and human in the loop forms. The wider API reference sits in a knowledge base open only to customers.

Sourcelearn.microsoft.com/en-us/connectors/ctwo, the C TWO connector referenceread 2026-10-12

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. There is no stated testing of agents with fixtures, mocks or datasets before production, no scoring of output quality over time, and no test set, simulation or scoring surface.

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

C TWO measures operations as they run. Cross technology value reporting compares the cost and performance of RPA, APIs, AI agents and Power Automate, the Optimization Center points out inefficiencies with suggested improvements, and predictive intelligence flags SLA risks and likely failures before they hit. A team can see which kind of worker handles a process best, but a change to an SLA, routing rule or governance policy goes live without a test run first.

Sourcectwo.com/amp/real-time-intelligence and the C TWO new product features postread 2026-10-12

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. So the bots control a real interface directly.

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

The robots C TWO manages click and type through screens, and C TWO itself does not. It dispatches, watches and recovers those workers, and the Bot Agent on each machine reboots it and reports on virtual desktop performance and the processes and applications running, all through system controls. When a screen change breaks a robot, C TWO notices, reports and reroutes the work.

SourceC TWO Bot Agent post and ctwo.com/amp/autonomous-operations; ctwo.com/blog/c-two-bot-agent-secure-and-seamless-bot-managementread 2026-10-12