Integration

Zembula + Skio

Skio tracks a next billing date for every subscription, and Zembula can show that date in an email. Zembula can read the subscription by its ID or by the email of the subscriber.

It's our business to grow yours

Book a demo

What Zembula can read from Skio

Skio manages subscriptions for Shopify stores, and its GraphQL API gives Zembula the details of each recurring order. A Skio subscription mirrors a Shopify subscription contract. Zembula can read its status, its next billing date, the number of cycles completed, its currency code, a churn score and any custom attributes. Each subscription has lines.

A line holds a quantity, an amount before discount and a removal date, and it points to a product variant with a title. Zembula can find one subscription by its ID, or it can find the subscriptions of a person by the email on the customer record. Orders and customers come from list queries that take the same arguments. A store admin makes an API token in the Skio dashboard, under API in the left navigation.

That token reads only the data of its own store. One GraphQL endpoint serves all of it, and a query can nest four levels deep, from subscription to line to variant to product. Skio also names a BigQuery integration for bulk export. The email address of a person, or a subscription ID, must reach Zembula in the image URL.

DataDetailLooked up by
SubscriptionStatus, next billing date, cycles completed, currency, churn score and custom attributes.subscription id; customer email
CustomerThe person who holds a subscription, with an email.email
Subscription lineOne product line, with its quantity and removal date.subscription id
Product variantThe variant on a subscription line, with its title.set at setup
OrderAn order that comes from a subscription.set at setup

How the data arrives

  • API: Zembula can read subscriptions, customers and orders from one GraphQL endpoint with an API token for your store.

What you need

  • An API key or a data export from Skio. Zembula sets up the connection for you.
  • An API token that a store admin makes in the Skio dashboard, under API.
  • The email address of a person as a merge tag in the image URL, or a subscription ID.

Limits to plan for

LimitWhat it means
30,000 requests per minute, shared by all API tokens of one store.Open-time reads for the whole store share this rate.

Ideas for email

  • Warn a person before the next billing date and show the subscription lines.
  • Show the cycles completed on a subscription in a loyalty email.
  • Show the product variant titles of a subscription in a renewal email.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.