> 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/administration-and-troubleshooting/integrations/add-an-integration-instance.md).

# Add an integration instance

Add and configure an integration instance in Cortex XSIAM.

To use a downloaded integration, you must configure an integration instance.

Before you begin:

* Content packs containing integrations are downloaded when you adopt playbooks and configure playbook tasks. The content pack must be downloaded before you can configure an integration instance.
* Consider whether you want to add credentials, which enable you to save login information without exposing usernames, passwords, certificates, and SSH keys. For more information, see [Manage credentials](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/administration-and-troubleshooting/integrations/manage-credentials.md).
* Although you can view integration documentation when adding an instance, [https://xsoar.pan.dev/](https://xsoar.pan.dev/docs/reference/index) has more detailed information about integrations, including commands, outputs, and recommended permissions.

{% stepper %}
{% step %}

### Find the integration

Navigate to **Settings** → **Data Sources & Integrations**. Search for the integration.
{% endstep %}

{% step %}

### Add an instance

Select the integration and click **Add Instance**.
{% endstep %}

{% step %}

### Configure parameters

Add the required parameters.
{% endstep %}

{% step %}

### Test the connection

Optional: Click **Test** to verify the integration instance works correctly.
{% endstep %}

{% step %}

### Save the instance

Click **Save & Exit**.

You can expand the integration to view instance details. You can also enable, disable, or copy the instance.

If an error occurs, see [Troubleshoot integrations](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/administration-and-troubleshooting/integrations/troubleshoot-integrations.md).
{% endstep %}

{% step %}

### Choose when to use the instance

By default, the instance runs whenever the integration is called. Change **Always** to **On Demand** to use it only with the `using` argument in a playbook or CLI.

For example, use an on-demand instance for manual testing.
{% endstep %}

{% step %}

### Configure command access

Optional: See [Configure integration permissions](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/administration-and-troubleshooting/integrations/configure-integration-permissions.md) to manage access to specific commands.
{% endstep %}
{% endstepper %}


---

# 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/administration-and-troubleshooting/integrations/add-an-integration-instance.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.