Nintex Partner Portal — Connection Reference

To map external integrations for the Nintex Partner Portal, you can catalog each API, proxy path, and service with key metadata including endpoints, auth headers, rate limits, and configuration files. This prevents hunting across the repository and deployment scripts.

Syncing Northpass and Impartner requires specific environment variables, MariaDB database connection pools, and PM2 deployment targets. Maintaining these configurations keeps the production portal stable during incremental syncs and WebSocket events.

You can audit MariaDB and Databricks API connections by referencing a centralized inventory of service endpoints, auth headers, and rate limits. This operational playbook documents how notifications and syncs flow across services to troubleshoot failures faster.

Yes, you can use Node.js scripts to document deployment hosts and SMTP configurations. The reference relies on Node.js dependencies including dotenv, mariadb, and node-fetch to capture environment variables and service metadata required for production stability.

The best way to onboard new partners to a portal with external integrations is to use an operational playbook that documents how incremental syncs, notifications, and WebSocket events flow across Northpass, Impartner, and Databricks services.

Portal sync chains often fail due to missing or incorrect environment variables, database connection pool limits, or expired auth headers. Auditing the API proxy paths and rate limits across Northpass, Impartner, and Databricks helps identify the broken link.