Note: Nintex Apps data centers are located in West US and Australia (AUS). In-region processing of Nintex Apps data is only available in these regions.

Connectors

The power of Nintex Apps lies in the ability to bring together all of your data within a cohesive user experience. To bring that data into your pages, you'll first connect to that data in the Nintex Apps UI.

There are three key concepts in connecting to data with Nintex Apps:

• Connectors are Nintex Apps "helpers" that facilitate the communication between Nintex Apps and a data system. These bundles of code allow Nintex Apps to speak with other systems, and newconnectors generally are included with every major release of Nintex Apps.

  Nintex Apps contains several pre-configured connectors, which allow for plug-and-play connections to specific data services. Some of these include Salesforce, Google Drive, and the others listed in this section's table of contents.

  But to allow admins and developers the flexibility of connecting to other services, there are connectors that are not attached to specific products—such as the REST and ODataconnectors. While these require additional configuration to use, they facilitate connections to a plethora of services.

• Authentication providers are used to authenticate to data systems and are often the first step in connecting to data. They are configured by admins in the Nintex UI to coordinate with—and authenticate to—an external system. Additionally, admins often make adjustments within the external system to properly configure permissions and create the necessary credentials for authentication. For systems produced by the same company—such as Google—it is often sufficient to create one authentication provider for multiple connections.

• Connections are the individual associations between Nintex Apps and a specific service. They are configured by admins in the Nintex Apps UI and depend on both of the above concepts. Nintex Apps connections use connectors to speak a service's language and authentication providers to authenticate to a service.

Once you've created your connections, you can implement as many as you want in each Nintex Apps page through models; you can mix and match data from Salesforce orgs, REST connections, and various other sources all in one page.

Any headers or parameters that should be sent with every request (such as API keys and/or authentication) are configured on the connection.

Note:  Be conscious of whether the page you're working with is added to the app it will be deployed within. Using a page within a deployed app's pages without first adding it to the app could result in unexpected behaviors. See the Apps topic for more information.