Nintex · Process Automation · Salesforce

What Is Nintex? A Guide to Nintex Process Automation for Salesforce Teams

Nintex covers process mapping, workflows, forms, documents, e-signatures and bots on one platform, and much of it has been renamed since 2024. This guide explains what each part does in 2026, how a Nintex workflow runs, how Nintex connects to Salesforce, and when it is a better choice than Salesforce Flow.

Key Takeaways

  • Nintex is a low-code process automation platform. Its cloud platform is now called Nintex CE (Nintex Automation CE); the on-premises edition is Nintex Automation K2.
  • Several products were renamed: Promapp is Process Manager, AssureSign is Nintex eSign, and Skuid SFX is Nintex Apps for Salesforce. Forms are part of Nintex Workflow.
  • Every Nintex workflow is a start event followed by actions. Connections let those actions read and write data in Salesforce, SharePoint, Box and other systems.
  • For Salesforce teams, the two main pieces are the Salesforce connector in Nintex Workflow and Nintex DocGen for Salesforce, a managed package for document generation.
  • Salesforce Flow is usually enough for automation that stays inside Salesforce. Nintex earns its place when a process crosses several systems, needs mapped and governed procedures, or produces documents.

What is Nintex process automation? Nintex process automation means using the Nintex platform to map a business process, then automate it with workflows, forms, documents, e-signatures and software bots, mostly without code. Nintex sells it as a cloud platform, Nintex CE, and as a self-hosted product, Nintex Automation K2. Salesforce teams use it mainly to automate approvals and to generate documents from Salesforce data.

We first published this guide in 2024. This version is rebuilt from Nintex's current help documentation, product pages, 2026 announcements and its AppExchange listing, all checked in October 2026. It uses the current product names, keeps and corrects the workflow and My Nintex details from the original, and adds the Salesforce integration, a comparison with Salesforce Flow, the 2026 AI changes and a plan for getting started. It is written for operations leaders, Salesforce admins and IT teams at growing and mid-market companies who are deciding whether Nintex fits their processes, or who already own it and want more out of it.

Section 01 · Definition

What Is Nintex, and What Is It Used For?

Nintex is a low-code platform for automating business processes from start to finish. Teams use it to map how work is done, build workflows that route tasks and approvals, collect data with forms, generate documents and collect signatures, and use bots for systems without an API. Business users design workflows by drag and drop or from a prompt, and IT governs them.

Nintex describes its cloud platform, Nintex CE, as an "agentic business orchestration platform" that brings together process intelligence, workflow orchestration and AI-assisted solution building. In practice, most buyers use a few parts of it:

Workflows and approvals

Nintex Workflow routes tasks, approvals and notifications between people and systems, with forms to start a process or capture a decision.

Documents and signatures

DocGen for Salesforce and Nintex Documents build quotes, contracts and letters from live data; Nintex eSign collects the signatures.

Process management

Process Manager documents each process, its owner and its approvals, so the team automates the agreed way of working.

Section 02 · Products

Which Products Make Up Nintex in 2026?

The core is Nintex Workflow, which runs on the Nintex CE cloud platform, alongside Process Manager, RPA, document generation, eSign and app building. Several names changed after our original post. Nintex's help site now carries the notice that "Nintex Workflow is now part of the Nintex CE Platform", and the older "Nintex Workflow Cloud" and "Nintex Automation Cloud" names have gone from Nintex's current pages.

Product (2026 name)FormerlyWhat it does
Nintex CE (Nintex Automation CE)Nintex Automation Cloud, Nintex Workflow CloudThe multi-tenant cloud platform that holds the products below
Nintex WorkflowWorkflow automation; form automationWorkflows built from start events and actions, with start forms, task forms and approvals
Process ManagerNintex PromappProcess maps with owners, experts and change approvals; BPMN modelling; AI process capture and generation where licensed
Nintex RPA—Attended bots (started by a person) and unattended bots (running on their own), built in a drag-and-drop designer
Nintex DocGen for Salesforce—A Salesforce managed package that turns Salesforce records into Word, Excel, PowerPoint or PDF documents
Nintex Documents—Document generation inside Nintex CE, now with built-in signatures for up to five sequential signers
Nintex eSignNintex AssureSignElectronic signatures with reminders, tracking and an audit trail; can be sent from Salesforce
Nintex Apps for SalesforceSkuid SFXDrag-and-drop pages, portals and forms inside Salesforce
Nintex Automation K2Nintex K2The self-hosted edition on Windows and SQL Server, for organisations that need full control of their data

Sources: Nintex platforms, Nintex CE, Process Manager, Nintex RPA, Nintex eSign, Nintex Automation K2 and the Nintex Apps for Salesforce release notes. Our original post also listed "Form Automation" as a separate product. Nintex no longer presents it that way: forms are built and used inside Nintex Workflow.

Section 03 · Workflows

How Does a Nintex Workflow Work?

Every Nintex workflow is a start event followed by a series of actions that run one after another. The start event decides what launches the workflow, such as a submitted form, a schedule or a new Salesforce record. Actions then do the work: assign a task, send an email, branch on a condition, update a record or generate a document. A workflow does nothing until it is published.

Nintex workflow designer showing an Engineering Change Order workflow: a form start event, parallel branches that add a document to Google Drive, run an Azure function and create a Teams channel, then engineering and CAD review approvals with approved and rejected decision paths; the action toolbox on the left lists connectors such as DocuSign, SharePoint, Salesforce CRM and UiPath
A Nintex workflow in the designer: a form starts it, parallel branches run across several systems, and approvals decide the path. Interface labels in your tenant may differ.

The four building blocks

Building blockWhat it isExamples
Start eventWhat launches the workflowA form submission; a scheduled start in a chosen time zone; a component workflow called by another workflow or over HTTP; a connector event such as a new Salesforce record or a new SharePoint item; and, from 2026, an orchestration
ActionsThe steps the workflow runs, in sequenceCore actions (AI, communication, logic and flow, operations, collections, document generation, tables) and connector actions for other systems
ConnectionsStored credentials a connector action usesA Salesforce, Box or SharePoint account. Owners can edit and share a connection; users can only use it. A tenant can hold up to 1,000
VariablesValues the workflow stores and passes between stepsStart-event data such as form fields, task outcomes, instance details and the outputs of earlier actions

Nintex documents these in its help pages on creating a workflow, workflow start events, workflow actions, managing connections and workflow variables. You can build a workflow by dragging actions onto the canvas, or use "Start with AI" to generate a first draft from a description.

Forms and tasks

A form can be the start event, so submitting it launches the workflow, or it can sit inside a task, so an approver sees the request and records a decision. Nintex offers two task types, Express approval and Form-based. While a task is open, the workflow pauses until the assignee responds, as the help page on tasks explains.

Publishing, versions and auto-save

  • Draft and published. Saving keeps a draft. Changes to a published workflow take effect only when you publish again, and every action must be configured before publishing succeeds.
  • Versions. Each publish creates a new version, kept in the version history, so you can see what changed and when. The Workflows list is where you edit, pause, export and manage permissions.
  • Session expiry. A designer session ends after two hours of inactivity or when you close the browser tab, with a countdown message 15 minutes before. Unsaved workflow changes are saved automatically as a new version, but unsaved changes in the form designer are not, so save forms often. The details are on Nintex's workflows overview.
  • Moving between tenants. Workflows can be exported and imported, but connections, data lookups and component workflows do not travel with them, and imports arrive as drafts.
Section 04 · My Nintex

What Do Users See in My Nintex?

My Nintex is the participant portal where people fill in forms, act on their tasks and follow the workflows they started. Its dashboard shows recent tasks, submissions, favourite forms and drafts. What each person sees depends on their role in a workflow and on settings the workflow owner controls, and everyone needs Participant access to the Nintex CE tenant first.

The dashboard

Dashboard panelWhat it shows
Active tasksThe ten most recent active tasks assigned to you
Latest form submissionsThe five most recent forms you submitted
Favourite formsUp to ten are displayed; you can favourite up to 50 forms on the Forms page
Draft start forms and draft task formsForms saved but not submitted. Drafts are deleted 30 days after they are first saved

Selecting a task or form opens its activity feed, with its status, assignee or submitter, and task history. A submitted form can be resubmitted only if its status is Completed, Failed or Terminated, and only its latest submission, as described in Nintex's help pages on the My Nintex dashboard and form submissions. Administrators can also resubmit workflow instances, up to 50 at a time, and a resubmission always runs the latest published version.

Roles in My Nintex

RoleWhat they can see and do
Business ownerWorkflow tracking for the workflow: all its instances, start data and forms, and management of its tasks
Workflow initiatorThe instances they started and the progress of their tasks; the owner can widen or narrow this
Task assigneeThe instance behind each task assigned to them; more depends on the My Nintex settings

Each workflow has its own My Nintex settings, managed by its workflow owner, as set out in Nintex's My Nintex permissions page. Delegation is one of them: when the owner turns on "Delegate tasks", assignees and business owners can pass a task on, for tasks created by the "Assign a task to multiple users" action, to up to ten delegates.

Section 05 · Salesforce

How Does Nintex Work with Salesforce?

Through three products: the Salesforce connector in Nintex Workflow, Nintex DocGen for Salesforce, and Nintex Apps for Salesforce. The connector lets workflows start from Salesforce records and read or write Salesforce data. DocGen generates documents from Salesforce records inside Salesforce. Apps for Salesforce builds custom pages and portals. Nintex eSign then collects signatures on the documents.

Salesforce connector in Nintex Workflow

Cross-system workflows

Best for: processes that start in Salesforce but involve people or systems outside it.

Actions create, retrieve, update, delete and query Salesforce records, and attach or retrieve files. Two start events, "Salesforce - New record" and "Salesforce - Update record", launch a workflow when a record of a chosen object is created or a monitored field changes. Forms can also look up Salesforce records for drop-down lists. Nintex receives these events by polling Salesforce, so a workflow starts shortly after the change, not at the same moment.

  • API access. The connection needs a Salesforce org with API access, and the connecting user needs object and field permissions for every action, such as delete permission for "Delete a record".
  • Five connections per user. Salesforce allows each connected app five approvals per user. When a sixth connection is created for the same Salesforce user, the first one is revoked, so use a dedicated integration user rather than personal logins.
  • Token policy. Nintex recommends a refresh token policy of "valid until revoked", or expiry only after a period of non-use, so connections do not drop.
  • Avoid loops. If a workflow starts when a record is updated and also updates that record, Nintex advises separate connections with separate accounts for the start event and the action.

See Nintex's Salesforce connector and Salesforce new record start event pages.

Nintex DocGen for Salesforce

Documents from Salesforce data

Best for: quotes, proposals, contracts, invoices and letters generated from Salesforce records.

DocGen is a managed package on the Salesforce AppExchange. It works in Lightning, Classic, mobile and Experience Cloud, uses Word, Excel, PowerPoint or PDF templates, and can generate documents one at a time or in bulk. Each document type is set up as a DocGen Package in four steps: the Salesforce data it uses, the templates (always, optional or conditional), the delivery, and a test. Delivery can be Salesforce email, download, a Nintex workflow, SMTP, e-signature or a storage location, per Nintex's delivery options page.

  • Pricing. The AppExchange listing shows "Starting at $5,000/Company/Year", with discounts for nonprofits. Older per-user prices you may find online are out of date.
  • Connected app change. Following a Salesforce security change, Nintex required every DocGen for Salesforce customer to upgrade and move to the "Nintex DocGen for Salesforce Modern" connected app by 30 September 2026, warning that the app may stop working otherwise. If your org has not moved, do it now.
  • Upgrades. New package versions usually arrive monthly; Nintex recommends testing each one in a sandbox first.
  • Agentforce. The Nintex DocGen Agentforce Connector lets a user ask Agentforce to build a document; it confirms the template, generates the file and stores it on the record.

Nintex Apps for Salesforce and Nintex eSign

Interfaces and signatures

Best for: custom Salesforce pages and portals, and signatures collected without leaving Salesforce.

Nintex Apps for Salesforce builds pages, portals, guided forms and dashboards from more than 25 drag-and-drop components. Nintex eSign sends documents for signature directly from Salesforce, with reminders and status tracking, and DocGen can use it as a delivery option. Nintex's Salesforce page shows how the pieces fit together.

If documents are your main need, our Nintex DocGen for Salesforce services page covers templates, approval routing and delivery, and our Nintex integration services cover connections to Salesforce, Microsoft 365, ERP and other systems.

Section 06 · Comparison

Should You Use Nintex or Salesforce Flow?

Use Salesforce Flow when the process starts, runs and ends inside Salesforce. Consider Nintex when the process crosses several systems or many non-Salesforce users, needs documented and approved procedures, or produces complex documents. Many organisations use both: Flow for record logic inside Salesforce, and Nintex for the wider process around it.

Nintex is a good fit when… approvers, finance, HR or external parties work outside Salesforce; the process touches SharePoint, Box, ERP or legacy systems; documents and signatures are central; process owners need maps and change approval; or you want cloud and on-premises options.

Flow is usually enough when… every user is a Salesforce user, the logic reacts to record changes that must happen at once, and the output is an updated record, a task or an email. Adding Nintex there adds licences, a second tool to govern and a polling delay.

QuestionSalesforce FlowNintex
Where does it run?Inside SalesforceNintex CE cloud or self-hosted K2, connected to Salesforce
How does a Salesforce change start it?Record-triggered flows run inside Salesforce when the record is savedStart events detect new or updated records by polling
Who takes part?Salesforce usersAnyone with Nintex access, through forms, tasks and My Nintex
Other systemsThrough Salesforce's own integration features or custom workPrebuilt connectors such as SharePoint, Box, Google Drive, Dynamics CRM, Zendesk, and Nintex Gateway for on-premises systems
Documents and signaturesOutside Flow itself; usually a separate document appDocGen, Nintex Documents and eSign
Process documentationOutside Flow itselfProcess Manager

Salesforce describes Flow Builder in its Flow documentation, and our beginner's guide to Salesforce Flow covers what Flow can do on its own. If you are comparing document tools rather than workflow tools, our page comparing Conga Composer, Nintex DocGen, Formstack and S-Docs sets out the differences, but use the AppExchange listing above for current DocGen pricing.

Section 07 · Use Cases

Where Does Nintex Fit Best?

Nintex fits processes with several hand-offs, several systems and a document or approval at the end. The four patterns below are illustrations of how the products combine, not client results. Each one maps the process first, then automates the steps that are stable and frequent.

Sales

Quote to signed contract from Salesforce

A rep requests a discount on an opportunity. A Salesforce update start event launches an approval task for the sales manager and, above a threshold, finance. On approval, DocGen builds the quote and contract from the opportunity, and Nintex eSign sends them for signature. The signed copy is stored on the record.

Operations

Employee onboarding across HR, IT and facilities

An HR start form launches tasks for IT accounts, equipment and building access in parallel, with reminders and escalation. Most participants never open Salesforce, which is where My Nintex and its task forms help.

Compliance

Controlled procedures with an approval trail

Process Manager holds each procedure with a named process owner and expert, and changes are approved before they are published. Workflows then follow the approved procedure, which gives auditors one place to see how work is meant to happen.

Finance

Data entry into a system without an API

An unattended Nintex RPA bot copies approved invoice data into a legacy finance application on a schedule, and the workflow records the result. Bots suit stable screens and rules; when a system has an API, a connector is usually the better choice.

Our original post described a hospital and a bank with specific time savings. Those figures had no published source, so we have removed them. Our Nintex process automation services page describes how we find and score automation candidates before building.

Section 08 · 2026 Updates

What Is New in Nintex in 2026?

Nintex added AI actions to workflows, AI-generated workflows, AI agents and adaptive orchestration, and a packaging model called Nintex Solutions. The agent and orchestration features were in open beta in mid-2026, with general availability announced as planned for later in the year, so check their status before planning around them.

  • AI actions in workflows. A core "AI actions" group analyses, summarises or generates content inside a workflow, and Nintex Apps gained AI actions to detect and translate language, summarise text and analyse sentiment.
  • Agent Designer and Orchestration. Announced in March 2026. Agent Designer builds AI agents that run inside orchestrated processes and can hand over to people. Orchestration runs processes in phases that can advance, repeat, escalate or reroute based on context. Nintex's Q2 2026 update opened both as a beta to Nintex CE and Nintex Workflow customers, with general availability on the Professional tier and above planned later in the year.
  • Nintex Solutions. Announced in August 2026, Solutions packages workflows, forms, apps, documents and integrations into one governed unit, with versioning, approvals and promotion between environments.
  • On-premises AI. Nintex Automation K2 5.9.1 adds a locally hosted AI model for sentiment analysis and severity scoring, with no cloud dependency.

For Salesforce teams also weighing Agentforce, the question is where each agent should live. Agents that act on Salesforce data belong close to it; agents that coordinate work across many systems are where Nintex Orchestration is aimed. Our guide on how Agentforce works covers the Salesforce side.

Section 09 · Pitfalls

What Mistakes Should You Avoid with Nintex Workflows?

Most Nintex problems come from building before the process is agreed, and from running workflows nobody owns. The mechanics, such as connections, permissions and error handling, cause the rest. The six below are among the most common, especially where Nintex is connected to Salesforce.

Automating an unmapped process. The workflow fixes today's workarounds in place. Agree the process, its owner and its exceptions first, in Process Manager or on paper.
Personal accounts in connections. When that person leaves or their Salesforce password changes, every workflow using the connection fails. Use dedicated integration accounts with only the access they need.
Workflows that trigger themselves. An update start event plus an update action on the same record can loop. Use separate connections, as Nintex advises, and conditions that ignore the workflow's own changes.
Tasks assigned to named people. Approvals stall during holidays and reorganisations. Assign to roles or groups, and switch on delegation and escalation.
No error handling or monitoring. Failed instances go unnoticed until someone complains. Add failure paths and notifications, and review failed instances weekly.
Building and testing in production. Test in a separate tenant or Salesforce sandbox, and remember that connections do not move with an exported workflow.

Our guide to 10 common Nintex workflow mistakes covers each one with its fix. If you already have many workflows, a Nintex workflow optimization review sorts them into retire, repair, re-architect and keep.

Section 10 · Getting Started

How Do You Get Started with Nintex Process Automation?

Start with one frequent, stable, multi-step process that people complain about, map it, and automate it end to end before you scale. A first workflow that runs reliably for a month teaches more than ten half-finished ones. These seven steps are the sequence we follow with growing and mid-market companies.

1. Pick the process.
→ Score candidates on volume, number of hand-offs, systems touched, error cost and compliance exposure. Choose one with a clear owner.
2. Map it.
→ Record the steps, roles, exceptions and documents as the process really runs, and agree the target version with its owner.
3. Set up access.
→ Assign Nintex roles (Participant, Designer, administrators), set up single sign-on, and create dedicated integration accounts for Salesforce and other connections.
4. Build in a test environment.
→ Start event, forms, tasks, connector actions and error paths, connected to a Salesforce sandbox.
5. Test with real users.
→ Run normal, rejected and failed paths, and check permissions, delegation and documents.
6. Publish and train.
→ Publish, show participants My Nintex, and name a business owner who tracks the workflow.
7. Measure, then scale.
→ Track cycle time, failed instances and task ageing, then move to the next process with the same standards.

Our Nintex workflow automation services follow the same approach, with build standards, peer review and testing.

Section 11 · Bottom Line

The Bottom Line

Nintex is a strong choice when a process spans people and systems beyond Salesforce, or when documents, signatures and governed procedures are part of it. For automation that lives entirely in Salesforce, Flow is often enough. Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges: we implement, rescue, optimize, and integrate complex CRM and revenue systems, including Nintex alongside Salesforce.

  1. 1

    Use the 2026 names: Nintex CE, Nintex Workflow, Process Manager, Nintex eSign and Nintex Apps for Salesforce.

  2. 2

    Think of every workflow as a start event, actions, connections and variables.

  3. 3

    Connect Salesforce with a dedicated user, the right permissions and a stable token policy.

  4. 4

    Make sure DocGen for Salesforce runs on the Modern connected app.

  5. 5

    Map the process, start with one workflow, and give every workflow an owner.

Ready to Start

Find the Right First Process to Automate

Tell us which process slows your team down and which systems it touches. We will tell you whether Nintex, Salesforce Flow or both fit, and what the first workflow should look like.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Nintex is used to map and automate business processes: approvals, requests, onboarding, document generation, e-signatures and repetitive data entry. Teams build workflows by drag and drop or from a prompt, connect them to systems such as Salesforce, SharePoint and Box, and let participants complete forms and tasks in My Nintex.

Nintex now calls its cloud platform Nintex CE, or Nintex Automation CE, and its help site states that Nintex Workflow is now part of the Nintex CE Platform. Workflows, forms and connections work as before. Promapp is now Process Manager, AssureSign is Nintex eSign, and Skuid SFX is Nintex Apps for Salesforce.

Yes. Nintex Workflow has a Salesforce connector that creates, updates, deletes and queries records and starts workflows when records are created or updated. Nintex DocGen for Salesforce generates documents from Salesforce records, Nintex Apps for Salesforce builds custom pages, and Nintex eSign sends documents for signature from Salesforce.

Neither is better in general. Salesforce Flow suits automation that stays inside Salesforce and must react immediately to record changes. Nintex suits processes that involve people and systems outside Salesforce, need documented procedures, or produce documents and signatures. Many organisations use Flow for record logic and Nintex for the wider process.

The Salesforce AppExchange listing shows Nintex DocGen for Salesforce starting at $5,000 per company per year, with discounts for nonprofits. The final price depends on your edition and usage, so confirm it with Nintex. Per-user prices quoted in older articles are out of date.

Both, depending on the job. Business users can build forms and simple workflows by drag and drop, or generate a first draft with AI. Connecting systems, handling errors, setting permissions and building component workflows that other services call over HTTP still need technical skills and governance.

Yes. Nintex Automation K2 is the self-hosted edition, running on Microsoft Windows and SQL Server, for organisations that need full control and data sovereignty. Nintex CE is the multi-tenant cloud platform. Nintex RPA and Nintex Gateway can also reach on-premises systems from cloud workflows.

Users need Participant access to the Nintex CE tenant. Business owners see all instances of their workflows, initiators see the instances they started, and task assignees see the instances behind their tasks. Each workflow owner can widen or narrow this in the workflow's My Nintex settings, including whether tasks can be delegated.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Nintex workflows and document automation for Salesforce, for 500+ clients over 12+ years.