Clearbit n8n integrationAutomate Clearbit with n8n.
An email address lands in your workflow, and two seconds later you know who sent it and where they work. The Clearbit n8n integration covers 3 operations across 2 resources: autocomplete a company name, enrich a company from its domain, enrich a person from an email. Made for sales and ops teams that qualify inbound.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Clearbit n8n integration give you?
The Clearbit node is an app node shipped with n8n. It calls the Clearbit API with your API key and returns enriched data inside a workflow, so a raw signup becomes a qualified record without anyone opening a browser tab. Three operations, two resources: company.autocomplete guesses a company from a fragment of its name, company.enrich starts from a domain, and person.enrich starts from an email address.
Start with the one that matches what you already have. You hold an email? Go straight to person.enrich. You hold a domain? company.enrich. You hold a half typed company name from a form? company.autocomplete first, then chain into the company lookup with the domain it gives back.
The most common build is inbound qualification. A demo request arrives through a n8n Webhook, which is a URL that a third party service calls to push data into your workflow. The Email field of the form feeds person.enrich, and the enriched item goes straight into HubSpot or Pipedrive. The sales rep opens a record that is already filled in rather than a bare email.
Second build, the pre call briefing. A Schedule Trigger runs every morning, reads the day's meetings, and passes each attendee domain to company.enrich. The result is posted to Slack or sent through Gmail before the call. The three public templates that use this node, 2116, 2124 and 2125, follow that shape.
Third build, cleaning a list you already own. A sheet of company names typed by humans is a mess of abbreviations. Loop the rows of Google Sheets through company.autocomplete, keep the domain it returns, and you have a key you can join on later.
One thing to keep in mind when you design the workflow: the catalogue of this node is these 3 operations. Anything else you want from the Clearbit API goes through the HTTP Request node, which calls any endpoint while reusing the same credential through predefined authentication. And a field marked required stops the node when it is empty, so branch on a missing email before the enrichment rather than after it. If you want the wider picture of the platform before committing, the n8n review covers it.
How do you connect Clearbit to n8n?
- 01
Create the Clearbit account
The credential starts on the Clearbit side. Create an account at clearbit.com, then open the dashboard documentation to find where API keys are created and viewed. That page is the only place the key exists in readable form, so copy it into a password manager before you leave it. Nothing to install on the n8n side: the node ships with n8n, on n8n Cloud and on a self hosted instance alike.
- 02
Register the API key in n8n
In n8n, open the Credentials menu and create a Clearbit credential. The node supports one authentication method, API key, so there is a single field to fill: API Key, where you paste the value from the Clearbit dashboard. A credential is created once and reused across every workflow of the instance, which means the next Clearbit node you drop on the canvas already finds it in its dropdown list.
- 03
Run one enrichment to check
Drop a Clearbit node, pick the Person resource and the Enrich operation, and type a real work email in the Email field, the one the placeholder
name@email.comis asking for. Execute the node alone. You get an item back and you know the key works. Only then wire the trigger in front of it, because debugging authentication and workflow logic at the same time doubles the guesswork.
What can the Clearbit node do?
The Clearbit node exposes 3 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Company
2 operationsAutocomplete a company
company.autocompleteWhat you see in n8n
Notes & use cases
Feed a fragment of a company name and the operation returns matching companies, with the logo and the domain of each. Its job is to turn something a human typed into a domain a machine can use.
Key parameters
- Name: required, the partial name of the company. It usually comes from the previous node as an expression such as
{{ $json.name }}, an expression being the way n8n reads a field of the incoming item.
Enrich a company
company.enrichWhat you see in n8n
Notes & use cases
Give the operation a domain. It looks up the person and company data attached to it, then returns one enriched item for the rest of the workflow to consume.
Key parameters
- Domain: required, the domain to look up, most often
{{ $json.domain }}coming from the autocomplete step. - Additional Fields: an optional collection of 4 hints you already hold, Company Name, Facebook, Linkedin and Twitter, each the name or the social URL of the company.
Person
1 operationEnrich a person
person.enrichWhat you see in n8n
Notes & use cases
From a single email address, this one looks up the person and the company data behind it. It is the entry point of most inbound workflows, because an email is usually the first thing any signup form or webhook hands you.
Key parameters
- Email: required, the email address to look up, in the shape of the
name@email.complaceholder, typically{{ $json.email }}. - Family Name and IP Address: two of the 9 Additional Fields, singled out because the documentation recommends passing them whenever you have them. Given Name, Company, Company Domain and Location sit in the same collection.
Need help automating Clearbit with n8n?
A person reads every message.