Skip to content
Book a demoStart free
Connectors

SendPulse connector

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

SendPulse connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your SendPulse 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 survey and email data instead of moving it.

Sync your SendPulse messaging data into BigQuery with Kaivo to measure campaigns and audience growth across channels.

CategorySurveys & Email, Marketing & Sales
AuthenticationAPI key
SetupSelf-service

Getting started with the SendPulse connector

Section titled “Getting started with the SendPulse connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your SendPulse 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.

Authenticate with your SendPulse credentials. You provide:

Field Description
OAuth Client ID
OAuth Client Secret

Prerequisites

SendPulse uses OAuth 2.0 client credentials. You need to register your own API application in SendPulse to obtain credentials:

  1. Log in to your SendPulse account and go to Settings → API.
  2. Note your Client ID and Client Secret.

Then enter those values below.

Need help? Reach our team via the chat in the bottom-right corner.

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

balance (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
balance_currency FLOAT64
currency STRING
datetime STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
balance_details (13 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
balance__bonus STRING
balance__currency STRING
balance__main STRING
email__current_subscribers FLOAT64
email__finished_time STRING
email__is_unique_type BOOL
email__maximum_subscribers FLOAT64
email__tariff_name STRING
push__auto_renew FLOAT64
push__end_date STRING
push__tariff_name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
campaigns (25 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
all_email_qty FLOAT64
company_price STRING
id FLOAT64
is_sms BOOL
is_viber BOOL
message__attachments STRING
message__list_id FLOAT64
message__sender_email STRING
message__sender_name STRING
message__subject STRING
name STRING
overdraft_currency STRING
overdraft_price FLOAT64
paid_email_qty FLOAT64
send_date STRING
statistics__delivered FLOAT64
statistics__error FLOAT64
statistics__link_redirected FLOAT64
statistics__opening FLOAT64
statistics__sent FLOAT64
statistics__unsubscribe FLOAT64
status FLOAT64
tariff_email_qty FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
mailing_lists (13 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
active_email_qty FLOAT64
active_phones_quantity FLOAT64
all_email_qty FLOAT64
creationdate STRING
exc_phones_quantity FLOAT64
id FLOAT64
inactive_email_qty FLOAT64
name STRING
new_phones_quantity FLOAT64
status FLOAT64
status_explain STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
senders (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
email STRING
is_allowed_for_smtp BOOL
name STRING
status STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
templates (15 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
category STRING
category_info JSON
created STRING
full_description STRING
id STRING
is_structure BOOL
lang STRING
name STRING
name_slug STRING
owner STRING
preview STRING
real_id FLOAT64
tags JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
webhooks (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
action STRING
id FLOAT64
url STRING
user_id FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where SendPulse 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.

How long does the initial sync take for SendPulse?

Section titled “How long does the initial sync take for SendPulse?”

It depends on how much history is in your SendPulse 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.

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 SendPulse’s schema changes?

Section titled “What happens when SendPulse’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 SendPulse, 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?

Section titled “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 SendPulse 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 SendPulse connector in Kaivo and all of its synced data is deleted with it.

Use campaigns to track results across email and other channels over time.

Use mailing_lists to see how your audience grows.

Use balance_details to monitor sending spend over time.

Use SendPulse data in your AI and BI tools

Section titled “Use SendPulse data in your AI and BI tools”

Once SendPulse 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 SendPulse data.

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

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

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

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

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

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

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

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