# 6Sense

![6Sense_logo.png|400](https://assets.relyanceuat.xyz/images/docs/38586544072845/38586544059021_white.png)

This integration enables syncing 6sense intent, enrichment, and segment data into Relyance AI— empowering account prioritization, segmentation, and downstream workflows.

### **Prerequisites:**

- Active **6sense account** with API access
- An API token with access to both:
    - **People Search API** — used to authenticate the connection when you first set it up
    - **People Enrichment API** — used to pull people-level data once the connection is running
- Admin access to Relyance AI

### **Generate API Credentials in 6sense:**

To generate a unique API token:

1. In the 6sense Platform, go to **Settings >> API Token Management**.
2. Click **Generate New API token**.
3. Under **API group**, select the group(s) that give you access to **People Search API** and **People Enrichment API**, then name your token (e.g. "Relyance Integration"). 6sense tokens are locked to the API group(s) chosen at creation and cannot be re-scoped later — if you're unsure whether your plan issues one combined token or separate tokens per group, check with your 6sense account admin.
4. Select **Relyance** under Integrations.
5. Add Allowed domains, if you want to restrict the usage of API on selected domains. This option is only available for Company Identification API and does not apply here.
6. Copy your API token immediately — 6sense will not show it again after you leave the page.

> If you see the error **"6Sense rejected the API token. Verify the token has PeopleSearch API access"** when connecting, the token in use was generated without People Search API access. Generate a new token that includes **People Search API** (and **People Enrichment API**, so data pulls don't silently come back empty afterward) and re-enter it in Relyance.

### **Setup in Relyance AI application:**

1. Go to: **Settings → Integrations**.

2. Choose **6sense** from the integration catalog.
![Screenshot](https://assets.relyanceuat.xyz/images/docs/38586544072845/38586544061069.png)
3. Click on **Add Integration**, Provide a connection name
4. Check the **Connections Options**\
![Screenshot](https://assets.relyanceuat.xyz/images/docs/38586544072845/38586552936333.png)
5. Define the **Rescan Frequency**\
![Screenshot](https://assets.relyanceuat.xyz/images/docs/38586544072845/38586552937613.png)
7. Enter the API Token and Account Domain:\
![Screenshot](https://assets.relyanceuat.xyz/images/docs/38586544072845/38586544069133.png)
**API Token**- Use the API token which was generate from the previous steps. **Account Domain** - Get the Account Domain from the 6Sense team.
8. Click on **Authenticate**
9. After the authentication click on **Finish**
10. Congratulations! Now you are now connected to **6sense**

<!-- 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 credential rotated at the vendor is not picked up here.** **Api Token** and **Account Domain** are 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.
2. **Check the address fields before suspecting the credentials.** **Account Domain** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

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

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

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `Api Token` (secret), `Account Domain` (secret) | — |

<!-- auth-methods: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" "6sense" {
  vendor = "6sense"
  name   = "<your connection name>"

  auth = {
    method = "api-token"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      API_TOKEN = var.6sense_api_token
      ACCOUNT_DOMAIN = var.6sense_account_domain
    }
    secrets_wo_version = 1
  }

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

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