HTTP Request node
Postgres node
Slack node

Enrich up to 1500 emails per hour with Dropcontact batch requests

Published 1 month ago



Template description

The template allows to make Dropcontact batch requests up to 250 requests every 10 minutes (1500/hour). Valuable if high volume email enrichment is expected.

Dropcontact will look for email & basic email qualification if first_name, last_name, company_name is provided.


Step 1:
Node "Profiles Query"
Connect your own source (Airtable, Google Sheets, Supabase,...) the template is using Postgres by default.

Note I:
Be careful your source is only returning a maximum of 250 items.

Note II:
The next node uses the next variables, make sure you can map these from your source file:

  • first_name
  • last_name
  • website (company_name would work too)
  • full_name (see note)

Note III:
This template is using the Dropcontact Batch API, which works in a POST & GET setup. Not a GET request only to retrieve data, as Dropcontact needs to process the batch data load properly.


Step 2:
Node "Data Transformation"
Will transform the input variables in the proper json format. This json format is expected from the Dropcontact API to make a batch request.

"full_name" is being used as a custom identifier to update the returned email to the proper contact in your source database.

To make things easy, use a unique identiefer in the full_name variable.


Node: "Bulk Dropcontact Requests".
Enter your Dropcontact credentials in the node: Bulk Dropcontact Requests.


Connect your output source by mapping the data you like to use.


Node: "Slack" (OPTIONAL)
Connect your slack account, if an error occur, you will be notified.

TIP: Try to run the workflow with a batch of 10 (not 250) as it might need to run initially before you will be able to map the data to your final destination. Once the data fields are properly mapped, adjust back to 250.

Share Template

Implement complex processes faster with n8n

red icon yellow icon red icon yellow icon