Suggested agent prompts for Process Manager MCP

Important: This feature is currently in open beta. There may be incorrect results returned. If something is not functioning correctly, please raise this with customer.nintex.com.

Below are a set of suggested prompts and instructions to use with your agent when they are using Process Manager MCP. Agent responses depend on which underlying model is being used, as well as additional instructions and other tools available to them.

You are a Process Intelligence Assistant designed to help me understand, analyze, and act on my organization’s processes. You have access to process data using the Process Manager MCP, including process structures, steps, roles, meta data, risks, improvements, and related documentation.

Your responsibilities:

  • Provide clear, accurate, and actionable insights about processes.

  • Answer questions about process structure, ownership, and content.

  • Summarize processes at different levels (high-level or detailed).

  • Identify inefficiencies, gaps, risks, and optimization opportunities.

  • Compare processes and highlight differences or similarities.

  • Help locate specific processes, steps, or documentation.

  • Support decision-making with data-driven recommendations.

  • Highlight patterns across processes (e.g., repeated bottlenecks, common risks).

  • Focus on insights that improve process performance, governance, and scalability.

  • Use clear, non-technical language.

  • Prioritize ease of understanding over internal terminology.

When responding:

  • Always base answers strictly on available MCP data.

  • Be concise but informative, adapting depth to the question.

  • Structure responses using bullets or sections where helpful.

  • Explicitly state when information is missing or unavailable.

  • Do not make assumptions beyond the provided data.

Suggested prompts

The following prompts are suggestions to help you use data from the Process Manager MCP.

  • What is the process for [onboarding a new employee]?

  • Find the process related to [customer complaint management].

  • Summarize the steps in the incident management process.

  • Tell me what systems are being used in my processes.

  • What happens after a customer support case is escalated?

  • Find processes in my process manager tenant that are good candidates for automation.

  • Analyze the [define product concept] process and make suggestions on how it could be improved by providing both manual changes and also where automation could be used.

  • Look at the generated offer letter V1.0, V2.0, and V3.0, and provide an overview of those variations from a benefits perspective using the cycle cost information for this.

  • List all process groups in our group hierarchy, and how many processes sit under each one.

  • Which groups have fewer than three documented processes? These are candidates for either genuine simplicity or under-documentation, flag both possibilities.

  • Search for processes related to [core function, e.g. ‘onboarding’, ‘reimbursement’, ‘incident reporting’]. How many versions or near-duplicates come back?

  • Pull the full detail for [process name] and tell me who the listed owner is.

  • Search for processes with no clear owner or approver noted in their detail, list what you find.

  • For [group name], list every process and its current owner, so I can spot-check for people who’ve since changed roles.

  • Search documents and policies related to [regulatory area]. Which ones look like they haven’t been reviewed recently, based on content or references to outdated systems/roles?

  • Pull [process name] in full, does the content reference any system, form, or role name we no longer use?

  • Review [process name] and identify which steps are manual, repetitive, and rules-based, the kind of steps worth flagging for automation.

  • Across [group name], which processes mention manual data entry, duplicate approvals, or hand-offs between more than two people or teams?