Skip to content
Book a demoStart free
Connectors

Postmark connector

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

Postmark connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Postmark 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 Postmark delivery data into BigQuery with Kaivo to monitor transactional email deliverability and engagement.

CategorySurveys & Email
AuthenticationAPI key
SetupSelf-service

Getting started with the Postmark connector

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

Field Description
Server Token
Your Postmark server token, used to authenticate requests to a specific server. Found in your Postmark server settings.

| | Account Token |

Your Postmark account token, used for account-level API access. Found in your Postmark account settings.

|

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

bounces (19 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
bounced_at STRING Timestamp indicating when the email bounced
can_activate BOOL Whether the recipient can manually reactivate the email address
description STRING Description or reason for the bounce
details STRING Additional details or error message related to the bounce
dump_available BOOL Whether detailed dump of the bounce is available
email STRING Email address that bounced
from STRING Sender’s email address
id INT64 Unique identifier for the bounce entry
inactive BOOL Whether the recipient’s email address is inactive
message_id STRING Unique identifier for the original message
message_stream STRING Identifier for the message stream where the bounce occurred
name STRING Recipient’s name if available
server_id INT64 Identifier for the server that handled the message
subject STRING Subject of the original email
tag STRING Tag associated with the original message
type STRING Type of bounce (hard, soft, etc.)
type_code INT64 Numeric code representing the bounce type
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
deliverystats (4 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
count INT64 The total count of delivered items for the specified time period.
name STRING The name of the delivery status type corresponding to the count.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
domains (8 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
dkim_verified BOOL Indicates if DKIM for the domain is verified or not.
id INT64 The unique identifier assigned to the domain.
name STRING The name of the domain.
return_path_domain_verified BOOL Indicates if the return path domain is verified or not.
spf_verified BOOL Indicates if SPF for the domain is verified or not.
weak_dkim BOOL Indicates if the DKIM for the domain is weak or not.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
message-streams (12 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
archived_at JSON Timestamp when the message stream was archived.
created_at STRING Timestamp when the message stream was created.
description STRING Description of the message stream.
expected_purge_date JSON Expected date for purging the message stream data.
id STRING Unique identifier for the message stream.
message_stream_type STRING Type of the message stream (e.g., transactional, marketing).
name STRING Name of the message stream.
server_id INT64 Unique identifier of the server associated with the message stream.
subscription_management_configuration__unsubscribe_handling_type STRING Type of unsubscribe handling for the message stream (e.g., manual, automatic).
updated_at JSON Timestamp when the message stream was last updated.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
messages (14 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
from STRING Email address of the sender.
message_id STRING Unique identifier for the message.
message_stream STRING Stream identifier for the message.
metadata__client_id STRING Client identifier associated with the message.
metadata__color STRING Color tag associated with the message.
received_at STRING Timestamp indicating when the message was received.
sandboxed BOOL Indicates if the message was sent in sandbox mode.
status STRING Current status of the message (e.g., delivered, failed).
subject STRING Subject line of the message.
tag STRING Tag associated with the message for categorization.
track_links STRING Indicates if links in the message are being tracked.
track_opens BOOL Indicates if message opens are being tracked.
_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.
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.
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.
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 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.
email STRING Recipient’s email address.
name JSON Recipient’s name.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
servers (23 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
bounce_hook_url STRING URL to which bounce notifications are sent
click_hook_url STRING URL to which click event notifications are sent
color STRING Color associated with the server for identification purposes
delivery_hook_url STRING URL to which delivery event notifications are sent
delivery_type STRING Type of delivery mechanism used by the server
enable_smtp_api_error_hooks BOOL Flag indicating if SMTP API error hooks are enabled
id INT64 Unique identifier of the server
inbound_address STRING Email address for inbound messages
inbound_domain STRING Domain for inbound message processing
inbound_hash STRING Hash code associated with inbound messages
inbound_hook_url STRING URL to which inbound message notifications are sent
inbound_spam_threshold INT64 Spam threshold value for inbound messages
include_bounce_content_in_hook BOOL Flag indicating if bounce content is included in notifications
name STRING Name of the server
open_hook_url STRING URL to which open event notifications are sent
post_first_open_only BOOL Flag indicating if only the first open event should be tracked
raw_email_enabled BOOL Flag indicating if raw email content is enabled
server_link STRING Link to the server’s details or dashboard
smtp_api_activated BOOL Flag indicating if SMTP API is activated
track_links STRING Flag indicating if link tracking is enabled
track_opens BOOL Flag indicating if open tracking is enabled
_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 STRING
_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 Postmark 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 Postmark?

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

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

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

Use deliverystats and bounces to track delivery and failures over time.

Use messages to measure opens and clicks across your sends.

Join message-streams with messages to compare transactional and broadcast sends.

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