Chargebee

Chargebee ETL connector for data replication

Snapshot

Features
Details
Release Status
Released
Source API Version
v2
Table Selection
Yes
Column Selection
Yes
Edit Integration
Yes
Replication Type Selection
No
Authentication Parameters
Chargebee API Key Site Name on ChargeBee
Replication Type
Key Based Replication
Replication Key
Date
Suggested Replication Frequency
24 hrs
Tables/APIs Supported
Customers
Subscription

Pre-requisites

  1. 1.
    Generate Chargebee API Key for Daton
  2. 2.
    Read more on How to create Chargebee API Keys here

Integrate ChargeBee with Daton

  1. 1.
    Signin to Daton
  2. 2.
    Select ChargeBee from Integrations page
  3. 3.
    Provide Integration Name, Replication Frequency, and History. Integration name would be used in creating tables for the integration and cannot be changed later
  4. 4.
    Provide API Key and Site Name to authorize Daton to periodically extract data from ChargeBee
  5. 5.
    Post successful authentication, you will be prompted to choose from the list of available tables
  6. 6.
    Then select all required fields for each table
  7. 7.
    Submit the integration

Workflow

  1. 1.
    Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
  2. 2.
    Users would be able to edit/pause/re-activate/delete integration anytime
  3. 3.
    Users can view job status and process logs from the integration details page by clicking on the integration name from the active list

ChargeBee Data

Customers
Purpose: Retrieve details of a customer subscriptions, card and billing address.
Replication: Key-Based Replication
Replication Key: createdAt
Fields
Name
Target Datatype
id
STRING
email
STRING
auto_collection
STRING
net_term_days
INTEGER
allow_direct_debit
BOOLEAN
created_at
INTEGER
taxability
STRING
updated_at
INTEGER
pii_cleared
STRING
resource_version
NUMERIC
vatNumberStatus
STRING
deleted
BOOLEAN
object
STRING
card_status
STRING
contacts
RECORD
Subscription
Purpose: Retrieve details of subcription and billing close date or payment due date
Replication: Key-Based Replication
Replication Key: createdAt
Fields
Name
Target Datatype
id
STRING
customer_id
STRING
plan_id
STRING
plan_quantity
NUMERIC
plan_unit_price
NUMERIC
plan_amount
NUMERIC
billing_period
INTEGER
billing_period_unit
STRING
plan_free_quantity
INTEGER
status
STRING
trial_start
NUMERIC
trial_end
NUMERIC
next_billing_at
NUMERIC
created_at
NUMERIC
started_at
NUMERIC
updated_at
NUMERIC
has_scheduled_changes
BOOLEAN
resource_version
NUMERIC
deleted
BOOLEAN
currency_code
STRING
object
STRING
due_invoices_count
NUMERIC