6Sense

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
• Permissions for APIs:
  • People Enrichment
  • People
• Admin access to Relyance AI

Generate API Credentials in 6sense:

To generate a unique API token:

1. You can go to the Settings >> API Token management page in the 6sense Platform.
2. Click on Generate New API token.
3. Select the API group and name your token.
4. Select the 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.
6. Copy your API token.

Setup in Relyance AI application:

1. Go to: Settings → Integrations.
2. Choose 6sense from the integration catalog.
3. Click on Add Integration
4. Provide a connection name
5. Check the Connections Options
6. Define the Rescan Frequency
7. Enter the API Token and Account Domain:

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 are now connected to 6sense

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.

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.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. 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.

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 } }
}