Local service agencies
Prove which campaigns bring calls for each client.
Review Hunter.io saved leads, verification statuses and sequence campaign metrics in a read-only data source.
Updated November 2026
| First name | Last name | |
|---|---|---|
| alex@company.com | 1,240 | 1,240 |
| jordan@harbor.example | 640 | 640 |
| sam@acme.example | 210 | 210 |
Prove which campaigns bring calls for each client.
Track lead volume and quality by source.
See how many calls and leads came in last week.
Read leads, lists and campaigns using your Hunter.io API key.
Datapipe reads Hunter.io data for reports. It never changes anything in Hunter.io.
Leads and campaigns are never modified.
Combine lead verification statuses, list counts and campaign replies in one report.
An API key or token from your Hunter.io account.
Read access only. Datapipe never changes anything in Hunter.io.
Read-only reporting access using your Hunter.io API key. Leads and campaigns are never modified.
Verified outreach leads, lead lists, and email campaigns from Hunter.io.
Read-only reporting access using your Hunter.io API key. Leads and campaigns are never modified.
Verified outreach leads, lead lists, and email campaigns from Hunter.io. Read-only reporting access using your Hunter.io API key. Leads and campaigns are never modified.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Hunter.io saved leads with lead ID, email, name, company, job title, verification status, and creation date.
Hunter.io lead lists with list ID, name, lead count, and creation date.
Hunter.io email sequences with campaign ID, name, status, recipients, sent, opened, and replied counts.
19 report fields across 3 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Summarize Hunter.io saved leads, verification statuses, and email campaign stats.
2,180 verified leads across 5 lists, with 640 campaign emails sent and 54 replies.
Hunter.io saved leads with lead ID, email, name, company, job title, verification status, and creation date.
Use this template →Hunter.io lead lists with list ID, name, lead count, and creation date.
Use this template →Hunter.io email sequences with campaign ID, name, status, recipients, sent, opened, and replied counts.
Use this template →Create a project and choose Hunter.io in Data sources.
Pick where it goes. This one sends the numbers to Amazon Redshift.
Pick where it goes. Choose Leads, Lead lists, or Campaigns and a destination.
| Lead ID | First name | Last name | Company | Position | Verification status | Created at | |
|---|---|---|---|---|---|---|---|
| ld_01 | alex@company.com | 1,240 | 1,240 | Acme Corp | Head of Growth | valid | 2026-11-13 |
| 1025 | jordan@harbor.example | 640 | 640 | 640 | 640 | Pending | 640 |
| 1031 | sam@acme.example | 210 | 210 | 210 | 210 | Refunded | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
This integration is read-only in Datapipe. You can report on Hunter.io, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in Hunter.io. Read-only reporting access using your Hunter.io API key. Leads and campaigns are never modified.
This page lists 19 report fields across 3 datasets. You pick the columns when you build the report.
Verified outreach leads, lead lists, and email campaigns from Hunter.io. Account permissions and the records available from the provider determine which rows can be read.
One for each Hunter.io account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Hunter.io when you are ready.