Subi has an app on Zapier. With it, a change to a subscription in Subi can start a Zap, for example to give a customer access to your community or app when they subscribe and take it away when they cancel, or to keep their profile in your CRM in step with their subscription. A Zap can also act on a subscription in Subi: cancel, pause, resume, skip the next order or move the next billing date.
The app is not in Zapier's app directory, so you add it to your Zapier account with an invite link, as below.
What you need
An API key from Subi. Open Settings > API keys in Subi, click Generate API key and give the key a name. The key is shown only once, so copy it or click Save to download it. If a key is already listed there, another tool may be using it: use that key if you have it, because Rotate makes a new one and stops the old one working everywhere. If the page shows a lock instead, see What your store needs in the Subi API guide.
A Zapier account. Filter by Zapier steps, and any Zap with more than two steps such as the recipe further down, need a paid Zapier plan.
How to connect Subi to Zapier
Sign in to Zapier, then open the Subi app invite and accept it.
Create a Zap and search for Subi as the trigger or action app.
When Zapier asks you to connect your account, paste your Subi API key.
What the app can do
Zapier checks the triggers every 1 to 15 minutes, depending on your Zapier plan, so a Zap starts a little after the change rather than at once.
New Subscription starts a Zap when a customer starts a subscription.
Subscription Cancelled starts one when a subscription is cancelled.
Subscription Payment Failed starts one when a renewal payment fails. It can run again for the same subscription while its payment is still failing.
Subscription Updated starts one when a subscription changes, for example a pause, a resume, a skip, a new next billing date or a renewal. Changes made between two checks arrive as one run, showing the subscription as it is at that check.
Three searches help a Zap find what it needs:
Get Subscriber finds the customer's email, first name and last name from the Shopify customer ID a trigger gives you.
Find Subscriber finds a subscriber by email address.
Find Subscription finds a customer's subscriptions by their Shopify customer ID, and by status if you choose one.
The actions are Cancel Subscription, Pause Subscription, Resume Subscription, Skip Next Order and Reschedule Subscription (a new next billing date). Each takes the subscription contract ID.
Recipe: give and take away access in another tool
This works with any tool on Zapier that has a step to remove a member by email, or to remove the tag or list that gives access. Check that your tool has that step before you build the Zap.
Trigger: Subi, Subscription Cancelled.
Search: Subi, Get Subscriber. Map Shopify customer ID to the trigger's Shopify customer ID.
Action: your tool's step that removes the member, tag or list. Map its email field to the Email from the Get Subscriber step.
Build a second Zap the same way with New Subscription and your tool's step that gives access.
A subscription with a set number of payments ends as EXPIRED, not cancelled. To take access away then too, add a Zap on Subscription Updated with a Filter by Zapier step that continues only when Status is EXPIRED.
To take access away on a pause, use Subscription Updated with a Filter that continues only when Status is PAUSED. It also lets through later changes to a subscription that is still paused, so the step after it should be safe to run twice. If you do this, give access back on a resume with another Zap: Subscription Updated, a Filter that continues only when Status is ACTIVE, then your tool's step that gives access. That Zap also runs on every renewal, so use a step that accepts someone who already has access.
Good to know
Each API key can make 60 requests a minute.
If more than 100 subscriptions change at once, for example on a busy renewal day, Zapier holds the runs and asks you to confirm them.
Changes made while a Zap is off for more than 6 hours are not picked up when you turn it back on.
If you need a change the moment it happens, Subi's webhooks can send it to Zapier at once. See Sending Subi webhooks to Zapier or Make.
If you rotate your API key in Subi, reconnect Subi in Zapier with the new one.