- Source
- Finance & Ops Analytics
- Alpha
Move Chift data anywhere it matters.
Stream Chift consumers, connections and syncs to any warehouse or AI app.
Source
Chift
Snowflake
BigQuery
Postgres
Databricks
Claude
- Streams
- 4
- Incremental stream
- 1
- Destinations
- 50+
- Standard support
- 0.1.5
Overview
What is the Airbyte Chift connector?
The Airbyte Chift connector extracts data from Chift and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes 4 streams you can select per connection.
- 01
Sync to your warehouse
Land 4 Chift tables in 50+ destinations on a schedule you control.
- 02
Incremental syncs
Pull only the records that changed since the last run instead of reloading everything.
- 03
One authorization
Authenticate Chift once and Airbyte keeps every scheduled sync running on it.
- 04
Cloud or self-hosted
Run the Chift connector on Cloud, OSS, Hybrid.
4 streams
Every table you can sync from Chift
consumers Primary key consumerid Sync modes FullIncr. connections Primary key connectionid Sync modes FullIncr. syncs Primary key syncid Sync modes FullIncr. executionsIncremental Primary key id Sync modes FullIncr.
Setup
Live in six steps
In the left navigation bar of the Airbyte UI, click Sources. In the top-right corner, click + New source.
Find and select Chift from the list of available sources.
Enter a Source name of your choosing.
Enter the Client Id, Client Secret, and Account Id from your Chift API key.
Optionally, enter a Start Date in YYYY-MM-DDTHH:MM:SS format, for example 2026-01-01T00:00:00. Only executions that started on or after this date are synced. If you leave it empty, the connector syncs all executions. Other formats, such as a date without a time or a value with a Z suffix, are rejected.
Click Set up source and wait for the tests to complete.
Configuration fields
| Field | Type | Description |
|---|---|---|
| account_id* | string | Not documented. |
| client_id* | string | Not documented. |
| client_secret* | string | Not documented. |
| start_date | string | Only executions started on or after this date are synced. Use the YYYY-MM-DDTHH:MM:SS format, for example 2026-01-01T00:00:00; a date without a time, or a value carrying a Z suffix or a UTC offset, is rejected. Optional; defaults to 1970-01-01T00:00:00, which syncs everything. |
Hybrid deployment
Sovereign by architecture, not by policy.
The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.
- Cloud
- OSS
- Hybrid
Your environment
Airbyte control plane
FAQ
Chift connector questions
What data can I sync from Chift with Airbyte?
4 streams: consumers, connections, syncs, executions.
Does the Chift connector support incremental sync?
Yes. executions support incremental sync, and every documented stream supports full refresh.
Where can I run the Chift connector?
Run the Chift connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.
Didn't find your answer? Talk to sales
Start syncing Chift in minutes.
Free 14-day trial. No credit card needed.