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.

Callback URLs/Redirect URIs

In OAuth 2.0 authentication, the client—on the end user's behalf—will send the server a client ID, credentials, scopes, and callback URLs—all of which the server needs in order to properly authenticate a client. The callback URLs, also known as redirect URIs, tell the server where to send the user with the proper tokens after authentication.

For purposes within Nintex Apps, you'll want the end user sent back to the Nintex Apps site/org accessing the data. So whether you're using one of Google's many APIs, modifying data on an external Salesforce org, or accessing a Sharepoint database, you will need to use your Nintex Apps callback URL for every external connection that uses OAuth 2.0 authentication.

Note that you will be entering your callback URL on the settings page of whatever service you are accessing, such as the Google API Console, the Salesforce Connected App page, or the Dropbox API app page. You will not be entering this URL on any Nintex Apps page.

Constructing callback URLs

For Nintex Apps sites, append /auth/oauth/callback to your Nintex Apps site's domain URL.

Some examples:

• For https://example-us-trial.skuidsite.com/, use https://example-us-trial.skuidsite.com/auth/oauth/callback
• For https://gui-construction.skuidsite.com/, use https://gui-construction.skuidsite.com/auth/oauth/callback
• For https://asgard-talent-management.skuidsite.com/, use https://asgard-talent-management.skuidsite.com/auth/oauth/callback