# Clearbit

![Clearbit_Logo__Color_.svg](https://assets.relyanceuat.xyz/images/docs/7121553611533/7121245185805.svg)
Clearbit is a web-based sales intelligence platform that enriches sign-ups, identifies prospects and obtains customer insights. It does so by searching the web with the ability to parses millions of data-points in real time, and obtain actionable intelligence from multiple sources.

In order to integrate Clearbit with Relyance AI you will need a **Clearbit API Key** and your Clearbit **Company Domain**.

#### In Clearbit:

1. Login to your Clearbit account.
2. Go to the API section in Clearbit: [https://dashboard.clearbit.com/api](https://dashboard.clearbit.com/api)
3. Here you will find your **Secret API Key,** this will be used as your **Clearbit API Key**.
4. The **Company Domain** will be your company's domain, for instance Relyance's domain is *relyance.ai.*

![Clearbit-1.png](https://assets.relyanceuat.xyz/images/docs/7121553611533/7121966704013.png)

#### 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. Click on the **Vendors and Data Stores** filter.
5. Find the **Clearbit** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Custom**.
8. Paste the **Clearbit API Key** and **Company Domain** into their respective fields.

![Clearbit-2.png](https://assets.relyanceuat.xyz/images/docs/7121553611533/7121966532621.png)

9. Click **Authenticate**.
10. At this point, you should see the following result on the Vendor Integrations page:

![Clearbit-3.png](https://assets.relyanceuat.xyz/images/docs/7121553611533/7121966532749.png)

11. Congratulations, you are now connected to **Clearbit**.

<!-- 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.** **Clearbit API Key** 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.
2. **Check the address fields before suspecting the credentials.** **Company 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 -->

<!-- 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" "clearbit" {
  vendor = "clearbit"
  name   = "<your connection name>"

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

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

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