Zapier connects Loop to thousands of other apps through automated workflows called Zaps. A Zap uses a trigger (an event in Loop) to start a workflow and an action (an event in another app) to complete it. This article covers how the integration works, how to connect Loop to Zapier, the triggers and actions available, and common use cases.
How it works
A Zap has two parts that work together to automate a task across apps.
Trigger: an event in one app that starts the workflow.
Action: an event in another app that Zapier performs automatically after the trigger fires.
When something happens in Loop, such as a subscriber creating a subscription, Zapier can instantly perform a related action in another app, like adding the customer to your CRM. You build Zaps directly in Zapier, so no code is required to connect Loop to the apps you already use.
Note: The Zapier integration is available on the Pro plan. Your store must be on the Pro plan to generate an API token and connect Loop to Zapier.
Setting up Zapier with Loop
You connect Loop to Zapier using an API token generated from Loop admin. Once connected, you can build Zaps that use Loop as a trigger, an action, or both.
Prerequisites
An active Loop account on the Pro plan
A Zapier account
Step 1: Get your Loop API token
Navigate to Loop admin > Settings > Admin > API tokens.
Click on Show token and then copy the API token
If you don't have a token, click on Create token to generate a one
Keep this token ready, as you will paste it into Zapier when connecting your account.
Note: Treat your API token like a password. Anyone with the token can access your Loop data through Zapier, so do not share it publicly.
Step 2: Connect Loop and Zapier
Log in to your Zapier account and click on App connections
Click on Add connection and search for Loop subscriptions
Paste the API token you copied from Loop admin and click on Connect
Once the token is validated, you will be able to see the Loop connection under connections section
Step 3: Configure your trigger
The trigger is the event that starts your Zap. Select Loop subscriptions as your trigger app
Then choose one of the available triggers listed below, such as Subscription cancelled or Subscription paused.
After selecting a trigger event, select your Loop account that you connected with Zapier and click on Continue
Now click on Test trigger to confirm it is set up correctly.
Step 4: Add your action
Actions are the events your Zap performs after it is triggered. Add an action from another app, or select Loop as the action app to perform a subscription action such as Pause subscription or Skip next order.
After configuring your action, click Test step to confirm it works as intended.
Step 5: Publish your Zap
Once your trigger and action are tested, publish the Zap. Zapier then runs your action automatically whenever the trigger event occurs in Loop.
Available triggers
The following triggers are available when you select Loop as the trigger app in Zapier.
Trigger | Trigger definition | Use case |
Subscription cancelled | Fires when a subscription is cancelled | Add the customer to a win-back or retention campaign |
Subscription paused | Fires when a subscription is paused | Send a re-engagement reminder before the next order resumes |
Subscription resumed | Fires when a paused subscription is resumed | Restart fulfillment or marketing workflows for the subscriber |
Subscription updated | Fires when a subscription's details change | Sync the updated subscription with your data warehouse |
Subscription reactivated | Fires when a cancelled subscription is reactivated | Re-enroll the subscriber in rewards or post-purchase flows |
Subscription expired | Fires when a subscription expires | Remove the subscriber from active fulfillment lists |
Recurring order processed | Fires when a recurring order is successfully processed | Create a fulfillment task or send an order confirmation |
Recurring order payment failed | Fires when a recurring order payment fails | Create a support ticket or send a payment retry reminder |
Subscription rescheduled | Fires when a subscription's next order date changes | Update your logistics tool to adjust delivery forecasting |
Available actions
The following actions are available when you select Loop as the action app in Zapier.
Action | Description |
Cancel subscription | Cancels an active subscription |
Pause subscription | Pauses an active subscription |
Resume subscription | Resumes a paused subscription |
Reactivate subscription | Reactivates a cancelled subscription |
Expire subscription | Expires a subscription |
Reschedule next order date | Changes the date of the next recurring order |
Skip next order | Skips the next scheduled recurring order |
Use cases
You can combine Loop triggers and actions with other apps to automate subscription workflows across your stack. The examples below show how merchants connect Loop to their CRM, support tools, and marketing platforms.
Win back cancelled subscribers
When a subscriber cancels, you can automatically add them to a retention campaign and alert your team to follow up.
Trigger: Subscription cancelled
Actions:
Add the customer to a win-back email list
Create a task in your CRM for the retention team
Recover failed payments
When a recurring order payment fails, you can notify the customer and flag the account for your support team.
Trigger: Recurring order payment failed
Actions:
Send a payment retry reminder to the customer
Create a support ticket with the order details
Troubleshooting
Use the following tips to resolve common issues with the Loop Zapier integration.
Authentication errors
If your connection fails or returns an authentication error, generate a new API token in Loop admin > Settings > Admin > API tokens and reconnect your account in Zapier.
Resource not found
If an action returns a not found error, confirm that the subscription or customer exists in Loop before attempting to update or cancel it.
Action did not run
If a published Zap does not perform its action, return to Zapier and re-test both the trigger and the action steps to confirm each is configured correctly.
Note: For additional help with building or debugging Zaps, contact Zapier's support team.
Considerations
Consider the following when using Zapier with Loop.
Consideration | Notes |
Plan requirement | The Zapier integration requires the Pro plan. API tokens can only be generated on the Pro plan. |
API limitations | API rate limits apply to all calls made through Zapier. High-volume workflows may be throttled. |
Authentication | Your store must be connected with a valid API token before building a Zap. Regenerate the token if the connection stops working. |
Need help?
No worries - we're here for you!
If you have any questions or need assistance, feel free to email us at [email protected] or chat with us using the support beacon at the bottom right of your screen.
Regards,
Loop subscriptions team 🙂