Enrich Person and Company
clearbit.enrich_combined
ActionCRM & salesconnection required
Calls the Clearbit API with the connection's credentials.
Look up a person and their employer in one call, so a lead's profile and their company record arrive together.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Clearbit
- Secret shape
- the secret API key (sk_…), or {"api_key": "…"}
- Config it needs
- stream, suppression, webhook_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
13 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
email The email address to look up. | string | Yes | — | email format | — |
given_name The person's first name, which improves the match rate. | string | No | — | — | — |
family_name The person's last name; passing it is strongly recommended. | string | No | — | — | — |
ip_address The person's IP address; passing it is strongly recommended. | string | No | — | — | — |
location The city or country where the person resides. | string | No | — | — | — |
company The name of the person's employer. | string | No | — | — | — |
company_domain The website domain of the person's employer. | string | No | — | — | — |
linkedin The person's LinkedIn profile URL. | string | No | — | — | — |
twitter The person's Twitter handle. | string | No | — | — | — |
facebook The person's Facebook profile URL. | string | No | — | — | — |
subscribe Subscribe to future changes to this person's record. | boolean | No | — | — | — |
webhook_id Your own identifier, echoed back on the webhook for a queued lookup. | string | No | — | — | — |
stream Hold the request open until Clearbit finishes instead of accepting a queued answer. Overrides the connection's own 'stream' setting. | boolean | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
status One of 'found', 'queued' (Clearbit is still looking) or 'not_found'. | string | — |
found True when Clearbit returned a record. | boolean | — |
pending True when the lookup was queued (HTTP 202); retry later or use a webhook. | boolean | — |
person The Clearbit person record, or null. | object | — |
company The employer's Clearbit record, or null. | object | — |
{
"company": {},
"found": false,
"pending": false,
"person": {},
"status": ""
}Notes
- Clearbit may know the company but not the person; 'found' is true when either half came back, so check 'person' and 'company' separately.
Solutions with Clearbit
See Enrich Person and Company run in a workflow.
In a technical demo we add the Clearbit connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.