# Qualtrics

![Qualtrics_XM_Logo.jpg](https://assets.relyanceuat.xyz/images/docs/36494596580493/36494596573965.jpg)

Qualtrics is a web-based platform primarily used for creating and distributing surveys, collecting responses, and analyzing data, all within a single interface.

To connect Relyance AI with Qualtrics, you will need an API Key:

**In Qualtrics:**

1. **Access Account Settings:** In the top-right corner of the screen, click on your account name and select **Account Settings.** Please note you must be an Admin.
2. **Refer to Qualtrics IDs**
3. **Find the API Token:** In the API box, you will find your API token.
    - If the API box is empty, click **Generate Token**.
4. **Copy the Token:** Select the token and copy it to paste it in Relyance AI.

**In the Relyance AI application:**

1. Login to your **Relyance** account.
2. Navigate to the **Settings** **Menu** in the bottom left-hand side.
3. Select **Integrations**.
4. Search and locate the **Qualtrics** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the Connection section, provide the appropriate values and click on **Continue**.
9. In the **Authentication** section, choose **Custom**. Provide the **Data Center** and **API Key.**

    The **Authentication** step asks for:

    - **Data Center (Eg: https://yul1.qualtrics.com)**: required.
    - **API Token**: required; held as a secret.
10. Review the configuration summary from the **Completion** section and click on **Finish**.
11. Confirm the integration Status reflects **Connected**.

![Screenshot](https://assets.relyanceuat.xyz/images/docs/36494596580493/36495965243789.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/36494596580493/36495946286605.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/36494596580493/36495946291853.png)

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `read:directory_contacts`, `delete:directory_contacts`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **A credential rotated at the vendor is not picked up here.** **API Token** is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

<!-- failure-modes:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "sap_qualtrics" {
  vendor = "sap_qualtrics"
  name   = "<your connection name>"

  auth = {
    method = "api-token"
    params = {
      data_center = "<data_center>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_token = var.sap_qualtrics_api_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->