Appearance
Clearbit
undefined
| Detail | Value |
|---|---|
| Category | Data |
| Base URL | https://company.clearbit.com |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | clearbit |
Using Clearbit in a workflow
- Go to Connections and click New Connection.
- Pick Clearbit from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Company Lookup |
GET | Person Lookup |
GET | Combined |
GET | Search |
GET | Name to Domain |
GET | Reveal |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Company Lookup
| Detail | Value |
|---|---|
| Operation ID | company_lookup_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Clearbit connection from the Connection dropdown.
- In the Operation dropdown, select
company_lookup_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Clearbit API reference.
GET
Person Lookup
| Detail | Value |
|---|---|
| Operation ID | person_lookup_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Clearbit connection from the Connection dropdown.
- In the Operation dropdown, select
person_lookup_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Clearbit API reference.
GET
Combined
| Detail | Value |
|---|---|
| Operation ID | combined_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Clearbit connection from the Connection dropdown.
- In the Operation dropdown, select
combined_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Clearbit API reference.
GET
Search
| Detail | Value |
|---|---|
| Operation ID | search_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Clearbit connection from the Connection dropdown.
- In the Operation dropdown, select
search_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Clearbit API reference.
GET
Name to Domain
| Detail | Value |
|---|---|
| Operation ID | name_to_domain_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Clearbit connection from the Connection dropdown.
- In the Operation dropdown, select
name_to_domain_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Clearbit API reference.
GET
Reveal
| Detail | Value |
|---|---|
| Operation ID | reveal_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Clearbit connection from the Connection dropdown.
- In the Operation dropdown, select
reveal_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Clearbit API reference.