Uplead n8n integrationAutomate Uplead with n8n.
A domain sitting in a spreadsheet is not a lead yet. The Uplead n8n integration exposes 2 operations across 2 resources: enrich a company, enrich a person. Uplead has no trigger node, so a schedule or a webhook starts the run. Built for sales ops who patch holes in a list every week.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Uplead n8n integration actually do?
The Uplead node calls the Uplead API from inside a workflow. You hand it what you already know, a company name, a domain, an email address, a first and last name, and it returns what Uplead holds, which the next node can read with an expression such as {{ $json.field }}. Two resources, Company and Person, one operation each, both named Enrich. That is the whole node, and it is enough to stop copying values between tabs by hand.
Fill a prospect list overnight. A Schedule Trigger reads the rows added to a Google Sheets tab, the Person operation enriches each one from the email column you already collected, and the result is written back next to the original row. Nobody opens a browser tab for it.
Hand the rep a file that is already filled. A company lands in HubSpot with nothing but a domain. The Company operation takes that domain, and an update node writes the returned values on the record before the first call is booked.
Qualify an inbound signup while it is still warm. A form submission hits the Webhook node, which is the n8n node that receives an HTTP call from an outside service, the Person operation enriches the email, and a Slack message drops the result in the sales channel.
One habit is worth taking on day one. Neither operation marks any field as required, so n8n will happily run the node on a form you left empty and pass the call through. An empty input is not blocked for you, which means the check belongs upstream: an IF node, or a Filter, that drops rows without an email or without a domain before they reach Uplead.
The node ships with the operations listed above. For an Uplead API endpoint that is not one of these two, the HTTP Request node calls it directly and reuses the same Uplead credential through predefined authentication, so there is no second key to store. Same workflow, same canvas, one extra node.
Worth knowing before you build: read one real response first. Run the node once with a domain you recognize, look at the output panel, and write your expressions from what you see rather than from what you assume. If you are still finding your way around expressions and credentials, the n8n training covers both.
How do you connect Uplead to n8n?
- 01
Generate the API key in Uplead
Log into your Uplead account and open Account > Profiles. The Generate New API Key button is there. API key is the only authentication method the Uplead credential supports, so there is no OAuth screen to click through and no redirect URL to paste anywhere. Copy the key once it appears and keep it handy for the next step.
- 02
Save it as an n8n credential
In n8n, open the Credentials menu, create a new Uplead credential and paste the key into the API Key field. Give it a name you will recognize later. A credential is created once and reused by every workflow on the instance, so this step happens a single time whether you run n8n Cloud or your own self-hosted instance.
- 03
Wire the node and run it once
Drop the Uplead node on the canvas and pick your credential from its dropdown list. Choose the resource, Company or Person, then the Enrich operation. Fill one field with a value you can verify, a domain you know, and execute the node on its own. The output panel shows you exactly what came back, and that is what your later expressions such as
{{ $json.field }}should point at.
What the Uplead node can do
The Uplead node exposes 2 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Company
1 operationEnrich a company
company.enrichWhat you see in n8n
Notes & use cases
Point the node at an organization and it returns what Uplead holds about it, ready for the node that follows.
Key parameters
- Company: the name of the company, for example amazon. This is the field to use when the only thing in your row is a trade name somebody typed in a form.
- Domain: the domain name, for example amazon.com. Steadier than a name when the row came from an email address, since a name can belong to several businesses.
Person
1 operationEnrich a person
person.enrichWhat you see in n8n
Notes & use cases
Turn a single identifier into a person record from Uplead, without leaving the workflow.
Key parameters
- Email: the email address, for example mbenioff@salesforce.com. The field carries the placeholder name@email.com in the node.
- First Name: the first name, Marc.
- Last Name: the last name of the person, for example Benioff. It travels with the first name rather than on its own, so fill both when you go the name route.
- Domain: the domain name, for example salesforce.com. Pair it with the name fields when no email address was collected.
Need help automating Uplead with n8n?
A person reads every message.
