Chargify

Chargify is subscription management software for B2B SaaS. The software is built for the evolving needs of fast-growth companies.

Data integration: Skyvia supports importing data to and from Chargify, exporting Chargify data to CSV files, replicating Chargify data to relational databases and synchronizing Chargify data with other cloud apps and relational databases.

Backup: Skyvia Backup does not support Chargify.

Query: Skyvia Query supports Chargify.

Chargify-Specific Features and Limitations

Skyvia has the following limitations for Chargify:

  • In the Data Integration product, Chargify connections are supported only for packages, which use a new data integration runtime.

    Make sure that the Use new runtime checkbox is selected on the tab bar if you want to use Chargify in your package.

  • Skyvia supports the following DML operations for Chargify objects:

    INSERT, UPDATE, DELETE: Coupons, Customers, ProductPricePoints, Products.

    INSERT: Invoices, ProductFamilies.

    INSERT, UPDATE: Subscriptions.

  • Skyvia supports Replication with Incremental Updates for such Chargify objects: Coupons, Customers, Events, Invoices, ProductPricePoints, Products, Subscriptions, ProductFamilies.

  • Skyvia supports Synchronization for such Chargify objects: Coupons, Customers, ProductPricePoints, Products, Subscriptions.

  • Coupons object and its peculiarities. When performing a Delete operation, the record is not actually deleted, the record is archived (the date is specified in the ArchivedAt column).

  • Subscriptions object and its peculiarities. Inserting records to the Subscriptions object is complicated by the fact that there is no fixed list of required parameters to successfully create a record. Hence, we do not have required fields, but information about the product and customer must be provided, as well as credit card details can be also required, depending on the specified product.

    The product can be passed, using the ProductId or ProductHandle columns

    The customer can be passed in two ways:

    • you specify an existing customer in the CustomerId column;

    • you specify a new customer, using attributes (column group Customer_xxx).

    Payment profile (credit card details) can be specified, using the attributes Credit Card (column group CreditCard_xxx) or Bank Account (column group BankAccount_xxx).

Chargify Connections

To create a connection to Chargify, you simply need to specify your subdomain and API Key. To start creating a connection, follow the below steps:

  1. Click +NEW in the top menu.
  2. Click Connection in the menu on the left to open the Select Connector page.
  3. In the opened pane, click Chargify.
  4. In the Connection Editor page, specify a connection name that will be used to identify the connection.
  5. Enter subdomain and API key.
  6. Use the Test Connection button to make sure that the connection is successful and then click Create Connection.

    Connection Editor window

Chargify connection has the following parameters:

  • Subdomain — the subdomain of your Chargify site — the fragment of its URL after ‘https://’ before the first dot: https://<subdomain>.chargify.com/
  • API Key — Chargify API key. Read more on how to create and manage API Keys in the Chargify documentation.

Suppressing Extended Requests

For some objects, Chargify API returns only part of the fields when querying multiple records. In order to query values of additional fields, Skyvia performs additional extended requests. Such API requests can be performed for each record of such object. However, this can decrease performance and significantly increase the number of API calls used.

To reduce the number of API calls, you can select the Suppress Extended Requests checkbox. However, please note that some of the fields in such objects will not be available in Skyvia (will return empty values) even if they have values in Chargify because Chargify API does not return them without extended requests.

Supported Actions and Actions Specifics

Chargify connector supports the following actions: