API

AI

Automations

Data Model

Data Import & Export

Introduction

CRM Integrations

Data Warehouse Integration

File Import

Custom Integrations

Import & Export via App

Help Center

Security

Changelog

Planhat Logo

Developers

Planhat Logo

Developers

Data Warehouse Integration

Planhat’s Data Warehouse integrations generally sync two types of data: cross-sectional (or “CRM”) and time series (or “usage”) data.

Planhat’s Data Warehouse integrations generally sync two types of data: cross-sectional (or “CRM”) and time series (or “usage”) data.

Planhat’s Data Warehouse integrations generally sync two types of data: cross-sectional (or “CRM”) and time series (or “usage”) data.

Snowflake

The Snowflake integration can sync both CRM data (bidirectional) and Usage data (only fetch). Authentication happens through oauth2. Read more about the Snowflake integration here.

CRM data

  • Bidirectional

  • Supports custom sync sections and field mappings

  • SourceId or ExternalId can be used as the key for each sync section - which one to use is optional

  • Planhat can fetch from both Snowflake Views and Tables

  • Sending and fetching data happens on an hourly basis, approximately

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

Snowflake

The Snowflake integration can sync both CRM data (bidirectional) and Usage data (only fetch). Authentication happens through oauth2. Read more about the Snowflake integration here.

CRM data

  • Bidirectional

  • Supports custom sync sections and field mappings

  • SourceId or ExternalId can be used as the key for each sync section - which one to use is optional

  • Planhat can fetch from both Snowflake Views and Tables

  • Sending and fetching data happens on an hourly basis, approximately

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

Snowflake

The Snowflake integration can sync both CRM data (bidirectional) and Usage data (only fetch). Authentication happens through oauth2. Read more about the Snowflake integration here.

CRM data

  • Bidirectional

  • Supports custom sync sections and field mappings

  • SourceId or ExternalId can be used as the key for each sync section - which one to use is optional

  • Planhat can fetch from both Snowflake Views and Tables

  • Sending and fetching data happens on an hourly basis, approximately

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

BigQuery

The BigQuery integration can sync both CRM data (bidirectional) and Usage data (only fetch). Authentication happens through oauth2. Read more about the BigQuery integration here.

CRM data (same as Snowflake above)

  • Bidirectional

  • Supports custom sync sections and field mappings

  • SourceId or ExternalId can be used as the key for each sync section - which one to use is optional

  • Planhat can fetch from both Snowflake Views and Tables

  • Sending and fetching data happens on an hourly basis, approximately

Usage data (same as Snowflake above)

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

BigQuery

The BigQuery integration can sync both CRM data (bidirectional) and Usage data (only fetch). Authentication happens through oauth2. Read more about the BigQuery integration here.

CRM data (same as Snowflake above)

  • Bidirectional

  • Supports custom sync sections and field mappings

  • SourceId or ExternalId can be used as the key for each sync section - which one to use is optional

  • Planhat can fetch from both Snowflake Views and Tables

  • Sending and fetching data happens on an hourly basis, approximately

Usage data (same as Snowflake above)

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

BigQuery

The BigQuery integration can sync both CRM data (bidirectional) and Usage data (only fetch). Authentication happens through oauth2. Read more about the BigQuery integration here.

CRM data (same as Snowflake above)

  • Bidirectional

  • Supports custom sync sections and field mappings

  • SourceId or ExternalId can be used as the key for each sync section - which one to use is optional

  • Planhat can fetch from both Snowflake Views and Tables

  • Sending and fetching data happens on an hourly basis, approximately

Usage data (same as Snowflake above)

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

PostgreSQL

The PostGres integration only syncs usage data, and uses basic authentication. Read more about the PostGreSQL integration here.

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

PostgreSQL

The PostGres integration only syncs usage data, and uses basic authentication. Read more about the PostGreSQL integration here.

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

PostgreSQL

The PostGres integration only syncs usage data, and uses basic authentication. Read more about the PostGreSQL integration here.

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

MySQL

The MySQL integration only syncs usage data, and uses basic authentication. Read more about the MySQL integration here.

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

MySQL

The MySQL integration only syncs usage data, and uses basic authentication. Read more about the MySQL integration here.

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

MySQL

The MySQL integration only syncs usage data, and uses basic authentication. Read more about the MySQL integration here.

Usage data

  • Fetch only

  • Both User Activities and Custom Metrics

  • Must use a unique, incrementing, numeric column as key

  • Can be set to fetch every 5, 10, 30 or 60 minutes, or daily on a schedule

Automation /

Data Import & Export /

Data Import & Export /