Reference · Tools
Clearbit
Enrich company and person data using the Clearbit API for sales intelligence and lead scoring.
The Clearbit node connects your BusyBot workflows to the Clearbit API for three operations: look up a person's social and professional profile by email, retrieve detailed company data by domain, or autocomplete a company name to get its domain and logo. A typical use is enriching inbound form submissions automatically before they reach your CRM.
- Node type
- Action
- Parameters
- 9
- Outputs
- Output, Error
- Credentials
- Clearbit API
Clearbit
Enrich company and person data for sales intelligence and lead scoring.
Overview
Clearbit is a data enrichment service. This tool supports three operations: (1) Person Enrich — look up social and professional information by email address, (2) Company Enrich — look up detailed company data by domain, and (3) Company Autocomplete — auto-complete company names and get domain/logo.
Category: Sales
Tool Name: clearbit
Version: 1
Appearance: Icon: lucide-Search | Color: #4DA6FF
Node Type
Action — processes input items and produces output
Input / Output
| Direction | Port(s) |
|---|---|
| Input | Input |
| Output | Output, Error |
Credentials
This tool requires Clearbit API credentials. See the Credentials Guide for setup instructions.
Resources
| Resource | Value |
|---|---|
| Company | company |
| Person | person |
Operations
Which operations are available depends on the selected resource — see the parameter subsections below.
| Operation | Value | Description |
|---|---|---|
| Autocomplete | autocomplete | Auto-complete company names and retrieve logo and domain. |
| Enrich | enrich | Look up person and company data based on an email or domain. |
Parameters
Company: Enrich
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Domain | string | Yes | — | The domain to look up. |
| Additional Fields | collection | No | {} | Extra hints sent with the lookup to improve the match. |
| — Company Name | string | No | — | The name of the company. |
string | No | — | The Facebook URL for the company. | |
string | No | — | The LinkedIn URL for the company. | |
string | No | — | The Twitter handle for the company. |
Company: Autocomplete
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Name | string | Yes | — | The partial name of the company to search for. |
Person: Enrich
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
string | Yes | — | The email address to look up. | |
| Additional Fields | collection | No | {} | Extra hints sent with the lookup to improve the match. |
| — Company | string | No | — | The name of the person’s employer. |
| — Company Domain | string | No | — | The domain for the person’s employer. |
string | No | — | The Facebook URL for the person. | |
| — Family Name | string | No | — | Last name of person. Passing this is strongly recommended to improve match rates. |
| — Given Name | string | No | — | First name of person. |
| — IP Address | string | No | — | IP address of the person. Passing this is strongly recommended to improve match rates. |
string | No | — | The LinkedIn URL for the person. | |
| — Location | string | No | — | The city or country where the person resides. |
string | No | — | The Twitter handle for the person. |
All Operations
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Max Concurrency | number | No | 10 | Maximum number of items to process concurrently. |
Output Data
Clearbit’s response is merged onto the input item’s JSON — your existing fields survive and the enrichment fields are added alongside them, overwriting any key of the same name. Binary data on the input item is forwarded.
| Operation | Output items per input item |
|---|---|
company / enrich | One — the company record merged onto the item. |
person / enrich | One — the person record merged onto the item. |
company / autocomplete | One per suggestion, so a single input item fans out into several. |
An autocomplete lookup that matched nothing still produces one item, carrying your original JSON plus a marker:
{
"_noResults": true
}
Test for {{ $json._noResults }} before treating an autocomplete branch as a hit. The two enrich operations have no such marker — an empty response simply leaves the item as it arrived, so check for a field you expect (for example {{ $json.name }}) instead.
The enrichment fields themselves are whatever Clearbit returns for the lookup; the node does not rename, nest or filter them. Reference them downstream by expression, e.g. {{ $json.domain }}.
Usage Examples
- Look up company information by domain
- Enrich a lead with person data by email address
- Auto-complete company names for a search interface
- Get company metrics and social profiles from a domain
- Find a person’s employment and social data by email
Example Configuration
Enrich a company from a domain on the item:
{
"type": "clearbit",
"parameters": {
"resource": "company",
"operation": "enrich",
"domain": "{{ $json.domain }}"
}
}
Give the company lookup extra hints to improve the match:
{
"type": "clearbit",
"parameters": {
"resource": "company",
"operation": "enrich",
"domain": "{{ $json.website }}",
"additionalFields": {
"companyName": "{{ $json.company }}",
"linkedin": "{{ $json.linkedinUrl }}",
"twitter": "{{ $json.twitterHandle }}"
}
}
}
Suggest companies from a partial name typed by a user:
{
"type": "clearbit",
"parameters": {
"resource": "company",
"operation": "autocomplete",
"name": "{{ $json.query }}"
}
}
Enrich a lead by email, passing name and location to raise the match rate:
{
"type": "clearbit",
"parameters": {
"resource": "person",
"operation": "enrich",
"email": "{{ $json.email }}",
"additionalFields": {
"givenName": "{{ $json.firstName }}",
"familyName": "{{ $json.lastName }}",
"company": "{{ $json.company }}",
"companyDomain": "{{ $json.domain }}",
"location": "{{ $json.city }}"
},
"maxConcurrency": 5
}
}
Error Handling
| Mode | Behavior |
|---|---|
| stop | Halts workflow on first error |
| continue | Skips failed items, passes successful ones through |
| errorPort | Routes failed items to Error output port |
Tips
Enrich company and person data using the Clearbit API — look up companies by domain, people by email, or auto-complete company names.
Parameter Dependencies
operationoptions depend on the selectedresourcedomainis only required for company enrichmentnameis only required for company autocompleteemailis only required for person enrichmentadditionalFieldsstructure varies by resource type- All conditional parameters are hidden unless their display conditions are met
Frequently asked questions
What credential does this node require, and where do I get it?
You need a Clearbit API credential, configured in BusyBot as type `clearbitApi`. You obtain the API key from your Clearbit account dashboard. Without this credential set up, none of the three operations will run.
Which input fields are required, and do they change depending on what I'm doing?
Yes — the required field depends on the operation. `email` is only needed for Person Enrich, `domain` is only needed for Company Enrich, and `name` is only needed for Company Autocomplete. BusyBot hides each field unless the matching resource and operation are selected, so you won't see irrelevant inputs cluttering the form.
What does Company Autocomplete actually return — is it just a name match?
Company Autocomplete returns candidate company names along with their associated domain and logo. It's intended for search-as-you-type scenarios or to resolve a fuzzy company name into a canonical domain before passing it to Company Enrich.
What happens if Clearbit can't find the email or domain I submitted?
The node routes execution to its Error output rather than the standard Output. This lets you branch your workflow — for example, flagging the lead for manual review or skipping downstream CRM steps — without the whole workflow failing.
Can I retrieve extra fields beyond the defaults for person or company lookups?
Yes. Each resource type exposes an `additionalFields` parameter whose available options differ between person and company lookups. The structure of that parameter changes based on which resource you've selected, so check the fields available after picking your resource type rather than assuming they're the same across operations.
Build with the Clearbit node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Clearbit API credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.