Connect Skio to Rig

    Sync your Skio subscriptions, orders and customers into Rig, along with products and the sessions and reasons from your cancel flows. Skio connects with a single API token that a Skio admin generates.

    Before you start

    • You need a Skio admin login, because the API token is generated in the Skio dashboard.

    Step 1: Get your Skio API token

    1. Sign in to the Skio dashboard as an admin and click API in the left navigation.
    2. Name the token and click Generate.
    3. Copy the token straight away, because Skio shows it only once. Rig sends it to Skio using Skio's own API authorisation scheme.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Skio, open the card and click Connect.
    3. API token: paste the token your Skio admin generated.
    4. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Skio lands in its own skio schema in your warehouse:

    • Core: subscriptions, orders and users.
    • Cancel flows: cancel flow sessions, reasons and rebuttals, across all three versions.
    • Catalogue and messaging: products, product variants and SMS messaging history.

    These streams are off by default because they are large: billing attempts, audit logs, subscription lines, order line items, discounts, order discount applications, selling plans, selling plan groups, policies, pricing policies and payment methods. Switch on the ones you need when you choose streams.

    Good to know

    • Subscriptions and users sync incrementally on their last update time, so a status change is picked up on the next run. Orders sync on creation time, because Skio orders do not change after they are placed.
    • Skio limits each request to a depth of four and 100 records, so large first loads take several pages of requests.
    • Billing attempts load their history once and then sync nightly, so switching them on gives you a recent window first.
    • To disconnect Skio, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Track subscription MRR and recurring revenue
    • Measure churn and retention by cohort
    • Forecast upcoming charges and revenue
    • Recover revenue lost to failed payments

    More ideas for using Skio

    Skio documentation

    Was this guide helpful?