Skip to main content
Connectors

lemlist connector

Set up the lemlist connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your lemlist data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.

What is the lemlist connector

Sync your lemlist outreach data into BigQuery with Kaivo to measure campaigns and outreach activity.

CategoryMarketing & Sales, Surveys & Email
AuthenticationAPI key
SetupSelf-service

Getting started with the lemlist connector

  1. Sign up for Kaivo and create a workspace.
  2. Connect your lemlist account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticating lemlist

Authenticate with your API Key.

FieldDescription
API Key

Lemlist API key.

Tables and columns synced from lemlist

Kaivo syncs 4 tables from lemlist into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

ColumnTypeDescription
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
typeSTRING
_idSTRING
campaign_idSTRING
campaign_nameSTRING
company_nameSTRING
created_atSTRING
created_bySTRING
emailSTRING
email_template_idSTRING
email_template_nameSTRING
extra__lead_company_nameSTRING
extra__lead_phoneSTRING
extra__lead_pictureSTRING
extra__send_user_idSTRING
extra__user_nameSTRING
first_nameSTRING
icebreakerSTRING
is_firstBOOL
last_nameSTRING
lead_emailSTRING
lead_first_nameSTRING
lead_idSTRING
lead_last_nameSTRING
linkedin_urlSTRING
phoneSTRING
pictureSTRING
sequence_idSTRING
sequence_stepINT64
sequence_testedSTRING
step_testedSTRING
team_idSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.
ColumnTypeDescription
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
_idSTRING
nameSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: campaigns__labels

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.
ColumnTypeDescription
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
_idSTRING
_updated_atSTRING
api_keySTRING
campaign_cron__last_atSTRING
created_atSTRING
created_bySTRING
ctd_check__last_atSTRING
data_integrity_checks_cron__last_atSTRING
linkedin_last_scanned_atSTRING
nameSTRING
revenue_visualization__average_contract_valueINT64
revenue_visualization__average_contract_value_currencySTRING
revenue_visualization__conversion_rateINT64
revenue_visualization__enabledBOOL
sequences_safe_check_cron__last_atSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: team__beta

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: team__billing__products

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
freetrial_expires_atSTRING
nameSTRING
okBOOL
ok_updated_atSTRING
planSTRING
quantityINT64
stripe_subscription_idSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: team__data_integrity_checks_cron__errors

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
textSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: team__user_ids

ColumnTypeDescription
_kaivo_parent_idSTRINGForeign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
valueSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.
ColumnTypeDescription
_kaivo_idSTRINGPrimary key that uniquely identifies the row. Auto-generated by Kaivo.
_idSTRING
emailSTRING
_kaivo_extracted_atTIMESTAMPTimestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the lemlist sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where lemlist supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.

Frequently asked questions

How long does the initial sync take for lemlist?

It depends on how much history is in your lemlist account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.

Can I sync only some tables or columns?

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.

What happens when lemlist's schema changes?

New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in lemlist, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in lemlist instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the lemlist connector in Kaivo and all of its synced data is deleted with it.

Common use cases for lemlist data

Campaign performance

Use campaigns and activities to track outreach results over time.

Deliverability

Use unsubscribes to monitor list health across campaigns.

Team view

Use team to compare outreach activity across the team.

Use lemlist data in your AI and BI tools

Once lemlist data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with lemlist data.

Claude

Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Power BI

Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Data Studio

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

Tableau

The premium analytics standard, with native BigQuery integration. Setup guide →

Google Sheets

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Excel

Connect via Power Query's BigQuery connector. Setup guide →

Metabase

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for lemlist connector pricing and plan details.

Was this helpful?

Still need help? Share an idea