Dropcontact n8n integrationAutomate Dropcontact with n8n.
Half a lead list is a name and a company site, and no way to reach anyone. The Dropcontact n8n integration puts one node in your workflow, with a single Contact resource and 2 operations: enrich a contact, or fetch the result of an enrichment. Built for teams who keep their prospecting data in a sheet or a CRM.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Dropcontact n8n integration actually do?
It connects a Dropcontact account to an n8n workflow through one node. That node carries a single resource, Contact, and 2 operations: contact.enrich finds a B2B email and completes a record from a name and a website, contact.fetchRequest picks up the result of an enrichment that was started earlier. Dropcontact has no trigger node in n8n, so the workflow always starts somewhere else and calls the node when a contact is missing an address.
Start with the list you already have. A team drops trade show badges or webinar signups into a spreadsheet: first names, company sites, almost never an email. A workflow reads the rows from Google Sheets, sends each one through the enrich operation, then writes the returned contact back next to the original row. The manual round of searching disappears.
Turn social activity into CRM records. A scraping tool collects the people who reacted to a LinkedIn post, Dropcontact turns each profile into a reachable contact, and the result lands as a new record in HubSpot or Pipedrive. A sending tool such as lemlist then picks up only the contacts that came back with an address.
React to a signal instead of a schedule. A monitoring tool flags a company that just opened a role, the workflow enriches the person who owns that budget, pushes the contact into Salesforce, and posts a short note to the channel that follows the account.
The node stops at those 2 operations. Anything else the Dropcontact API offers stays reachable through the HTTP Request node, which reuses the same credential with predefined authentication, so the key lives in one place. Keep that in mind before building a workaround: there is no bulk operation and no history lookup in the node.
Two things catch people out. The enrich operation has no required parameter, so an empty node runs and gives you almost nothing back: feed it an email, or a name with a website, or a LinkedIn profile. And with Simplify Output (Faster) turned on, the node hands back an identifier rather than the contact itself, which is exactly the job Fetch Request does afterwards. Still comparing platforms? The n8n review goes through the trade-offs.
How do you connect Dropcontact to n8n?
- 01
Open your Dropcontact API page
Dropcontact asks for a developer account before it hands out an API key. Once the account exists, the key sits on the API page of the Dropcontact app. Copy it from there rather than from an email or a shared document, so you always take the key attached to the account that will be billed for the enrichments.
- 02
Create the credential in n8n
In n8n, open the Credentials menu and create a Dropcontact credential. A credential is the box where n8n stores a secret so a node never holds it in plain sight. The Dropcontact credential has one field, API Key, and one supported authentication method, API key. Paste the value and save.
- 03
Point the node at the credential
Drop a Dropcontact node into a workflow and pick the credential from the dropdown list. Set Resource to Contact, Operation to Enrich, type a known work email in Email, and run the node once. A filled response confirms the key works, and you can switch the field to an expression such as
{{ $json.email }}for real runs.
What can the Dropcontact node do?
The Dropcontact node exposes 2 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Contact
2 operationsFind B2B emails
contact.enrichWhat you see in n8n
Notes & use cases
Sends a contact to Dropcontact and returns an enriched record built from what you already hold: an email, a name, a website.
Key parameters
- Email: the address to work from, often
{{ $json.email }}from the node before. No field is required here, so a name plus a Website is a valid starting point. - Simplify Output (Faster): on, the node returns a request identifier straight away; off, it waits for the contact data before it completes.
- French Company Enrich: adds the SIREN number, NAF code, TVA number, company address and leader details. French companies only.
Fetch Request
contact.fetchRequestWhat you see in n8n
Notes & use cases
Collects the result of an enrichment that was launched earlier. When Simplify Output (Faster) was on, the first call only returned an identifier, and this operation goes back for the finished contact data.
Key parameters
- Request ID: required, the identifier handed back by the enrich call, usually read from that node with an expression.
Need help automating Dropcontact with n8n?
A person reads every message.
