# Bombora

> Use Bombora's Company Surge intent data: find companies researching your topics, build and tune signal definitions, manage account lists, and start workflows when companies surge or lists change.

App · 20 actions. Web page: https://docs.lodol.com/docs/integrations/bombora

## Actions

### Add accounts

Add companies to a Manual account list by domain, or with your own id and attributes. An account already in the list is updated.

**Inputs**

- Account list (`account_list_id`, text, required): A Manual account list (the only kind whose accounts you change). Pick one, or give its id from an earlier step.
- Domains (`domains`, list): Company domains to add, such as bombora.com.
- Accounts with details (`accounts`, list): Accounts with your own id or attributes, such as [{"domain": "bombora.com", "id": "A-1", "attributes": {"rank": "1"}}]. Use this, domains, or both.

**Outputs**

- `account_list_id` (text): The account list's id
- `accounts` (list): The accounts sent
- `count` (number): How many accounts were sent
- `skipped_duplicates` (list): Repeats left out, since Bombora refuses a request that repeats one

**Example output**

```json
{
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2",
  "accounts": [
    {
      "attributes": {},
      "domain": "bombora.com",
      "id": "A-1"
    }
  ],
  "count": 1,
  "skipped_duplicates": []
}
```

### Create account list

Create an account list: Manual (you add accounts), Derived (a filter of another list), Surge (companies showing intent) or Visitor Insights (companies visiting your website).

**Inputs**

- Name (`name`, text, required): A name, up to 255 characters.
- Type (`list_type`, text, required): Manual lists hold the accounts you add; Derived lists filter another list; Surge lists hold the companies showing intent on a signal definition or topics; Visitor Insights lists hold companies that visited your website (needs Bombora to enable Visitor Insights). One of: `Manual` (Manual: accounts you add), `Derived` (Derived: filtered from another list), `Surge` (Surge: companies showing intent), `VisitorInsights` (Visitor Insights: companies visiting your site).
- Description (`description`, text): A description, up to 2,048 characters.
- Parent list (`parent_account_list_id`, text): For a Derived list: the list it filters. Only when Type is Derived: filtered from another list.
- Signal definition (`signal_definition_id`, text): For a Surge list: the companies surging on this signal definition. Use this or topics. Only when Type is Surge: companies showing intent.
- Topics (`topics`, list): For a Surge list: the companies surging on these topics, up to 50. Use these or a signal definition. Only when Type is Surge: companies showing intent.
- Visited within (days) (`visited_within_days`, number): For a Visitor Insights list: companies that visited in the last 1 to 180 days. Only when Type is Visitor Insights: companies visiting your site. From 1 to 180.
- Minimum score (`min_score`, number): For a Surge list: only companies scoring at least this, 0 to 100. Only when Type is Surge: companies showing intent. From 0 to 100.
- Headquarters countries (`countries`, list): Only companies headquartered in one of these countries.
- Company sizes (`company_sizes`, list): Only companies of one of these sizes, by employees.
- Industries (`industries`, list): Only companies in one of these industries.
- Custom filter (`custom_filter`, object): Any other condition, in Bombora's own form, joined to the fields above with "and". For example {"a": "domain", "neq": "*.edu"} leaves out .edu domains; {"or": [...]} joins conditions with "or".

**Outputs**

- `account_list` (object): What was sent: its type, name and specification
- `account_list_id` (text): The account list's id

**Example output**

```json
{
  "account_list": {
    "metadata": {
      "name": "Target accounts"
    },
    "specification": {},
    "type": "Manual"
  },
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2"
}
```

### Create signal definition

Create a signal definition that Bombora's AI fills with topics from a company domain, keywords or web pages. It is Processing until the topics are chosen; 'Wait for signal definition' waits for that.

**Inputs**

- Name (`name`, text, required): A name, up to 255 characters.
- Description (`description`, text): A description, up to 2,048 characters.
- Company domain (`domain`, text): The company's main web domain, such as example.com. Give this, keywords or web pages.
- Keywords (`keywords`, list): Words that describe the product or service.
- Web pages (`urls`, list): Pages about the company, product or service, each starting with https://.
- Partner client ID (`partner_client_id`, text): Your own client's id, for Bombora channel partners, who must give one. Leave empty otherwise.

**Outputs**

- `metadata` (object): The name and description sent
- `product_definition` (object): What it is built from
- `signal_definition_id` (text): The signal definition's id
- `status` (text): Processing, at first

**Example output**

```json
{
  "metadata": {
    "clientId": "",
    "description": "Companies researching Product X.",
    "name": "Signal for Product X"
  },
  "product_definition": {
    "domain": "example.com",
    "keywords": [
      "manufacturing",
      "communications"
    ],
    "urls": [
      "https://www.example.com/product"
    ]
  },
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b",
  "status": "Processing"
}
```

### Delete account list

Delete an account list. Bombora refuses while another list is derived from it.

**Inputs**

- Account list (`account_list_id`, text, required): The account list. Pick one, or give its id from an earlier step.

**Outputs**

- `account_list_id` (text): The account list's id
- `deleted` (true/false): Always true once deleted

**Example output**

```json
{
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2",
  "deleted": true
}
```

### Delete signal definition

Delete a signal definition.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `signal_definition_id` (text): The signal definition's id

**Example output**

```json
{
  "deleted": true,
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b"
}
```

### Get account list

Get an account list's type, name, number of accounts and what it is built from (its parent, signal or filter).

**Inputs**

- Account list (`account_list_id`, text, required): The account list. Pick one, or give its id from an earlier step.

**Outputs**

- `account_list` (object): The account list
- `account_list_id` (text): The account list's id

**Example output**

```json
{
  "account_list": {
    "accountsLastModified": "2026-01-27T05:06:07",
    "metadata": {
      "accountTotal": 100,
      "description": "The accounts we sell to",
      "name": "Target accounts",
      "pendingUpdate": false
    },
    "specification": {},
    "type": "Manual"
  },
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2"
}
```

### Get intent data

Get the companies showing Company Surge intent on a signal definition or topics, with their scores, filtered by score, country, size, industry or account list. Gets one page; to see more, run it again with the next page token it gives.

**Inputs**

- Signal definition (`signal_definition_id`, text): Read intent for this signal definition. Use this or topics, not both.
- Topics (`topics`, list): Up to 50 intent topics, by name. Use these or a signal definition, not both.
- Details to return (`attributes`, list): What each row holds. Defaults to the domain, score and score label. Choosing Topic, or a research place, gives one row per company and that topic or place. One or more of: `domain`, `topic` (Topic (one row per company and topic)), `researchCountry` (Research country (one row per country)), `researchState` (Research state, US and Canada (one row per state)), `researchMetro` (Research metro area (one row per metro area)), `score`, `scoreLabel` (Score label), `topicsCount` (Number of topics), `topics` (Topics with their scores), `areasOfInterest` (Areas of interest), and 7 more.
- Minimum score (`min_score`, number): Only companies whose intent score is at least this, 0 to 100. From 0 to 100.
- Score labels (`score_labels`, list): Only companies with one of these labels, such as Strong.
- Headquarters countries (`countries`, list): Only companies headquartered in one of these countries.
- Company sizes (`company_sizes`, list): Only companies of one of these sizes, by employees.
- Industries (`industries`, list): Only companies in one of these industries.
- Only accounts in list (`account_list_id`, text): Only companies in this account list.
- Custom filter (`custom_filter`, object): Any other condition, in Bombora's own form, joined to the fields above with "and". For example {"a": "domain", "neq": "*.edu"} leaves out .edu domains; {"or": [...]} joins conditions with "or".
- Rows per page (`limit`, number): How many rows to return, 1 to 10,000. Defaults to 100. Bombora may return fewer to keep a page under 10 MB. From 1 to 10000.
- Next page token (`page_token`, text): The 'next_page_token' from an earlier run of this step, to read the page after it. The other fields are then ignored.

**Outputs**

- `count` (number): How many
- `next_page_token` (text): Give this back as 'Next page token' for the next page; empty on the last
- `records` (list): One row per company (or per company and topic or place), holding the details asked for

**Example output**

```json
{
  "count": 1,
  "next_page_token": "nSA21gW",
  "records": [
    {
      "domain": "nasa.gov",
      "score": 95,
      "scoreLabel": "Strong"
    }
  ]
}
```

### Get product definition

Get what a signal definition was built from: the company domain, keywords and web pages.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.

**Outputs**

- `product_definition` (object): The domain, keywords and pages
- `signal_definition_id` (text): The signal definition's id

**Example output**

```json
{
  "product_definition": {
    "domain": "example.com",
    "keywords": [
      "manufacturing",
      "communications"
    ],
    "urls": [
      "https://www.example.com/product"
    ]
  },
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b"
}
```

### Get signal definition

Get a signal definition's name, description and weighted topics.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.

**Outputs**

- `metadata` (object): Its name and description
- `signal_definition_id` (text): The signal definition's id
- `topic_count` (number): How many
- `topics` (list): Its topics and weightings

**Example output**

```json
{
  "metadata": {
    "clientId": "",
    "description": "Companies researching Product X.",
    "name": "Signal for Product X"
  },
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b",
  "topic_count": 1,
  "topics": [
    {
      "id": 1333532,
      "name": "Local Government",
      "weighting": 0.9
    }
  ]
}
```

### List account domains

List every distinct company domain in an account list.

**Inputs**

- Account list (`account_list_id`, text, required): The account list. Pick one, or give its id from an earlier step.

**Outputs**

- `account_list_id` (text): The account list's id
- `count` (number): How many
- `domains` (list): The domains

**Example output**

```json
{
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2",
  "count": 2,
  "domains": [
    "bombora.com",
    "starbucks.com"
  ]
}
```

### List account lists

List your account lists with their type, number of accounts and when their accounts last changed.

**Inputs**

- Type (`list_type`, text): Only lists of this type. Leave empty for all. One of: `Manual` (Manual: accounts you add), `Derived` (Derived: filtered from another list), `Surge` (Surge: companies showing intent), `VisitorInsights` (Visitor Insights: companies visiting your site).

**Outputs**

- `account_lists` (list): The account lists
- `count` (number): How many

**Example output**

```json
{
  "account_lists": [
    {
      "accountTotal": 100,
      "accountsLastModified": "2026-01-27T05:06:07",
      "createdDate": "2026-01-27T05:06:07",
      "description": "The accounts we sell to",
      "id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2",
      "modifiedDate": "2026-01-29T07:03:02",
      "name": "Target accounts",
      "parentId": "",
      "pendingUpdate": false,
      "type": "Manual"
    }
  ],
  "count": 1
}
```

### List signal definitions

List your signal definitions with their status, number of topics and when each was created and changed.

**Inputs**

- Status (`status`, text): Only Available or only Processing ones. Leave empty for all. One of: `Available`, `Processing`.

**Outputs**

- `count` (number): How many
- `signal_definitions` (list): The signal definitions

**Example output**

```json
{
  "count": 1,
  "signal_definitions": [
    {
      "createdDate": "2026-06-28T00:00:00+00:00",
      "metadata": {
        "clientId": "",
        "description": "Companies researching Product X.",
        "name": "Signal for Product X"
      },
      "modifiedDate": "2026-06-28T00:00:00+00:00",
      "signalDefinitionId": "7030eb5a-311a-4608-b901-8e5d61aad86b",
      "status": "Available",
      "topicCount": 1
    }
  ]
}
```

### Remove accounts

Remove accounts from a Manual account list by id (or domain, for accounts added without an id), or remove every account and keep the empty list.

**Inputs**

- Account list (`account_list_id`, text, required): A Manual account list (the only kind whose accounts you change). Pick one, or give its id from an earlier step.
- Accounts (`account_ids`, list): The accounts to remove: the id you gave each, or its domain if you gave none.
- Remove every account (`remove_all`, true/false): Empty the list instead of removing the accounts given.

**Outputs**

- `account_list_id` (text): The account list's id
- `removed` (list): The accounts removed
- `removed_all` (true/false): Whether every account was removed

**Example output**

```json
{
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2",
  "removed": [
    "bombora.com"
  ],
  "removed_all": false
}
```

### Search accounts

Get an account list's accounts with company details Bombora knows and your own attributes, filtered by country, size, industry or a custom filter. Gets one page; to see more, run it again with the next page token it gives.

**Inputs**

- Account list (`account_list_id`, text, required): The account list. Pick one, or give its id from an earlier step.
- Details to return (`attributes`, list): What each account holds. Defaults to its id. One or more of: `domain`, `id` (Account ID), `attributes` (Your own account attributes), `company` (Company: every company detail), `company.name` (Company name), `company.industry` (Company industry), `company.size` (Company size), `company.revenue` (Company revenue), `company.hq` (Company headquarters).
- Your attributes to return (`account_attributes`, list): Names of your own attributes on the accounts to return, such as rank.
- Headquarters countries (`countries`, list): Only companies headquartered in one of these countries.
- Company sizes (`company_sizes`, list): Only companies of one of these sizes, by employees.
- Industries (`industries`, list): Only companies in one of these industries.
- Custom filter (`custom_filter`, object): Any other condition, in Bombora's own form, joined to the fields above with "and". For example {"a": "domain", "neq": "*.edu"} leaves out .edu domains; {"or": [...]} joins conditions with "or".
- Rows per page (`limit`, number): How many rows to return, 1 to 10,000. Defaults to 100. Bombora may return fewer to keep a page under 10 MB. From 1 to 10000.
- Next page token (`page_token`, text): The 'next_page_token' from an earlier run of this step, to read the page after it. The other fields are then ignored.

**Outputs**

- `account_list_id` (text): The account list's id
- `accounts` (list): The accounts, with the details asked for
- `count` (number): How many
- `next_page_token` (text): Give this back as 'Next page token' for the next page; empty on the last

**Example output**

```json
{
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2",
  "accounts": [
    {
      "attributes": {
        "rank": "1"
      },
      "company": {
        "size": "Medium-Small (50 - 199 Employees)"
      },
      "domain": "bombora.com",
      "id": "bombora.com"
    }
  ],
  "count": 1,
  "next_page_token": ""
}
```

### Search topics

Find Bombora intent topics by name, theme, category or description, or the topics most similar to some you choose.

**Inputs**

- Name contains (`name`, text): Topics whose name contains this; separate several with commas.
- Theme contains (`theme`, text): Topics whose theme contains this, such as Government.
- Category contains (`category`, text): Topics whose category contains this, such as Legal Services.
- Description contains (`description`, text): Topics whose description contains this.
- Topics (`topic_ids`, list): Particular topics, picked or by id.
- Match (`match`, text): Whether a topic must match any or all of the fields given. One of: `any` (Any of the filters (default)), `all` (All of the filters).
- Similar to (`similar_to`, list): Find the topics most like these instead. Can't be used with the fields above or paging.
- Most similar topics (`max_topics`, number): With 'Similar to': how many to return. Defaults to 50; 0 for all. From 0 to 50000.
- Page (`page`, number): Which page of results, from 1. Defaults to 1. At least 1.
- Page size (`page_size`, number): Topics per page, 1 to 50,000. Defaults to 50. From 1 to 50000.

**Outputs**

- `count` (number): How many
- `page` (number): This page's number, from 1
- `page_size` (number): Topics per page
- `topics` (list): The topics found
- `total_items` (number): Topics matching, on every page
- `total_pages` (number): How many pages there are

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "page_size": 50,
  "topics": [
    {
      "category": "Other",
      "description": "The administration of a particular town, county, or district.",
      "id": 1333532,
      "name": "Local Government",
      "theme": "Government"
    }
  ],
  "total_items": 1,
  "total_pages": 1
}
```

### Set signal definition topics

Replace a signal definition's topics, or add or remove some, optionally setting their weighting. Topics kept keep their weighting unless one is given.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.
- Topics (`topic_ids`, list, required): The intent topics. Pick them, or give their ids (numbers).
- Change (`mode`, text): Replace the topics, add these, or remove these. Defaults to replace. One of: `replace` (Replace the topics with these), `add` (Add these topics), `remove` (Remove these topics). Default: `replace`.
- Weighting (`weighting`, number): How much these topics count, 0 to 1, such as 0.9. From 0 to 1.

**Outputs**

- `signal_definition_id` (text): The signal definition's id
- `topic_count` (number): How many
- `topics` (list): The topics sent, with their weightings

**Example output**

```json
{
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b",
  "topic_count": 1,
  "topics": [
    {
      "id": 1333532,
      "weighting": 0.9
    }
  ]
}
```

### Update account list

Change an account list's name, description, Visitor Insights look-back or filter. Fields left empty keep their value; a list's type and parent can't change.

**Inputs**

- Account list (`account_list_id`, text, required): The account list. Pick one, or give its id from an earlier step.
- Name (`name`, text): A new name. Leave empty to keep it.
- Description (`description`, text): A new description. Leave empty to keep it.
- Visited within (days) (`visited_within_days`, number): For a Visitor Insights list: a new look-back, 1 to 180 days. From 1 to 180.
- Minimum score (`min_score`, number): For a Surge list: only companies scoring at least this. Any filter field given replaces the list's whole filter. From 0 to 100.
- Headquarters countries (`countries`, list): Only companies headquartered in one of these countries.
- Company sizes (`company_sizes`, list): Only companies of one of these sizes, by employees.
- Industries (`industries`, list): Only companies in one of these industries.
- Custom filter (`custom_filter`, object): Any other condition, in Bombora's own form, joined to the fields above with "and". For example {"a": "domain", "neq": "*.edu"} leaves out .edu domains; {"or": [...]} joins conditions with "or".

**Outputs**

- `account_list` (object): The account list now
- `account_list_id` (text): The account list's id

**Example output**

```json
{
  "account_list": {
    "accountsLastModified": "2026-01-27T05:06:07",
    "metadata": {
      "accountTotal": 100,
      "description": "The accounts we sell to",
      "name": "Target accounts",
      "pendingUpdate": false
    },
    "specification": {},
    "type": "Manual"
  },
  "account_list_id": "3e19d5f7-98f0-4c76-a859-c8707b57d9d2"
}
```

### Update product definition

Change the domain, keywords or web pages a signal definition is built from. Bombora then rebuilds it, replacing its topics. Fields left empty keep their value.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.
- Company domain (`domain`, text): The company's main web domain, such as example.com. Leave empty to keep it.
- Keywords (`keywords`, list): Words that describe the product or service.
- Web pages (`urls`, list): Pages about the company, product or service, each starting with https://.

**Outputs**

- `product_definition` (object): What it is built from now
- `signal_definition_id` (text): The signal definition's id
- `status` (text): Processing, until rebuilt

**Example output**

```json
{
  "product_definition": {
    "domain": "example.com",
    "keywords": [
      "manufacturing",
      "communications"
    ],
    "urls": [
      "https://www.example.com/product"
    ]
  },
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b",
  "status": "Processing"
}
```

### Update signal definition

Change a signal definition's name, description or partner client ID. Fields left empty keep their value.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.
- Name (`name`, text): A new name. Leave empty to keep it.
- Description (`description`, text): A new description. Leave empty to keep it.
- Partner client ID (`partner_client_id`, text): Your own client's id, for Bombora channel partners, who must give one. Leave empty otherwise.

**Outputs**

- `metadata` (object): Its name and description now
- `signal_definition_id` (text): The signal definition's id

**Example output**

```json
{
  "metadata": {
    "clientId": "",
    "description": "Companies researching Product X.",
    "name": "Product X buyers"
  },
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b"
}
```

### Wait for signal definition

Wait until Bombora has finished building a signal definition (its status is Available), checking each minute. Use it after creating one or changing its product definition.

**Inputs**

- Signal definition (`signal_definition_id`, text, required): The signal definition. Pick one, or give its id from an earlier step.

**Outputs**

- `signal_definition` (object): The signal definition, now ready
- `signal_definition_id` (text): The signal definition's id
- `status` (text): Available

**Example output**

```json
{
  "signal_definition": {
    "createdDate": "2026-06-28T00:00:00+00:00",
    "metadata": {
      "clientId": "",
      "description": "Companies researching Product X.",
      "name": "Signal for Product X"
    },
    "modifiedDate": "2026-06-28T00:00:00+00:00",
    "signalDefinitionId": "7030eb5a-311a-4608-b901-8e5d61aad86b",
    "status": "Available",
    "topicCount": 1
  },
  "signal_definition_id": "7030eb5a-311a-4608-b901-8e5d61aad86b",
  "status": "Available"
}
```
