Enrich up to 1500 emails per hour with Dropcontact batch requests
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on a schedule (every day). Along the way it connects Postgres and Slack. It also calls api.dropcontact.io over HTTP.
How it runs
Trigger: On a schedule (every day).
- PROFILES QUERY (Postgres): run a query
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- Aggregate: combines items into one
- DATA TRANSFORMATION (Code): runs custom Python code
- BULK DROPCONTACT REQUESTS (HTTP Request): calls api.dropcontact.io (POST)
- Wait: waits 600 seconds
- BULK DROPCONTACT DOWNLOAD (HTTP Request): calls an HTTP API
- Split Out: splits a list into separate items
- Slack: uses Slack
- Postgres: update
Services it uses
HTTP calls to: api.dropcontact.io
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Aggregate
n8n-nodes-base.aggregate - Postgres
n8n-nodes-base.postgres - HTTP Request
n8n-nodes-base.httpRequest - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Split Out
n8n-nodes-base.splitOut - Wait
n8n-nodes-base.wait - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
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 firstname, lastname, companyname is…