# Demandbase

![Integrate Demandbase with Salesloft - Salesloft](https://assets.relyanceuat.xyz/images/docs/39167083083917/ext-0f4d72ff8b.png)
Demandbase is an account-based marketing, advertising, sales intelligence and data company. It helps B2B companies hit their revenue goals using fewer resources. By using the power of AI to identify and engage the accounts and buying groups most likely to purchase. Demandbase combines your sales and marketing data with its validated B2B data and AI to create Account Intelligence that informs every step of your buyer’s journey.

In order to integrate ActiveCampaign with Relyance AI you will need a **Client ID** and **Client Secret** from Demandbase **.**

#### In Demandbase portal:

![DemandBase -1.png](https://assets.relyanceuat.xyz/images/docs/39167083083917/39652435634829.png)
1. Login to your Demandbase account.
2. Go to **Settings > APIs > API Key Sets**.
3. Click the Create New button
4. Enter an **API Key Set Name** and click on Save.
5. On the **API Permissions** step, check: **- API Admin / User Management** **- B2B Admin / Full Access**
6. Click **Next**.
7. Click **Create Token** to create a new **API token**.
8. The API Token generates two keys, **Client ID** and **Client Secret** copy them and store, they will be used in the next steps.

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

![Demandbase -2.png](https://assets.relyanceuat.xyz/images/docs/39167083083917/39652435637645.png)

#### In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations.**
4. Choose Demandbase from the integration catalog.
5. Click on **Add Integration.**
6. Provide a connection name.
7. Check the **Connections Options** and follow the steps-
8. Enter the **Client ID** and **Client Secret** (from Demandbase step 8).
9. Click on **Authenticate.**
10. After the authentication click on **Finish.**
11. Congratulations! Now are now connected to Demandbase.

![Demandbase -3.png](https://assets.relyanceuat.xyz/images/docs/39167083083917/39652442796685.png)

![Demandbase -4.png](https://assets.relyanceuat.xyz/images/docs/39167083083917/39652435641613.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. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. **A credential rotated at the vendor is not picked up here.** **Client Secret** 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 -->

<!-- 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 |
| --- | --- | --- |
| **Two Legged Oauth2** | `Client ID`, `Client Secret` (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" "demandbase" {
  vendor = "demandbase"
  name   = "<your connection name>"

  auth = {
    method = "oauth-client-credentials"
    params = {
      client_id = "<client_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      client_secret = var.demandbase_client_secret
    }
    secrets_wo_version = 1
  }

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

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