Agentic Business Orchestration

AI agents are great at getting work done. But once they're in production, a different question emerges: How do you know they're doing the right work, and doing it reliably? Think about a typical scenario: You've built a support ticket triage agentflow. A support request is submitted, an agent summarises, categorizes them, assigns priority, and another routes it to the right team. Everything works great during testing, so you publish it and make it available to your customers. A week later, the real questions start:  How often is the agentflow being used?  Is it completing successfully?  Are failures occurring?  Why did a specific ticket get routed incorrectly?  How many AI tokens is the agentflow consuming?  Answering these questions requires two capabilities: monitoring and observability.  Monitoring: Understanding agentflow activity and health Monitoring gives you a high-level view of how your Agentflow is performing over time. For a support ticket triage agentflow, you might wan

Bring AI-Powered Intelligence to Accounts Payable Finance teams spend countless hours reviewing invoices, reconciling purchase orders, and investigating exceptions before payments can be approved. While many organizations have automated parts of the process, invoice matching remains one of the most time-consuming and exception-heavy tasks within Accounts Payable.Today, we're excited to introduce the Invoice & Purchase Order Matching Agent, a new Nintex Agentflows gallery template that uses AI to streamline Invoice-to-PO matching and help finance teams reduce manual effort, lower processing costs, and accelerate payment workflows. Modernizing a Core Accounts Payable ProcessThe agent is designed to automate one of the most fundamental finance operations: comparing incoming invoices against purchase orders and detecting discrepancies for overcharges.  Using AI, the agent can analyze invoices and purchase orders, compare the information, and determine whether discrepancies require furt

Faster Triage, Smarter Escalation, Better Customer Outcomes Support and Service desk teams are under constant pressure to respond quickly, prioritize accurately, and identify high-risk customer issues before they escalate. But as ticket volumes grow, manually reviewing every case for urgency, emotional intensity, and business impact becomes increasingly difficult.That is why we are excited to introduce the Support Ticket Sentiment and Severity Agent, a new agent template designed to help teams analyze incoming support cases and tickets faster, more consistently, and with greater intelligence. The template uses Nintex Agentflows to analyze sentiment in support-reported cases and tickets, helping support teams triage requests more accurately and quickly.Helping support teams identify what needs attention firstThe mission of the Support Ticket Sentiment and Severity Agent is simple: help support teams identify the most urgent, high-risk, or emotionally distressed customers before a situat

Hello Nintex Community! 👋We're excited to announce that Agent Designer and Orchestration entered General Availability (GA) on July 13, 2026, as part of Nintex CE and Workflow. Together, these capabilities make it significantly easier to manage complexity, adapt to change, and scale automation.  🚀 What these unlock for you:Break down complex, monolithic workflows into coordinated, manageable phases with Orchestration Introduce AI agents that can execute tasks with real-time decisioning, with or without human input Reduce bottlenecks and maintain context across the full process lifecycle Gain a more flexible, scalable low-code foundation to evolve workflows and accelerate time to value  📍 Stay connectedThe Nintex Agent Designer and Nintex Orchestration forum sections remain your primary destination for all announcements, best practices, learning resources, and community support. Whether you're looking for the latest information or have questions, be sure to subscribe to receive notifi

As you start building your Nintex AI agents, the first step is knowing where to configure and manage them. All agent setup happens in Nintex Agent Designer, a dedicated experience where you define how your agent thinks, behaves, and interacts with tools and data.  For more details and instructions use any of the following resources:Nintex HelpConfigure an Agent blog  (by Andy Hayes)

Configuring an agent is one of the foundational steps in building effective Agentflows. In this short how-to video, you'll learn how to configure a single Agent Action and understand the key components that influence how an agent behaves, accesses information, and returns results.  Whether you're building your first AI-powered workflow or refining an existing Agentflow, this overview will help you understand the core configuration options available. What You'll LearnThis video provides a high-level walkthrough of:Adding an Agent Action to an Agentflow. Understanding the four key configuration areas: Model Tools Knowledge Output Selecting and configuring an AI model and connection. Adjusting model settings such as: Reasoning effort Temperature Defining the agent's: Role and rules Work request Adding and using tools to enable agent actions. Connecting agents to knowledge sources and document stores. Understanding shared context and external vector embeddings. Configuring user mes

A question that keeps coming up: when do I use an agent versus a workflow?It's exactly where most teams get tripped up when adopting AI. Here's a clean mental model and some practical guidance you can actually use.Summary: Use agents to interpret and choose. Use workflows to execute. Use both together for scale and safety. The Core Distinction  Agent Workflow Role Interprets, reasons, decides Executes, routes, enforces Best for Ambiguity, judgment, adaptation Precision, repeatability, governance Output A choice or recommendation A deterministic action  When to Use an AgentUse agent tools when human-like judgment, adaptation, decisioning or choosing can be a solution without needing a human in the loop and/or less effort to build.Signals:The path forward isn't known in advance Inputs are unstructured (emails, documents, messages) Decisions depend on nuance or context Multiple valid next steps exist The

Hi everyone! 👋If you've been hearing the word "Orchestration" floating around lately, today's the day. We're opening it up to all customers, and I wanted to give you a proper walkthrough before you dive in. So, what problem does it solve?Here's the honest truth about a lot of business processes: they don't behave the way flowcharts suggest they will.You build a workflow for employee onboarding, a customer claim, or a vendor approval. It works great, right up until reality intervenes. The case needs to go back a step. A new event changes the context. Two teams need to be working on different parts simultaneously.Before long, you're adding branches on branches, or spinning up a separate workflow to handle an exception that probably wasn't that exceptional.Orchestration is built for exactly this kind of process, and it's grounded in a case management approach.  What is case management?Case management is a way of thinking about work where the focus is on a single case moving through its l

For decades, organisations have pursued the same goal: reducing operational friction while improving efficiency, consistency, compliance, and visibility across business operations.What has changed over time is not the objective — but the technology used to achieve it.The journey from traditional Business Process Management (BPM), through Robotic Process Automation (RPA), and now into the emerging era of Agentic Process Automation represents one of the most significant shifts in automation technology in recent years.These technologies are not replacements for one another. They are evolutionary layers in a broader automation strategy.Platforms like Nintex have been uniquely positioned throughout this evolution — moving from workflow and forms automation into intelligent end-to-end process orchestration that now increasingly incorporates AI-driven decisioning and autonomous capabilities.The BPM Era: Structured Process OrchestrationTraditional BPM solutions emerged to address a fundamental

You are invited to join the weekly Agent and Orchestration Office Hours session focused on learning how to design, build, and operationalize AI agents.When? Weekly - Tuesdays 3:00 PM CT (Americas) / Wednesdays 8:00 AM AEDT (APAC)Where? Teams call: Join here!Each session will walk through a specific topic with a short demo and practical guidance you can apply immediately, such as:Build AI agents and understand when to use agents vs. simple actions Embed agents into workflows and orchestrations Design multi-agent solutions and master agents Connect agents to knowledge sources, tools, and external systems Implement guardrails, testing strategies, and human-in-the-loop patterns Deploy agents safely and monitor performance in productionThe office hours are designed to be interactive. Bring your questions, ideas, or scenarios you’d like help with.

AI is on everyone’s radar; the question is knowing where to start? The good news, you don’t need a massive overhaul to begin benefiting from AI. In fact, most companies find success by identifying just one clear use case and running a small instance or project. This introductory blog post – the first in our series on building AI agents for business applications – lays out practical best practices for getting started. We’ll explore why it’s smart to start with small, simple projects (think five steps or fewer), how to focus on straightforward, deterministic tasks for quick wins, and which high-impact, low-complexity use cases (like document processing, translation, or sentiment analysis) are perfect for early AI successes. Finally, we’ll discuss the importance of beginning at the department level and making AI a natural part of your design process. By focusing on clear, actionable steps and avoiding unnecessary complexity, you can dip your toes into AI confidently and set the stage for

Runtime AI brings AI-powered capabilities directly into the execution of a Nintex Workflow or App. Unlike design-time AI, which assists with building workflows, Runtime AI enhances how your live workflows operate by analyzing content, generating summaries, detecting entities, and making light, context-aware decisions as the workflow runs. Runtime AI Actions are lightweight, single-step automations that use large language models (LLMs) such as GPT and services like Azure Document Intelligence to perform specific content generation or analysis tasks. They are easy to configure and fit naturally into workflow execution, allowing you to add intelligence without complexity. All actions are delivered through the Runtime AI Platform Service and are accessible via API for integration across Nintex products. In this release, there are 11 out-of-the-box actions available in Nintex Workflow. VideosAnalyze sentiment Detect language Extract information from document or image Extract text from docum