Skip to content

Integrating SailPoint with Nintex

Nintex Automation Cloud (formerly Nintex Workflow Cloud) is a cloud-based platform that allows organizations to manage, automate, and optimize business processes. It provides tools for workflow automation, digital forms, and process intelligence, enabling users to streamline operations and improve productivity without extensive coding. This document provides instructions to configure a new direct connection to a Nintex source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Nintex connector supports the following:

Account Management

  • Aggregate Account Retrieve user identities and their core attributes from the target system.
  • Entitlement Management The managed system does not provide APIs for aggregating entitlements (roles); only account aggregation is supported

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Supported Managed System

  • Target System: Nintex Automation Cloud
  • Current Version: Cloud-based (SaaS)

Prerequisites

To successfully integrate and manage Nintex Automation Cloud (formerly Nintex Workflow Cloud) as a managed system, ensure the following requirements are met:

  • Administrator Access You must have a user account with Tenant Administrator permissions in the Nintex Automation Cloud instance to manage connections, apps, and security settings.
  • Tenant Environment Details Identify your specific Nintex Tenant URL (e.g., <https://[your-tenant-name].nintexcloud.com).> This is required for API endpoint configuration.
  • Authentication & API Access Nintex supports authentication via Personal Access Tokens (PAT) for user-level access or Service Credentials (OAuth 2.0 Client ID and Secret) for application-level integration.
    • Personal Access Token: Best for quick integrations and scripts.
    • Application/Service Credentials: Recommended for long-term managed system connections to ensure stability and scoped permissions.
  • Scopes and Permissions Ensure the generated token or application has the necessary scopes (e.g., workflows:read, tasks:write, users:read) depending on the automation requirements.
  • Official Documentation Reference For detailed steps on generating authentication tokens and managing application security, refer to the official documentation:

Required Permissions

To integrate with Nintex Automation Cloud, you must ensure the service account or user generating the credentials has the appropriate administrative privileges to access tenant-wide data.

  1. Service Account / API Credentials
    • Role Requirement: Only users assigned the Tenant Administrator role can create and manage API Keys for the tenant.
    • Authentication Method: The integration utilizes a Personal Access Token (API Key) generated within the Nintex Automation Cloud dashboard.
    • Generation Path: API Keys are managed via Settings > Tenant > Apps and tokens.
  2. Scope for Connector To ensure the integration can successfully fetch the full list of users and workflow data, the following requirements apply:
    • Administrative Access: The API Key must be associated with a user account that has tenant-wide visibility.
    • Role Limitations: If a service account is restricted to a "Developer" or "Designer" role instead of "Automation Administrator," the integration may fail to retrieve the complete identity list or global configuration settings.
    • Object Visibility: The user account must have permissions to view workflows and instances to retrieve account and workflow data correctly across the environment.
  3. Documentation Links For detailed instructions on setting up authentication and managing roles, refer to the following official resources:

Note

The linked document is not maintained by SailPoint and is subject to change without notice.