> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/nintex-workflow-cloud.md).

# Nintex Workflow Cloud

Use Nintex Workflow Cloud data with Cortex Cloud.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

**SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.

**saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Nintex Workflow Cloud connector

Cortex Cloud supports Nintex Workflow Cloud accounts assigned to the Global Administrator role.

To access Nintex Workflow Cloud, Cortex Cloud requires the following information, which you will specify during the connection process.

* **Client ID:** The unique identifier for the app you create in Nintex Workflow Cloud. Cortex Cloud uses this value to identify your integration.
* **Client Secret:** The secret key associated with your Nintex Workflow Cloud app. Cortex Cloud uses the Client ID and Client Secret to authenticate to the Nintex Workflow Cloud API.

Perform the following procedures in the order that they appear below.

#### Task 1: Create an App in Nintex Workflow Cloud

1. Log in to a Nintex Workflow Cloud account assigned to the **Global Administrator** role.
2. Navigate to **Settings** → **Apps and Tokens**.
3. Click **Add** to create a new app.
4. Copy the **Client ID** and **Client Secret** associated with your app and store them securely in a text file.

   > Do not continue to the next step unless you have copied both values. You must provide them to Cortex Cloud during the onboarding process.

#### Task 2: Connect Nintex Workflow Cloud to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Nintex Workflow Cloud.
4. Under **Recommended**, hover over the new Nintex Workflow Cloud integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Client ID** and **Client Secret** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that Nintex Workflow Cloud is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/nintex-workflow-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
