Dropcontact

Find B2B emails and enrich contacts

Overview

Dropcontact is a B2B contact enrichment service. Given a person’s name, company, website, or other identifying information, it can find verified professional email addresses and enrich contact data with company information, phone numbers, LinkedIn profiles, and more. Supports batch enrichment of multiple contacts in a single API call. Returns enrichment results either synchronously (with a configurable wait) or asynchronously via a request ID that can be fetched later.

Category: Sales
Tool Name: dropcontact
Version: 1

Appearance: Icon: lucide-Contact | Color: #FFA800

Node Type

Action — processes input items and produces output

Input / Output

Direction	Port(s)
Input	Input
Output	Output, Error

Credentials

This tool requires Dropcontact API credentials. See the Credentials Guide for setup instructions.

Resources

Resource	Value
Contact	contact

Operations

Operation	Value	Description
Enrich	enrich	Find B2B emails and enrich your contact from his name and his website
Fetch Request	fetchRequest	Retrieve results of a previously submitted enrichment request

Parameters

Contact: Enrich

Parameter	Type	Required	Default	Description
Email	string	No	—	Known email address of the contact.
Simplify Output (Faster)	boolean	No	false	When off, waits for the contact data before completing. Waiting time can be adjusted with Data Fetch Wait Time option. When on, returns a request_id that can be used later in the Fetch Request operation.
Additional Fields	collection	No	{}	Extra identifying details sent with the contact. The more you supply, the better Dropcontact can match.
— Company SIREN Number	string	No	—	French company SIREN number.
— Company SIRET Code	string	No	—	French company SIRET code.
— Company Name	string	No	—	Name of the company.
— Country	string	No	—	Country of the contact.
— First Name	string	No	—	First name of the contact.
— Full Name	string	No	—	Full name of the contact.
— Last Name	string	No	—	Last name of the contact.
— LinkedIn Profile	string	No	—	LinkedIn profile URL of the contact.
— Phone Number	string	No	—	Phone number of the contact.
— Website	string	No	—	Company website URL.
Options	collection	No	{}	Settings that apply to the whole enrichment request.
— Data Fetch Wait Time	number	No	45	When not simplifying the response, data will be fetched in two steps. This parameter controls how long to wait (in seconds) before trying the second step. (shown when Simplify Output (Faster) is false)
— French Company Enrich	boolean	No	false	Whether to include SIREN number, NAF code, TVA number, company address and leader information. Only applies to French companies.
— Language	options	No	en	Whether the response is in English or French.
				Options: en (English), fr (French)

Contact: Fetch Request

Parameter	Type	Required	Default	Description
Request ID	string	Yes	—	The request_id returned from a previous Enrich operation.

All Operations

Parameter	Type	Required	Default	Description
Max Concurrency	number	No	10	Maximum number of items to process concurrently.

Output Data

The two operations shape their output differently, and the difference matters downstream.

Enrich sends every incoming item to Dropcontact as one batch request and returns one output item per input item, in the same order. The enrichment fields are merged onto the input item’s JSON — your original fields survive, and Dropcontact’s fields are added alongside them, overwriting any key of the same name. Binary data on the input item is forwarded.

Because it is one request for the whole batch, the Options collection applies to the entire run rather than to individual items: French Company Enrich and Language are sent once with the batch, and Data Fetch Wait Time is waited once, not per item.

With Simplify Output (Faster) on, the node does not wait for enrichment at all. It returns the submission receipt for every item instead of contact data:

{
  "request_id": "...",
  "success": true
}

Feed that request_id into a later Fetch Request node to collect the results.

Fetch Request looks up one previously submitted request per input item and fans out — one output item per enriched contact in that request, so a single input item routinely becomes many. Each of those items replaces the JSON entirely with the enriched contact; the input item’s own fields are not carried through. Binary data is forwarded onto each.

When the request exists but holds no contacts yet, you get a single item that merges the receipt onto your input JSON instead:

{
  "request_id": "...",
  "success": true,
  "data": []
}

Check for that empty data array before treating a Fetch Request result as enriched contacts.

The enriched contact’s own fields are whatever Dropcontact returns for the lookup; the node does not rename, nest or filter them. Reference them downstream by expression, e.g. {{ $json.email }}.

Usage Examples

• Enrich a contact with their name and company to find their B2B email
• Batch enrich multiple contacts from a spreadsheet
• Fetch enrichment results from a previous request using the request ID

Example Configuration

Enrich a contact and wait for the result:

{
  "type": "dropcontact",
  "parameters": {
    "resource": "contact",
    "operation": "enrich",
    "simplify": false,
    "email": "{{ $json.email }}",
    "additionalFields": {
      "first_name": "{{ $json.firstName }}",
      "last_name": "{{ $json.lastName }}",
      "company": "{{ $json.company }}",
      "website": "{{ $json.website }}"
    },
    "options": {
      "waitTime": 30,
      "siren": true,
      "language": "en"
    }
  }
}

Find an email from just a full name and a company website:

{
  "type": "dropcontact",
  "parameters": {
    "resource": "contact",
    "operation": "enrich",
    "simplify": false,
    "additionalFields": {
      "full_name": "{{ $json.name }}",
      "website": "{{ $json.companyUrl }}"
    },
    "options": {
      "waitTime": 20
    }
  }
}

Submit the batch without waiting, and keep the request ID for later:

{
  "type": "dropcontact",
  "parameters": {
    "resource": "contact",
    "operation": "enrich",
    "simplify": true,
    "email": "{{ $json.email }}",
    "additionalFields": {
      "company": "{{ $json.company }}",
      "country": "US"
    },
    "maxConcurrency": 15
  }
}

Collect the results of that submission:

{
  "type": "dropcontact",
  "parameters": {
    "resource": "contact",
    "operation": "fetchRequest",
    "requestId": "{{ $json.request_id }}"
  }
}

Enrich a French company with the full SIREN dataset:

{
  "type": "dropcontact",
  "parameters": {
    "resource": "contact",
    "operation": "enrich",
    "simplify": false,
    "email": "{{ $json.email }}",
    "additionalFields": {
      "full_name": "{{ $json.fullName }}",
      "company": "{{ $json.company }}",
      "website": "{{ $json.website }}",
      "num_siren": "{{ $json.siren }}"
    },
    "options": {
      "waitTime": 45,
      "siren": true,
      "language": "fr"
    },
    "maxConcurrency": 5
  }
}

Error Handling

Mode	Behavior
stop	Halts workflow on first error
continue	Skips failed items, passes successful ones through
errorPort	Routes failed items to Error output port

Tips

Dropcontact enriches B2B contacts by finding verified professional emails from names, companies, and websites.

Parameter Relationships

• Operation Dependency: Parameters email, simplify, additionalFields, and options are only available when operation is "enrich"
• Request ID Dependency: Parameter requestId is only available when operation is "fetchRequest"
• Simplify Impact: When simplify is true, the operation returns immediately with a requestId. When false, it waits for results based on the waitTime option
• Wait Time: The waitTime option in the options collection only applies when simplify is false