Skip to content
Book a demoStart free
Connectors

ZapSign connector

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

ZapSign connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your ZapSign 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 data from ZapSign instead of moving it.

Sync your ZapSign e-signature data into BigQuery with Kaivo to track document signing and completion.

CategoryTech
AuthenticationAPI key
SetupSelf-service

Getting started with the ZapSign connector

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

Field Description
API Token
Your ZapSign API token. You can find it in your account under Settings or the API section.

|

When you set up the connector, you provide:

Field Description
Start Date
Any data before this date will not be fetched.

| | Signer IDs |

List of signer IDs to retrieve signer details for.

|

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

documents (13 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
created_at STRING
created_through STRING
deleted BOOL
external_id STRING
folder_path STRING
last_update_at STRING
name STRING
open_id FLOAT64
original_file STRING
status STRING
token STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
signer (32 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
auth_mode STRING
blank_email BOOL
blank_phone BOOL
cnpj STRING
cpf STRING
document_photo_url STRING
document_verse_photo_url STRING
email STRING
external_id STRING
hide_email BOOL
hide_phone BOOL
liveness_photo_url STRING
lock_email BOOL
lock_name BOOL
lock_phone BOOL
name STRING
phone_country STRING
phone_number STRING
qualification STRING
redirect_link STRING
require_document_photo BOOL
require_selfie_photo BOOL
selfie_photo_url STRING
selfie_photo_url2 STRING
selfie_validation_type STRING
send_via STRING
sign_url STRING
status STRING
times_viewed FLOAT64
token STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
templates (12 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
active BOOL
created_at STRING
folder_path STRING
lang STRING
last_update_at STRING
name STRING
redirect_link STRING
template_file STRING
template_type STRING
token STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_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 ZapSign 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 ZapSign?

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

It depends on how much history is in your ZapSign 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 ZapSign’s schema changes?

Section titled “What happens when ZapSign’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 ZapSign, 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 ZapSign 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 ZapSign connector in Kaivo and all of its synced data is deleted with it.

Use documents to track how many documents are sent, signed, and completed over time.

Join templates with documents to see which templates are used most.

Use signer to monitor who signs and how quickly.

Once ZapSign 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 ZapSign 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 ZapSign connector pricing and plan details.

  • Adform: Sync Adform to BigQuery.
  • Amplitude: Sync Amplitude to BigQuery.
  • Auth0: Sync Auth0 to BigQuery.
  • Convex: Sync Convex to BigQuery.
  • GitHub: Sync GitHub to BigQuery.
  • GitLab: Sync GitLab to BigQuery.