# Demandbase

> Find and enrich companies and contacts with Demandbase, read account intent, manage keyword sets, watch companies and people for changes, and export accounts with their journey stage and engagement.

App · 24 actions. Web page: https://docs.lodol.com/docs/integrations/demandbase

## Actions

### Create keyword set

Create a keyword set to measure intent against, with its keywords and any web pages Demandbase should draw more keywords from. Needs the Intent API.

**Inputs**

- Name (`name`, text, required): The keyword set's name, which must be new.
- Keywords (`keywords`, list): The keywords, one per row, such as zero trust.
- Seed pages (`seed_urls`, list): Web pages, one https address per row, that Demandbase reads to suggest up to 100 more keywords.
- Competitive (`is_competitor`, true/false): Mark the set as about competitors.

**Outputs**

- `keyword_set` (object): The new keyword set

**Example output**

```json
{
  "keyword_set": {
    "createdAt": "2026-08-20T09:14:22Z",
    "id": 9427,
    "isCompetitor": false,
    "keywords": [
      {
        "createdAt": "2026-08-20T09:14:22Z",
        "id": 551201,
        "keyword": "zero trust",
        "updatedAt": "2026-08-20T09:14:22Z"
      }
    ],
    "name": "Cloud Security Vendors",
    "seedUrls": [
      {
        "createdAt": "2026-08-20T09:14:22Z",
        "id": 8801,
        "seedUrl": "https://example.com/security"
      }
    ],
    "updatedAt": "2026-08-20T09:20:41Z"
  }
}
```

### Create subscription

Start watching companies, their news, their family trees or people for changes. Demandbase sets it up in a job: its subscription id comes from 'Get subscription job' once the job finishes. Needs the B2B API.

**Inputs**

- Name (`name`, text, required): A name to know the subscription by.
- Watch for (`subscription_type`, text, required): What the subscription watches. One of: `company` (Company changes), `companyNews` (Company news), `dbPerson` (Person changes), `companyFamilyTree` (Company family tree changes).
- Company IDs (`company_ids`, list): The companies to watch, one Demandbase company id per row. For a family tree, give each tree's top parent company. Only when Watch for is Company changes, Company news or Company family tree changes.
- Person IDs (`person_ids`, list): The people to watch, one Demandbase person id (dbPersonId) per row, from 'Search contacts'. Only when Watch for is Person changes.
- Check every (`frequency_every`, number): How many of the unit to wait between checks, such as 7 for every 7 days. The shortest is 1 day for companies and people, 15 minutes for news and 1 week for family trees. At least 1.
- Unit (`frequency_unit`, text): The unit of 'Check every'. Defaults to days. One of: `d` (Days), `w` (Weeks), `m` (Months), `h` (Hours), `M` (Minutes).
- Start date (`start_date`, date): When to start. The first check is one frequency after it.
- Company fields to watch (`company_fields`, list): Alert when any of these change. Leave empty to watch every field. Only when Watch for is Company changes. One or more of: `all` (Any field), `name`, `activeStatus` (Active status), `companyStatus` (Company status), `companyType` (Company type), `businessStructure` (Business structure), `revenue`, `revenueRange` (Revenue range), `employees`, `employeeRange` (Employee range), and 12 more.
- Person fields to watch (`person_fields`, list): Alert when any of these change, such as a new job. Leave empty to watch every field. Only when Watch for is Person changes. One or more of: `all` (Any field), `newEmployment` (New job), `titles` (Job titles), `active` (Still in the job), `name`, `email`, `phone`, `executiveMobileNo` (Mobile number), `linkedInHandle` (LinkedIn), `twitterHandle` (X (Twitter)), and 6 more.
- News categories (`news_categories`, list): Only alert on news in these categories. Leave empty for every category. Only when Watch for is Company news. One or more of: `LEADERSHIP_CHANGES` (Leadership Changes), `NEW_OFFERINGS` (New Offerings), `ACQUISITIONS`, `PARTNERSHIPS`, `EXPANDING_OPERATIONS` (Expanding Operations), `COST_CUTTING` (Cost Cutting), `OUTPERFORMING`, `UNDERPERFORMING`, `COMPANY_PRESENTATION` (Company Presentation), `LITIGATION`, and 8 more.
- Description (`description`, text): What the subscription is for.
- Webhook address (`webhook_url`, text): An https address of your own for Demandbase to post each alert to. It must answer Demandbase's check first. Leave empty to read alerts in Lodol instead.
- Signing secret (`signing_secret`, text): A secret Demandbase signs each webhook post with, up to 500 characters.

**Outputs**

- `job` (object): The job Demandbase runs the change in. Its subscriptionId is filled in once the job finishes; read it with 'Get subscription job'.

**Example output**

```json
{
  "job": {
    "createdAt": "2026-11-02T09:00:42.620Z",
    "invalidIds": [],
    "jobId": "39ddf756-c04e-465c-b8c1-8d2c2be0abed",
    "jobStatus": "accepted",
    "jobType": "notificationSubscriptionCreate",
    "message": "",
    "subscriptionId": "",
    "subscriptionType": "company",
    "totalEntitiesProcessed": 2
  }
}
```

### Delete subscription

Delete a subscription, which stops its checks and alerts for good. Needs the B2B API.

**Inputs**

- Subscription (`subscription_id`, text, required): The subscription. Pick one, or give its id from an earlier step.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `message` (text): What Demandbase said
- `subscription_id` (text): The subscription deleted

**Example output**

```json
{
  "deleted": true,
  "message": "Subscription deleted successfully",
  "subscription_id": "63914a27-a5ca-4fdf-80b0-ffc985f53c14"
}
```

### Export account lists

Export every account list with its id, or the accounts in the lists you give. Demandbase builds the file in a job: get its link with 'Get export job'. Needs the Data Export API.

**Inputs**

- Account list IDs (`account_list_ids`, list): Lists whose accounts to export, one id per row. Leave empty to export every list instead.
- Export name (`job_name`, text): A name for the export. Defaults to Lodol account lists export.

**Outputs**

- `job` (object): The export job. Follow it with 'Get export job' until it is finished.

**Example output**

```json
{
  "job": {
    "createdAt": "2026-11-02T16:43:57.378Z",
    "entityType": "accountlist",
    "jobId": "dcb34525-2baa-4f54-8c11-9e6175ecbc74",
    "jobName": "Lodol account lists export",
    "jobStatus": "accepted"
  }
}
```

### Get company

Get a company's firmographics: industry, revenue, employees, address, phone, codes, websites and social profiles, with its family tree, competitors, logos or installed technology if you ask. Needs the B2B API; uses one credit.

**Inputs**

- Company ID (`company_id`, text, required): The Demandbase company id, digits such as 726263, from 'Search companies', 'Match company' or an earlier step.
- Also get (`include`, list): Extra details to add. One or more of: `familytree` (Family tree), `competitors`, `installedtech` (Installed technology), `logos`.

**Outputs**

- `company` (object): The company. Extra details asked for come as familyTree, competitors, logos and techUsed.

**Example output**

```json
{
  "company": {
    "address": {
      "city": "Redmond",
      "country": "US",
      "latitude": "47.64",
      "longitude": "-122.13",
      "state": "WA",
      "street": "100 Example Way",
      "zip": "98052"
    },
    "businessStructure": "Global Parent",
    "classification": {
      "primaryBusiness": {
        "industry": "Computer Software",
        "industryCode": "8"
      },
      "secondaryBusinesses": [
        {
          "industry": "Computer Software",
          "industryCode": "8",
          "subIndustry": "Enterprise Resource Planning Software",
          "subIndustryCode": "8_32"
        }
      ]
    },
    "companyId": 726263,
    "companyName": "Example Software Inc.",
    "companyStatus": "Operating",
    "companyType": "Public",
    "employeeCount": 12800,
    "financialYearEnd": "6",
    "foundedIn": "1995",
    "naics": "5132",
    "naicsDescription": "Software Publishers",
    "phone": "+1 425 555 0100",
    "revenue": 2450,
    "revenueCurrency": "USD",
    "sic": "7371",
    "sicDescription": "Services-Computer Programming Services",
    "siteCount": 41,
    "siteLocationCount": 12,
    "socialHandles": {
      "blog": "https://example.com/blog",
      "facebook": "https://www.facebook.com/example",
      "linkedIn": "https://www.linkedin.com/company/example",
      "twitter": "https://twitter.com/example"
    },
    "tickers": [
      {
        "exchange": "NASD",
        "tickerName": "EXSW"
      }
    ],
    "websites": [
      "https://www.example.com/"
    ]
  }
}
```

### Get company intent

Find which companies are researching your keywords: for each, the keyword, intent strength, how many people are researching it, and whether it is trending, week by week. Look up by keyword set, keywords or company. Needs the Intent API (in beta).

**Inputs**

- From (`start_date`, date, required): The first day to look at.
- To (`end_date`, date, required): The last day to look at, at most 12 months after 'From'.
- Keyword sets (`keyword_set_ids`, list): Up to 10 keyword sets to look up intent for.
- Keywords (`keywords`, list): Up to 50 keywords, one per row, such as zero trust.
- Company IDs (`company_ids`, list): Up to 10 Demandbase company ids, one per row, to look up intent for.
- Intent strength (`intent_strength`, text): Only signals of this strength. Leave empty for every strength. One of: `HIGH`, `MED` (Medium), `LOW`.
- Fewest people researching (`min_people_researching`, number): Only signals with at least this many people researching. At least 0.
- Most people researching (`max_people_researching`, number): Only signals with at most this many people researching. At least 0.
- Sort by (`sort_by`, text): What to sort the signals by. One of: `endDate` (Period end (default)), `startDate` (Period start), `intentStrength` (Intent strength), `numPeopleResearching` (People researching), `trendingScore` (Trending score).
- Order (`sort_order`, text): Descending unless you choose. One of: `DESC` (Descending (default)), `ASC` (Ascending).
- Most signals (`page_size`, number): How many signals to return, 1 to 100. Defaults to 25. From 1 to 100.

**Outputs**

- `signals` (list): One per company, keyword and week
- `total_count` (number): How many signals match, which may be more than were returned

**Example output**

```json
{
  "signals": [
    {
      "companyId": "726263",
      "domain": "example.com",
      "endDate": "2026-11-01",
      "intentStrength": "HIGH",
      "isTrending": true,
      "keyword": "zero trust",
      "keywordSetId": 9427,
      "keywordSetName": "Cloud Security Vendors",
      "numPeopleResearching": 8,
      "numTrendingDays": 3,
      "startDate": "2026-10-26",
      "trendingScore": 10
    }
  ],
  "total_count": 1
}
```

### Get company news

Get recent news about a company, such as leadership changes, funding or acquisitions, from all categories or the ones you pick. Needs the B2B API; uses one credit.

**Inputs**

- Company ID (`company_id`, text, required): The Demandbase company id, digits such as 726263, from 'Search companies', 'Match company' or an earlier step.
- Categories (`categories`, list): Only news in these categories. Leave empty for all news. One or more of: `LEADERSHIP_CHANGES` (Leadership Changes), `NEW_OFFERINGS` (New Offerings), `ACQUISITIONS`, `PARTNERSHIPS`, `EXPANDING_OPERATIONS` (Expanding Operations), `COST_CUTTING` (Cost Cutting), `OUTPERFORMING`, `UNDERPERFORMING`, `COMPANY_PRESENTATION` (Company Presentation), `LITIGATION`, and 8 more.
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 50. Defaults to 10. From 1 to 50.

**Outputs**

- `articles` (list): The news articles, newest first
- `company_id` (text): The company's id
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `total_count` (number): How many there are in all, across every page

**Example output**

```json
{
  "articles": [
    {
      "imageUrl": "https://news.example.com/cmo.jpg",
      "newsCategory": "LEADERSHIP_CHANGES",
      "publicationDate": "2026-11-01T14:00:00Z",
      "source": "Example Newswire",
      "title": "Example Software names a new chief marketing officer",
      "url": "https://news.example.com/example-software-cmo"
    }
  ],
  "company_id": "726263",
  "page": 1,
  "page_size": 10,
  "total_count": 1
}
```

### Get contact

Get a person's job, email addresses, phone numbers, job level and function, and social profiles, by their contact id. Needs the B2B API; uses one credit.

**Inputs**

- Contact ID (`contact_id`, text, required): The Demandbase contact id, from 'Search contacts' or 'Match company'.
- Include other jobs (`include_other_jobs`, true/false): Also list the person's other jobs.

**Outputs**

- `contact` (object): The person and their job

**Example output**

```json
{
  "contact": {
    "dbPersonDetails": {
      "firstName": "Jamie",
      "lastName": "Taylor",
      "mobileNumber": "+1 206 555 0142",
      "socialHandles": {
        "linkedIn": "https://www.linkedin.com/in/jamie-taylor-example",
        "twitter": "https://twitter.com/jamietaylor"
      }
    },
    "employmentDetails": {
      "companyId": 726263,
      "companyName": "Example Software Inc.",
      "contactId": 17864319,
      "contactQualityScore": "A",
      "emails": [
        {
          "email": "jamie.taylor@example.com",
          "validationStatus": "VALID"
        }
      ],
      "jobFunctions": [
        {
          "id": "14",
          "name": "Marketing"
        }
      ],
      "jobLevels": [
        {
          "id": "3",
          "name": "Vice President"
        }
      ],
      "lastValidatedDate": "Aug 15, 2026",
      "phoneNumbers": {
        "corporateNumber": "+1 425 555 0100",
        "directNumber": "+1 425 555 0111"
      },
      "titles": [
        "Vice President, Marketing"
      ]
    }
  }
}
```

### Get credit usage

See how many B2B API credits your Demandbase account has, has used and has left.

**Inputs**: None.

**Outputs**

- `usage` (object): The account's B2B API credits

**Example output**

```json
{
  "usage": {
    "chargingModel": "perRecord",
    "scope": "lifetime",
    "totalCreditsAllocated": 50000,
    "totalCreditsAvailable": 49885,
    "totalCreditsConsumed": 115
  }
}
```

### Get export job

Check an export: accepted, processing, finished or failed, and once finished the link to download its file, which works for 24 hours. Needs the Data Export API.

**Inputs**

- Job ID (`job_id`, text, required): The job's id, from the step that started it.

**Outputs**

- `finished` (true/false): Whether it is finished
- `job` (object): The export job
- `results_url` (text): The file's download link, valid for 24 hours; empty until finished
- `results_urls` (list): Every file's link, for exports of several files
- `status` (text): accepted, processing, finished or failed

**Example output**

```json
{
  "finished": true,
  "job": {
    "createdAt": "2026-11-02T16:43:57.378Z",
    "entityType": "account",
    "jobId": "dcb34525-2baa-4f54-8c11-9e6175ecbc74",
    "jobName": "Lodol account export",
    "jobStatus": "finished",
    "message": "",
    "resultsUrl": "https://d3sp479zadslli.cloudfront.net/apps/data-access-proxy/uapi/1017/export.json",
    "updatedAt": "2026-11-02T16:46:25.307Z"
  },
  "results_url": "https://d3sp479zadslli.cloudfront.net/apps/data-access-proxy/uapi/1017/export.json",
  "results_urls": [
    "https://d3sp479zadslli.cloudfront.net/apps/data-access-proxy/uapi/1017/export.json"
  ],
  "status": "finished"
}
```

### Get subscription

Get a subscription's settings: what it watches, how often it checks, when it next checks and its webhook. Needs the B2B API.

**Inputs**

- Subscription (`subscription_id`, text, required): The subscription. Pick one, or give its id from an earlier step.

**Outputs**

- `subscription` (object): The subscription

**Example output**

```json
{
  "subscription": {
    "createdAt": "2026-11-02T09:02:56.994Z",
    "description": "Changes at our tier 1 accounts",
    "fields": [
      "revenue",
      "employees"
    ],
    "frequency": "1d",
    "name": "Target account changes",
    "newsCategories": [],
    "nextFireTime": "2026-11-03T00:00:00.000Z",
    "startDate": "2026-11-02",
    "subscriptionId": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
    "subscriptionType": "company",
    "webhook": {
      "disableReasonMessage": "",
      "status": "ACTIVE",
      "url": "https://hooks.example.com/demandbase"
    }
  }
}
```

### Get subscription alert

Get what changed in one alert: for each company or person, the fields that changed, or the news articles and their categories, or the companies added to a family tree. Needs the B2B API.

**Inputs**

- Subscription (`subscription_id`, text, required): The subscription. Pick one, or give its id from an earlier step.
- Alert ID (`alert_id`, text, required): The alert's id, from 'List subscription alerts' or the alert trigger.
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 5000. Defaults to 5,000. From 1 to 5000.

**Outputs**

- `alert_id` (text): The alert
- `changes` (list): One entry per company or person that changed: companyId or dbPersonId with the fields that changed, or a news article's articleUrl, timestamp and newsCategories, or companyFamilyTreeChanges
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `subscription_id` (text): The subscription
- `subscription_type` (text): company, companyNews, dbPerson or companyFamilyTree
- `total_count` (number): How many there are in all, across every page
- `total_pages` (number): How many pages there are

**Example output**

```json
{
  "alert_id": "364559",
  "changes": [
    {
      "companyId": "726263",
      "fields": [
        "revenue",
        "employees"
      ]
    }
  ],
  "page": 1,
  "page_size": 5000,
  "subscription_id": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
  "subscription_type": "company",
  "total_count": 1,
  "total_pages": 1
}
```

### Get subscription job

Check a job that creates or changes a subscription: accepted, processing, finished or failed, the subscription's id once known, and any ids Demandbase didn't recognize. Needs the B2B API.

**Inputs**

- Job ID (`job_id`, text, required): The job's id, from the step that started it.

**Outputs**

- `job` (object): The job

**Example output**

```json
{
  "job": {
    "createdAt": "2026-11-02T09:00:42.620Z",
    "invalidIds": [],
    "jobId": "39ddf756-c04e-465c-b8c1-8d2c2be0abed",
    "jobStatus": "finished",
    "jobType": "notificationSubscriptionCreate",
    "message": "",
    "subscriptionId": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
    "subscriptionType": "company",
    "totalEntitiesProcessed": 2
  }
}
```

### List export jobs

List the exports started for your Demandbase account, newest first, with their status. Needs the Data Export API.

**Inputs**

- Records (`entity_type`, text): Only exports of this kind. One of: `All` (Every kind (default)), `account` (Accounts), `person` (People), `opportunity` (Opportunities), `activity` (Activities), `accountList` (Account lists), `campaign` (Campaigns), `creative` (Creatives), `accountBuyingGroup` (Account buying groups), `personBuyingGroupMember` (Buying group members), `sourceAccount` (Source accounts).
- Status (`job_status`, text): Only exports with this status. One of: `All` (Any status (default)), `accepted`, `processing`, `finished`, `failed`.
- Order (`sort`, text): Newest or oldest first. One of: `descending` (Newest first (default)), `ascending` (Oldest first).
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `jobs` (list): The export jobs
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `total_count` (number): How many there are in all, across every page

**Example output**

```json
{
  "jobs": [
    {
      "createdAt": "2026-11-02T16:43:57.378Z",
      "entityType": "account",
      "jobId": "dcb34525-2baa-4f54-8c11-9e6175ecbc74",
      "jobName": "Lodol account export",
      "jobStatus": "finished",
      "updatedAt": "2026-11-02T16:46:25.307Z"
    }
  ],
  "page": 1,
  "page_size": 10,
  "total_count": 1
}
```

### List keyword sets

List the keyword sets intent is measured against, with their ids. Needs the Intent API.

**Inputs**

- Name contains (`name_contains`, text): Only keyword sets whose name contains this.
- Sort by (`sort_by`, text): What to sort them by. One of: `createdAt` (Created (default)), `updatedAt` (Last changed), `name`.
- Order (`sort_order`, text): Descending unless you choose. One of: `DESC` (Descending (default)), `ASC` (Ascending).
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 500. Defaults to 25. From 1 to 500.

**Outputs**

- `keyword_sets` (list): The keyword sets, without their keywords
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `total_count` (number): How many there are in all, across every page

**Example output**

```json
{
  "keyword_sets": [
    {
      "createdAt": "2026-08-20T09:14:22Z",
      "id": 9427,
      "isCompetitor": false,
      "name": "Cloud Security Vendors",
      "updatedAt": "2026-08-20T09:20:41Z"
    }
  ],
  "page": 1,
  "page_size": 25,
  "total_count": 1
}
```

### List keywords in a set

List one page of a keyword set's keywords. Needs the Intent API.

**Inputs**

- Keyword set (`keyword_set_id`, text, required): The keyword set. Pick one, or give its id from an earlier step.
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 500. Defaults to 25. From 1 to 500.

**Outputs**

- `keyword_set_id` (text): The keyword set
- `keywords` (list): The keywords
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `total_count` (number): How many there are in all, across every page

**Example output**

```json
{
  "keyword_set_id": "9427",
  "keywords": [
    {
      "createdAt": "2026-08-20T09:14:22Z",
      "id": 551201,
      "keyword": "zero trust",
      "updatedAt": "2026-08-20T09:14:22Z"
    }
  ],
  "page": 1,
  "page_size": 25,
  "total_count": 1
}
```

### List subscription alerts

List the alerts a subscription has made, newest first: one for each check that found changes. Read one with 'Get subscription alert'. Needs the B2B API.

**Inputs**

- Subscription (`subscription_id`, text, required): The subscription. Pick one, or give its id from an earlier step.
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 50. Defaults to 10. From 1 to 50.

**Outputs**

- `alerts` (list): The alerts, newest first, each with its alertId
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `subscription_id` (text): The subscription
- `total_count` (number): How many there are in all, across every page
- `total_pages` (number): How many pages there are

**Example output**

```json
{
  "alerts": [
    {
      "alertId": 364559,
      "createdAt": "2026-11-03T00:05:12.202Z"
    }
  ],
  "page": 1,
  "page_size": 10,
  "subscription_id": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
  "total_count": 1,
  "total_pages": 1
}
```

### List subscriptions

List your Demandbase subscriptions, which watch companies, people or company news for changes. Needs the B2B API.

**Inputs**

- Kinds (`subscription_types`, list): Only subscriptions of these kinds. One or more of: `company` (Company changes), `companyNews` (Company news), `dbPerson` (Person changes), `companyFamilyTree` (Company family tree changes).
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 50. Defaults to 10. From 1 to 50.

**Outputs**

- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `subscriptions` (list): The subscriptions
- `total_count` (number): How many there are in all, across every page
- `total_pages` (number): How many pages there are

**Example output**

```json
{
  "page": 1,
  "page_size": 10,
  "subscriptions": [
    {
      "createdAt": "2026-11-02T09:02:56.994Z",
      "description": "Changes at our tier 1 accounts",
      "name": "Target account changes",
      "subscriptionId": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
      "subscriptionType": "company"
    }
  ],
  "total_count": 1,
  "total_pages": 1
}
```

### Match company

Find the company, and the person if you give one, that a name, website, work email or LinkedIn handle belongs to: the way to enrich a lead or a CRM record. Needs the B2B API; uses one credit for each company or person matched.

**Inputs**

- Company name (`company_name`, text): The company's name, such as Acme Inc.
- Website (`website`, text): The company's website or domain, such as acme.com.
- Work email (`email`, text): A person's work email. It finds their company, and them too.
- LinkedIn handle (`linkedin_handle`, text): A person's LinkedIn handle, the part after linkedin.com/in/.
- Stock ticker (`ticker`, text): The company's stock ticker.
- Phone (`phone`, text): The company's phone number.
- Street (`street`, text): The company's street address.
- City (`city`, text): The company's city.
- State or region (`state`, text): The company's state or region, such as WA.
- Postal code (`zip_code`, text): The company's postal code.
- Country (`country`, text): The company's country, by name, such as United States.
- First name (`first_name`, text): To match a person too: their first name.
- Last name (`last_name`, text): To match a person too: their last name.
- Job title (`title`, text): To match a person too: their job title.
- Most matches (`max_results`, number): The most companies and people to return, 1 to 50. From 1 to 50.

**Outputs**

- `companies` (list): The companies matched, best first
- `company_id` (text): The best matching company's id, empty if none
- `contact_id` (text): The best matching person's contact id, empty if none
- `contacts` (list): The people matched, best first
- `matched` (true/false): Whether anything matched

**Example output**

```json
{
  "companies": [
    {
      "city": "Redmond",
      "companyId": 726263,
      "country": "United States",
      "name": "Example Software Inc.",
      "state": "WA",
      "street": "100 Example Way"
    }
  ],
  "company_id": "726263",
  "contact_id": "17864319",
  "contacts": [
    {
      "active": true,
      "companyId": 726263,
      "contactId": 17864319,
      "contactQualityScore": "A",
      "dbPersonId": 15568398,
      "firstName": "Jamie",
      "lastName": "Taylor",
      "title": "Vice President, Marketing"
    }
  ],
  "matched": true
}
```

### Search companies

Find companies in Demandbase's database by name, website, country, industry, size, revenue and more. Gets one page of up to 50, with each company's id for 'Get company'. Needs the B2B API; uses no credits.

**Inputs**

- Company name (`name`, text): The company's name, or part of it.
- Website (`website`, text): The company's web domain, such as demandbase.com.
- Stock ticker (`ticker`, text): The company's stock ticker, such as MSFT.
- Country (`country`, text): Only companies in this country. One of: `68` (Afghanistan), `1` (Ahvenanmaan Laani), `120` (Albania), `109` (Algeria), `2` (American Samoa), `114` (Andorra), `121` (Angola), `3` (Anguilla), `4` (Antarctica), `5` (Antigua and Barbuda), and 243 more.
- State or region (`state`, text): A state or region code, such as CA.
- Cities (`cities`, text): One or more cities, separated by commas, such as San Francisco, New York.
- Industries (`industries`, list): Only companies in any of these industries. One or more of: `1` (Aerospace and Defense), `2` (Agriculture and Forestry), `3` (Automotive), `4` (Banks), `5` (Chemicals), `6` (Civic, Non-Profit and Membership Groups), `7` (Computer Hardware), `8` (Computer Software), `9` (Construction and Building Materials), `10` (Consumer Product Manufacturing), and 20 more.
- Business types (`business_types`, list): Only these kinds of organization. One or more of: `public`, `private`, `school`, `government`, `organization`.
- Company status (`company_status`, list): Only companies in these states, such as Operating. One or more of: `operating`, `non-operating` (Not operating), `acquired`, `liquidating`, `outOfBusiness` (Out of business), `unassigned`.
- Fortune ranking (`fortune_ranking`, text): Only Fortune 500 or Fortune 1000 companies. One of: `fortune500` (Fortune 500), `fortune1000` (Fortune 1000).
- Business structure (`business_structure`, text): Only global parents, subsidiaries, branches and so on. One of: `globalParent` (Global parent), `subsidiary`, `branch`, `independent`, `group`, `uncategorized`.
- Regions (`regions`, list): Only companies in these parts of the world. One or more of: `northamerica` (North America), `europe`, `asia`, `middleeast` (Middle East), `africa`, `oceania`, `southamerica` (South America).
- Fewest employees (`min_employees`, number): Only companies with at least this many. At least 0.
- Most employees (`max_employees`, number): Only companies with at most this many. At least 0.
- Lowest revenue (millions) (`min_revenue`, number): Only companies with at least this yearly revenue, in millions of US dollars. At least 0.
- Highest revenue (millions) (`max_revenue`, number): Only companies with at most this yearly revenue, in millions of US dollars. At least 0.
- Sort by (`sort_by`, text): What to sort the companies by. One of: `companyRevenue` (Revenue), `employeeCount` (Employees), `businessType` (Business type), `location`.
- Order (`sort_order`, text): Ascending or descending. One of: `asc` (Ascending), `desc` (Descending).
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 50. Defaults to 10. From 1 to 50.

**Outputs**

- `companies` (list): The companies found, each with its companyId
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `total_count` (number): How many there are in all, across every page

**Example output**

```json
{
  "companies": [
    {
      "city": "Redmond",
      "companyId": 726263,
      "country": "US",
      "name": "Example Software Inc.",
      "state": "WA"
    }
  ],
  "page": 1,
  "page_size": 10,
  "total_count": 1
}
```

### Search contacts

Find people by name, job title, level or function, at given companies or a company's website, by country or industry. Gets one page of up to 50 with their contact ids, but not their emails or phones: get those with 'Get contact'. Needs the B2B API; uses no credits.

**Inputs**

- First name (`first_name`, text): The person's first name.
- Last name (`last_name`, text): The person's last name.
- Email (`email`, text): The person's email address.
- Job titles (`titles`, list): Job titles to look for, one per row, such as Marketing Director.
- Company IDs (`company_ids`, list): Only people at these companies: Demandbase company ids, one per row, from 'Search companies' or an earlier step.
- Company name (`company_name`, text): Only people at a company of this name.
- Company website (`company_website`, text): Only people at the company with this web domain, such as demandbase.com.
- Company country (`company_country`, text): Only people at companies in this country. One of: `68` (Afghanistan), `1` (Ahvenanmaan Laani), `120` (Albania), `109` (Algeria), `2` (American Samoa), `114` (Andorra), `121` (Angola), `3` (Anguilla), `4` (Antarctica), `5` (Antigua and Barbuda), and 243 more.
- Person's country (`contact_country`, text): Only people who are in this country. One of: `68` (Afghanistan), `1` (Ahvenanmaan Laani), `120` (Albania), `109` (Algeria), `2` (American Samoa), `114` (Andorra), `121` (Angola), `3` (Anguilla), `4` (Antarctica), `5` (Antigua and Barbuda), and 243 more.
- Job levels (`job_levels`, list): Only people at these levels, such as Director or C Level. One or more of: `0` (Board Member), `1` (C Level), `2` (Senior Executive), `3` (Vice President), `4` (Director), `5` (Manager), `8` (Lead & Senior), `6` (Others), `9` (Mid & Entry).
- Job functions (`job_functions`, list): Only people in these functions, such as Marketing. One or more of: `1` (Academics), `2` (Accounting), `3` (Administration), `4` (Business Development), `5` (Construction Engineering), `6` (Consulting), `7` (Customer Support), `8` (Human Resources), `9` (Information Technology), `10` (Investment Management), and 14 more.
- Industries (`industries`, list): Only companies in any of these industries. One or more of: `1` (Aerospace and Defense), `2` (Agriculture and Forestry), `3` (Automotive), `4` (Banks), `5` (Chemicals), `6` (Civic, Non-Profit and Membership Groups), `7` (Computer Hardware), `8` (Computer Software), `9` (Construction and Building Materials), `10` (Consumer Product Manufacturing), and 20 more.
- Fewest employees (`min_employees`, number): Only companies with at least this many. At least 0.
- Most employees (`max_employees`, number): Only companies with at most this many. At least 0.
- Only with an email (`email_required`, true/false): Only people Demandbase has an email for.
- Only with a phone (`phone_required`, true/false): Only people Demandbase has a phone number for.
- Lowest data quality (`min_contact_quality_score`, text): Only people whose details Demandbase rates at least this well. One of: `A+` (A+ (best)), `A` (A or better), `B` (B or better), `C` (C or better).
- Sort by (`sort_by`, text): What to sort the people by. One of: `companyName` (Company name), `title` (Job title), `active` (Still in the job).
- Order (`sort_order`, text): Ascending or descending. One of: `asc` (Ascending), `desc` (Descending).
- Page (`page`, number): Which page to get, from 1. Defaults to 1. At least 1.
- Page size (`per_page`, number): How many to get on a page, 1 to 50. Defaults to 10. From 1 to 50.

**Outputs**

- `contacts` (list): The people found, each with dbPersonDetails and employmentDetails
- `page` (number): This page's number, from 1
- `page_size` (number): How many a page holds
- `total_count` (number): How many there are in all, across every page

**Example output**

```json
{
  "contacts": [
    {
      "dbPersonDetails": {
        "city": "Seattle",
        "country": "United States",
        "dbPersonId": 15568398,
        "firstName": "Jamie",
        "lastName": "Taylor"
      },
      "employmentDetails": {
        "active": true,
        "companyId": 726263,
        "companyName": "Example Software Inc.",
        "contactId": 17864319,
        "contactQualityScore": "A",
        "hasEmail": true,
        "hasPhone": true,
        "jobFunctions": [
          {
            "id": "14",
            "name": "Marketing"
          }
        ],
        "jobLevels": [
          {
            "id": "3",
            "name": "Vice President"
          }
        ],
        "titles": [
          "Vice President, Marketing"
        ]
      }
    }
  ],
  "page": 1,
  "page_size": 10,
  "total_count": 1
}
```

### Start export

Export your Demandbase accounts, people, opportunities or activities with the fields you pick, such as an account's journey stage, engagement minutes and scores, to a file. Demandbase builds it in a job: get the file's link with 'Get export job' or the 'Export finished' trigger. Needs the Data Export API.

**Inputs**

- Records (`entity_type`, text, required): What to export. One of: `account` (Accounts), `person` (People), `opportunity` (Opportunities), `activity` (Activities).
- Fields (`fields`, list, required): The fields to put in the file, such as an account's journey stage, engagement minutes or scores. Pick what to export first, or give field names such as {Account}.name.
- Export name (`job_name`, text): A name for the export. Defaults to Lodol and the records.
- From (`from_date`, date): Only records from this day on, for activities and similar.
- To (`to_date`, date): Only records up to this day.
- Account list IDs (`account_list_ids`, list): Only accounts in these lists, one list id per row, from 'Export account lists'. Only when Records is Accounts.
- Person list IDs (`person_list_ids`, list): Only people in these lists, one list id per row. Only when Records is People.
- Most records (`max_records`, number): The most records to export. At least 1.
- File format (`file_format`, text): JSON or CSV. Defaults to JSON. One of: `JSON`, `CSV`.

**Outputs**

- `job` (object): The export job. Follow it with 'Get export job' until it is finished.

**Example output**

```json
{
  "job": {
    "createdAt": "2026-11-02T16:43:57.378Z",
    "entityType": "account",
    "jobId": "dcb34525-2baa-4f54-8c11-9e6175ecbc74",
    "jobName": "Lodol account export",
    "jobStatus": "accepted"
  }
}
```

### Update keyword set

Rename a keyword set, mark it competitive or not, or add and remove keywords and seed pages. Needs the Intent API.

**Inputs**

- Keyword set (`keyword_set_id`, text, required): The keyword set. Pick one, or give its id from an earlier step.
- New name (`name`, text): A new name. Leave empty to keep it.
- Competitive (`competitor`, text): Whether the set is about competitors. One of: `unchanged` (Leave as is), `competitor` (Competitive), `not_competitor` (Not competitive). Default: `unchanged`.
- Keywords to add (`add_keywords`, list): Keywords to add, one per row.
- Keywords to remove (`remove_keywords`, list): Keywords to remove, one per row.
- Seed pages to add (`add_seed_urls`, list): Web pages to add, one https address per row.
- Seed pages to remove (`remove_seed_urls`, list): Web pages to remove, one address per row.

**Outputs**

- `keyword_set` (object): The keyword set as it is now

**Example output**

```json
{
  "keyword_set": {
    "createdAt": "2026-08-20T09:14:22Z",
    "id": 9427,
    "isCompetitor": false,
    "keywords": [
      {
        "createdAt": "2026-08-20T09:14:22Z",
        "id": 551201,
        "keyword": "zero trust",
        "updatedAt": "2026-08-20T09:14:22Z"
      }
    ],
    "name": "Cloud Security Vendors",
    "seedUrls": [
      {
        "createdAt": "2026-08-20T09:14:22Z",
        "id": 8801,
        "seedUrl": "https://example.com/security"
      }
    ],
    "updatedAt": "2026-08-20T09:20:41Z"
  }
}
```

### Update subscription

Add or remove the companies or people a subscription watches, or change its name, frequency, fields, news categories or webhook. Demandbase makes the change in a job. Needs the B2B API.

**Inputs**

- Subscription (`subscription_id`, text, required): The subscription. Pick one, or give its id from an earlier step.
- Watches (`subscription_type`, text, required): What the subscription watches, as it was created. One of: `company` (Company changes), `companyNews` (Company news), `dbPerson` (Person changes), `companyFamilyTree` (Company family tree changes).
- Companies to add (`add_company_ids`, list): Demandbase company ids to start watching, one per row. Only when Watches is Company changes, Company news or Company family tree changes.
- Companies to remove (`remove_company_ids`, list): Demandbase company ids to stop watching, one per row. Only when Watches is Company changes, Company news or Company family tree changes.
- People to add (`add_person_ids`, list): Demandbase person ids to start watching, one per row. Only when Watches is Person changes.
- People to remove (`remove_person_ids`, list): Demandbase person ids to stop watching, one per row. Only when Watches is Person changes.
- New name (`name`, text): A new name. Leave empty to keep it.
- New description (`description`, text): A new description. Leave empty to keep it.
- Check every (`frequency_every`, number): How many of the unit to wait between checks, such as 7 for every 7 days. The shortest is 1 day for companies and people, 15 minutes for news and 1 week for family trees. At least 1.
- Unit (`frequency_unit`, text): The unit of 'Check every'. Defaults to days. One of: `d` (Days), `w` (Weeks), `m` (Months), `h` (Hours), `M` (Minutes).
- Company fields to watch (`company_fields`, list): Alert when any of these change. Leave empty to watch every field. Only when Watches is Company changes. One or more of: `all` (Any field), `name`, `activeStatus` (Active status), `companyStatus` (Company status), `companyType` (Company type), `businessStructure` (Business structure), `revenue`, `revenueRange` (Revenue range), `employees`, `employeeRange` (Employee range), and 12 more.
- Person fields to watch (`person_fields`, list): Alert when any of these change, such as a new job. Leave empty to watch every field. Only when Watches is Person changes. One or more of: `all` (Any field), `newEmployment` (New job), `titles` (Job titles), `active` (Still in the job), `name`, `email`, `phone`, `executiveMobileNo` (Mobile number), `linkedInHandle` (LinkedIn), `twitterHandle` (X (Twitter)), and 6 more.
- News categories (`news_categories`, list): Only alert on news in these categories. Leave empty for every category. Only when Watches is Company news. One or more of: `LEADERSHIP_CHANGES` (Leadership Changes), `NEW_OFFERINGS` (New Offerings), `ACQUISITIONS`, `PARTNERSHIPS`, `EXPANDING_OPERATIONS` (Expanding Operations), `COST_CUTTING` (Cost Cutting), `OUTPERFORMING`, `UNDERPERFORMING`, `COMPANY_PRESENTATION` (Company Presentation), `LITIGATION`, and 8 more.
- Webhook address (`webhook_url`, text): An https address of your own for Demandbase to post each alert to. It must answer Demandbase's check first. Leave empty to read alerts in Lodol instead.
- Signing secret (`signing_secret`, text): A secret Demandbase signs each webhook post with, up to 500 characters.

**Outputs**

- `job` (object): The job Demandbase runs the change in. Its subscriptionId is filled in once the job finishes; read it with 'Get subscription job'.

**Example output**

```json
{
  "job": {
    "createdAt": "2026-11-02T09:00:42.620Z",
    "invalidIds": [],
    "jobId": "39ddf756-c04e-465c-b8c1-8d2c2be0abed",
    "jobStatus": "accepted",
    "jobType": "notificationSubscriptionUpdate",
    "message": "",
    "subscriptionId": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
    "subscriptionType": "company",
    "totalEntitiesProcessed": 2
  }
}
```
