Allowlist IP addresses
This page references the IP addresses that you may need to allowlist in your firewalls and networking devices to enable communications with Nintex cloud products. To execute workflows and services that connect to other systems, firewall rules are required to allow traffic from and to Nintex IP addresses. If firewall rules are not configured correctly, then a connection cannot be made and functionality will fail.
Important: IP addresses change over time, so ensure that you periodically review and update them. You can set up a Microsoft Azure action group to notify you if the IP addresses that you have in your allowlists have failed so that you can update them. Nintex does not monitor or communicate IP address changes.
Jump to:
Nintex Automation Cloud
Important: IP addresses change over time, so ensure that you periodically review and update them. You can set up a Microsoft Azure action group to notify you if the IP addresses that you have in your allowlists have failed so that you can update them. Nintex does not monitor or communicate IP address changes.
Nintex Automation Cloud is hosted in Microsoft Azure and uses Imperva Web Application Firewalls (WAF). The public IP address ranges of Nintex Automation Cloud services are determined by Microsoft Azure and Imperva.
To enable communications between Nintex Automation Cloud and your firewalls and networking applications, add the Microsoft Azure IP addresses to your allowlists. The ranges unique to your region are available in the downloadable JSON file.
To enable inbound data communications to Nintex Automation Cloud, add Imperva's latest IP address ranges to your allowlists.
If you are sending emails from a workflow using a Nintex Automation Cloud communication action, add the 149.72.132.168, 167.89.109.75, and 198.21.3.35 IP addresses to your allowlists. Emails originating from these IP addresses will bypass spam filters and be allowed.
For Microsoft Azure SQL and Microsoft SQL Server connectors, search for "AppService" in the Microsoft Azure IP addresses downloadable JSON file and allowlist those IP addresses. The ranges unique to your region are available in the file (for example, "AppService.NorthEurope"). Other connectors such as Smartsheet, Exchange Online, Google Drive, Nintex eSign, ServiceNow, Salesforce, SharePoint Online, and Box may also require you to add the AppService IP addresses to your allowlists. Because the downloadable JSON file from Microsoft contains many IP addresses, we are providing a condensed list of public IP addresses for these connectors to aid you in updating your allowlists.
| Australia | Canada | Europe | USA | UK |
|---|---|---|---|---|
|
|
|
|
|
For other Nintex Automation Cloud connectors, see the list of public IP addresses for Nintex Xtensions.
Nintex Gateway
Nintex Gateway is an on-premises application that enables Nintex Automation Cloud to access on-premises resources, such as Nintex RPA Central, Microsoft SQL Server on-premises on-premises, and SharePoint on-premises.
Nintex Gateway creates an outbound connection from the on-premises system where Nintex Gateway is installed. See the Nintex Gateway download and installation prerequisites for a list of hostnames that should be allowed to be reached.
Nintex Xtensions
Important: IP addresses change over time, so ensure that you periodically review and update them. Nintex does not monitor or communicate IP address changes.
Nintex Xtensions is an extensibility framework for Nintex Automation Cloud that allows you to create connectors to connect to third-party platforms in your workflows.
If you are creating an on-premises Xtension and are not using Nintex Gateway, you may need to allow Nintex Automation Cloud to connect through your firewalls. To enable these communications, add the IP addresses for your tenant region, listed below, to your allowlists.
| API Gateway | Public IP address |
|---|---|
| Australia South East | 13.70.175.145 |
| Canada Central | 20.200.72.235 |
| Japan East | 20.46.188.38 |
| North Europe | 20.67.164.93 |
| UK South | 20.90.233.85 |
| West US | 137.135.15.65 |
We recommend that you use Nintex Gateway for on-premises Xtensions, instead of opening ports. See Integrate on-premises applications via Nintex Gateway for more information.
Nintex Insights
Important: IP addresses change over time, so ensure that you periodically review and update them. You can set up a Microsoft Azure action group to notify you if the IP addresses that you have in your allowlists have failed so that you can update them. Nintex does not monitor or communicate IP address changes.
To enable Nintex Insights communications, add Imperva's latest IP address ranges to your allowlists.
Because the Nintex Insights front end static content is served via Azure CDN, which doesn’t sit behind the Imperva Web Application Firewall (WAF), you may also need to allowlist Azure CDN IP addresses. These public IP address ranges are determined by Microsoft Azure. Download a JSON file that includes the complete list of Microsoft Azure IP addresses and then search for "AzureFrontDoor.Backend" and allowlist those IP addresses.
Nintex eSign
Important: IP addresses change over time, so ensure that you periodically review and update them. You can set up a Microsoft Azure action group to notify you if the IP addresses that you have in your allowlists have failed so that you can update them. Nintex does not monitor or communicate IP address changes.
Nintex eSign is hosted in Microsoft Azure and uses Imperva Web Application Firewalls (WAF). The public IP address ranges of these services are determined by Microsoft Azure and Imperva.
To enable communications between Nintex eSign and your firewalls and networking applications, add the Microsoft Azure IP addresses to your allowlists. The ranges unique to your region are available in the downloadable JSON file.
To enable Nintex eSign inbound communications, add Imperva's latest IP address ranges to your allowlists.
Because the downloadable JSON file from Microsoft contains many IP addresses, we are providing a condensed list of public IP addresses to aid you in updating your allowlists.
| APAC | CA1 | EU1 | NA1 | SB | WWW |
|---|---|---|---|---|---|
|
|
|
|
|
|
Nintex DocGen for Salesforce
If you are using FTP/SMTP servers or services with your DocGen Package delivery options, or if you are utilizing Salesforce IP Restrictions, add the IP addresses listed below to your allowlists:
-
4.198.112.112 - 4.198.112.119
-
20.25.131.192 - 20.25.131.199
-
20.170.41.136 - 20.170.41.143
-
23.96.193.24 - 23.96.193.31
-
52.168.91.200 - 52.168.91.207
-
13.64.29.201
-
13.64.30.23
-
20.79.234.18
-
20.185.105.142
-
52.147.39.56
Nintex K2 Cloud
Important: IP addresses change over time, so ensure that you periodically review and update them. You can set up a Microsoft Azure action group to notify you if the IP addresses that you have in your allowlists have failed so that you can update them. Nintex does not monitor or communicate IP address changes.
After provisioning, each Nintex K2 Cloud tenant has a dedicated public IP address. Nintex K2 Cloud tenants are hosted in Microsoft Azure. The public IP address ranges of Nintex K2 Cloud services are determined by Microsoft Azure.
To enable communications between Nintex and your firewalls and networking applications, add the Microsoft Azure IP addresses to your allowlists. The ranges unique to your region are available in the downloadable JSON file.
To learn about allowlisting IP addresses for Nintex K2 Cloud inbound communications via VPN or OPDA, attend an onboarding meeting between Nintex and your networking resources at the time of configuration.
If you use the on-premises data access tool for Nintex K2 Cloud, see the list of connector configuration ports.
Nintex K2 Five
The public IP address ranges of Nintex K2 Five services are dependent on customer environments. To view a list of ports commonly used in a K2 implementation, see the Nintex K2 Five Installation and Configuration Guide.
Nintex Process Manager and Nintex for Office 365
Important: IP addresses change over time, so ensure that you periodically review and update them. You can set up a Microsoft Azure action group to notify you if the IP addresses that you have in your allowlists have failed so that you can update them. Nintex does not monitor or communicate IP address changes.
Nintex Process Manager and Nintex for Office 365 are hosted in Microsoft Azure and use Imperva Web Application Firewalls (WAF). The public IP address ranges of these services are determined by Microsoft Azure and Imperva.
To enable communications between Nintex Process Manager and Nintex for Office 365 and your firewalls and networking applications, add the Microsoft Azure IP addresses to your allowlists. The ranges unique to your region are available in the downloadable JSON file.
To enable Nintex Process Manager and Nintex for Office 365 inbound communications, add Imperva's latest IP address ranges to your allowlists.
Nintex RPA LE
Important: IP addresses change over time, so ensure that you periodically review and update them. Nintex does not monitor or communicate IP address changes.
Nintex RPA LE uses the Incapsula Web Application Firewall (WAF) service for IP address allowlists. We strongly recommend allowlisting the domain, as the service uses a CNAME that could resolve to different IP addresses. However, if you need to allowlist by IP address instead, use Imperva's latest IP address ranges.
Current IP address ranges are listed below:
-
199.83.128.1 - 199.83.135.254
-
198.143.32.1 - 198.143.63.254
-
149.126.72.1 - 149.126.79.254
-
103.28.248.1 - 103.28.251.254
-
185.11.124.1 - 185.11.127.254
-
45.64.64.0 - 45.64.67.255
-
192.230.64.1 - 192.230.127.254
-
107.154.0.0 - 107.154.255.254
-
45.60.0.1 - 45.60.255.254
-
45.223.0.1 - 45.223.255.254
-
2a02:e980:0:0:0:0:0:0 - 2a02:e987:ffff:ffff:ffff:ffff:ffff:ffff