Datapipe
Outbound agencies
Send each client a weekly report of leads reached, replies and meetings booked.
Read & reportControlled changes
See your lemlist numbers in Data Studio.
Read campaigns, results by day, sequence steps, sending mailboxes and replies from a lemlist team. You can allow teammates and AI tools to resume or pause campaigns, add leads, mark leads interested or not interested, and pause or resume a lead. Allowed changes apply right away and are recorded in history.
- Replies, interested leads and booked meetings for every campaign, across email and LinkedIn
- See which step in the sequence earns the replies
- Ask ChatGPT or Claude which mailbox disconnected this week
Data StudioUpdated November 2026
| Campaign name | Messages sent | Replies |
|---|---|---|
| Ops leaders · logistics | 2,011 | 101 |
| CFOs · mid-market SaaS | 1,652 | 71 |
| Founders · seed-stage fintech | 1,212 | 59 |
- SetupPaste a key or token
- Reads95 report fields across 5 datasets
- Changes4 change actions
- RefreshDaily to every 15 minutes
Who uses Datapipe with lemlist
Sales development teams
Compare email and LinkedIn steps without exporting from lemlist.
Revenue operations
Keep every rep’s mailboxes connected and within their daily limits.
What you can do with lemlist
Read and report
One team stays bound to each data source.
- Campaign performance
- Campaign results by day
- Sequence steps
- Sending mailboxes
- and 1 more
Controlled changes
- Resume or pause a campaign
- Add a lead to a campaign
- Mark a lead interested or not interested
- Pause or resume a lead
Changes stay off until you allow them. Allowed changes apply to lemlist right away, and history keeps the values before and after.
Full read details
Campaign results, steps and replies use UTC dates, up to 365 days; results by day cover up to 92 days. Leads who replied include the reply channel, company and current state; names, phone numbers and custom variables are left out.
Examples for your team
Report replies and meetings by channel
Compare leads reached, replies, interested leads and booked meetings for every campaign, with email and LinkedIn side by side.
- Scheduled refresh
- Latest lemlist data
- Updated report
Keep mailboxes connected
List every team member’s mailboxes with connection status, daily limit and lemwarm, so a disconnected inbox shows before a campaign stalls.
- Scheduled refresh
- Latest lemlist data
- Updated report
Mark a reply as interested
A teammate marks a lead from the Leads who replied report as interested in its campaign.
- Allowed
- Applied
- Recorded
Limit: History keeps the earlier state.
Fix things in lemlist without opening it
Spot it, fix it
See the problem in your report, then make the fix in Datapipe instead of opening lemlist, finding the record and retyping it.
More people can help
Teammates and AI tools you allow can make changes without getting edit access to lemlist.
You decide what can change
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
Jobs you can stop doing by hand in lemlist
Resume or pause a campaign
Pause a campaign with a setup issue
TodayLog in to lemlist, find the campaign and pause it by hand.
With DatapipeYour Campaign performance report flags a disconnected sender. Pause the campaign from Datapipe; its leads and steps stay as they are.
Resume after the fix
TodayWait for a teammate with lemlist access to resume it.
With DatapipeResume the paused campaign from Datapipe once the mailbox is reconnected.
Exactly what this can change
Resumes or pauses one campaign in the connected lemlist team. A resumed campaign carries on with its leads on its own schedule; a paused one stops until it is resumed. A campaign that was never launched is started in lemlist itself.
Supported fields: Campaign.
Add a lead to a campaign
Add a referral to the right campaign
TodayCopy the details into lemlist by hand.
With DatapipeA teammate adds the referral’s email, name and company to the campaign. lemlist contacts them on the campaign’s schedule.
Add an event contact
TodayImport a one-row CSV in lemlist.
With DatapipeClaude adds the contact from your event list to the follow-up campaign. A lead already in the campaign is refused.
Exactly what this can change
Adds one lead to a campaign. If the campaign is running, lemlist contacts the lead on the campaign’s schedule. A lead already in the campaign is refused.
Supported fields: Email, First name, Last name, Company, Job title.
Mark a lead interested or not interested
Mark a reply as interested
TodayOpen the reply in lemlist and change the lead’s status.
With DatapipeYour Leads who replied report lists yesterday’s replies. Mark the right one interested from Datapipe.
Close out a polite no
TodayFind the lead in each campaign and relabel it.
With DatapipeClaude marks leads who replied “not now” as not interested in that campaign, so interest counts stay honest.
Exactly what this can change
Marks one lead interested or not interested in one campaign, as you would in lemlist. Interested counts in lemlist and in reports follow. The lead is not contacted.
Supported fields: Interest.
Pause or resume a lead
Hold a lead who asked to talk next month
TodayOpen the lead in lemlist and pause it.
With DatapipePause the lead from Datapipe; the rest of the campaign keeps running.
Resume a paused lead
TodayFind the lead and resume it by hand.
With DatapipeResume the lead from Datapipe when the timing is right.
Exactly what this can change
Pauses or resumes one lead’s sequence. The rest of the campaign keeps running.
Supported fields: Lead.
Mark a lead interested or not interestedLead avery@cobalt-labs.example · Ops leaders · logistics · made by Jordan Blake
| Field | Before | After |
|---|---|---|
| Interest | Replied by email | Interested |
You control who can change what
- A change is allowed for this data source
- A teammate or AI tool makes it
- It applies right away, or waits for approval if you set that
- Recorded with the values before and after
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider rules and limits
Provider permissions still apply, and automations in lemlist may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
Before you connect
What you need
An API key or token from your lemlist account.
Read and write
Read access for reports. The 4 change actions need edit access in lemlist and stay off until the owner, an admin or a project manager allows them.
Limits and exclusions
SMS, WhatsApp and call outcomes are not included. Lead names, phone numbers and custom variables are not included.
Full details and limits
Read one lemlist team: campaign results across email and LinkedIn, results by day, sequence steps, team members’ sending mailboxes, and leads who replied with their current state. Dates use UTC, up to 365 days (92 days for results by day). Lead names, phone numbers and custom variables are left out.
Uses a lemlist API key from Settings, Integrations. The key acts for the whole team, so the same key covers reports and campaign and lead changes. A lemlist admin, or a member allowed to use the API, creates it.
One key reads one lemlist team. Dates use UTC; results by day cover up to 92 days. Statuses and mailbox settings show their current value. SMS, WhatsApp and call outcomes are not included. Lead names, phone numbers and custom variables are not included.
Reports you can build
5 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- Campaign performance
- Campaign results by day
- Sequence steps
- Sending mailboxes
- Leads who replied
What each dataset reports
- Campaign performance
One row per campaign with lemlist’s results for the selected UTC dates, across email and LinkedIn: leads reached, opened, answered and marked interested, messages sent, delivered, opened, clicked and replied, bounces, accepted invitations and booked meetings, plus email and LinkedIn on their own. Lead counts count each lead once; message counts count every message. Drafts are left out.
- Campaign results by day
One row per campaign and UTC day with lemlist’s results for that day: messages sent and delivered, opens, clicks, replies, bounces, leads marked interested, unsubscribes and meetings booked. Days without activity are left out.
- Sequence steps
One row per campaign and sequence step for the selected UTC dates, with the step’s channel (email, LinkedIn invite, message or visit, call, manual task or condition) and what it sent, delivered, opened, clicked and got replies to.
- Sending mailboxes
Current state of each team member’s connected mailbox: provider, connection status, daily sending limit and whether lemwarm is on. Report dates do not change these values.
- Leads who replied
One row per lead and campaign with an email or LinkedIn reply in the selected UTC dates: how many replies arrived, the step that got the last one, and the lead’s current state in the campaign. Lead email and company come from lemlist; names and other lead fields are left out.
Metrics and dimensions
95 report fields across 5 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.
Send lemlist data anywhere
Google SheetsA sheet that refreshes every morning.Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
Excel / CSVA Drive file you can open in Excel.
ClaudeAsk Claude about these numbers in a sentence.
ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed lemlist changes. They can never widen their own access.
Which lemlist campaign booked the most meetings in the last 30 days, and did email or LinkedIn bring more replies?
Ops leaders · logistics led with 10 meetings. Email brought most replies; the LinkedIn message step added the rest.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- Each campaign can be its own row.
- The same numbers can be split by who they came from.
- You can keep a row per day instead of one lump sum.
- People and the way you reach them can be their own rows.
Start from a goal
Campaign performance
One row per campaign with lemlist’s results for the selected UTC dates, across email and LinkedIn: leads reached, opened, answered and marked interested, messages sent, delivered, opened, clicked and replied, bounces, accepted invitations and booked meetings, plus email and LinkedIn on their own.
Use this template →Campaign results by day
One row per campaign and UTC day with lemlist’s results for that day: messages sent and delivered, opens, clicks, replies, bounces, leads marked interested, unsubscribes and meetings booked.
Use this template →Sequence steps
One row per campaign and sequence step for the selected UTC dates, with the step’s channel (email, LinkedIn invite, message or visit, call, manual task or condition) and what it sent, delivered, opened, clicked and got replies to.
Use this template →Sending mailboxes
Current state of each team member’s connected mailbox: provider, connection status, daily sending limit and whether lemwarm is on.
Use this template →How it works
Create a project and choose lemlist in Data sources.
Pick where it goes. This one sends the numbers to Data Studio.
Pick where it goes. Choose campaign performance or another dataset, the dates and a destination.
Sample report
Sample campaign report for the last 30 UTC days, one row per campaign. Messages and replies count email and LinkedIn together; interested leads and meetings count each lead once.
| Campaign name | Messages sent | Replies | Leads interested | Meetings booked |
|---|---|---|---|---|
| Ops leaders · logistics | 2,011 | 101 | 40 | 10 |
| CFOs · mid-market SaaS | 1,652 | 71 | 29 | 7 |
| Founders · seed-stage fintech | 1,212 | 59 | 14 | 6 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with lemlist
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.
Questions
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.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected lemlist account. Nobody else gets a lemlist login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that lemlist received it, the request is marked Uncertain and is never retried automatically, so you can check lemlist first.
Yes. Datapipe reads the reports on this page and can make 4 kinds of change: resume or pause a campaign; add a lead to a campaign; mark a lead interested or not interested; pause or resume a lead. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 95 report fields across 5 datasets. You pick the columns when you build the report.
Read one lemlist team: campaign results across email and LinkedIn, results by day, sequence steps, team members’ sending mailboxes, and leads who replied with their current state. Dates use UTC, up to 365 days (92 days for results by day). Lead names, phone numbers and custom variables are left out. Account permissions and the records available from the provider determine which rows can be read.
One for each lemlist 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.
Try lemlist with sample data first
Build the report first, then add lemlist when you are ready.