- Home
- Resources
- Integrations
- Loop Subscriptions
Loop Subscriptions Zapier integrationAutomate Loop Subscriptions with Zapier.
The Loop Subscriptions Zapier integration gives you 9 triggers, 7 actions and 0 searches. All nine triggers are instant: a failed payment, a cancellation or a pause reaches Zapier as it happens. The actions pause, resume, skip, reschedule, cancel, expire or reactivate a subscription.
Verified Trustpilot reviews · AI, automation & growth agency
What the Loop Subscriptions Zapier integration actually does
Loop Subscriptions is a platform that manages recurring orders for brands selling by subscription, with retention in mind. The Zapier integration lets a Zap (an automation built in Zapier) react to what happens to those subscriptions, and change a subscription in Loop from the outside.
Three results come up most. A payment problem nobody misses: Recurring Order Payment Failed starts a Zap the moment a renewal payment fails, so the team hears about it in the tool they read. A cancellation that updates everything else: Subscription Cancelled fires whether the cancellation came from a portal or from another system, and the next step updates your CRM or your spreadsheet. A subscription changed without opening Loop: actions such as Pause Subscription, Skip Next Order or Reschedule Next Order Date act on a subscription when another step supplies its Loop Subscription ID.
All nine triggers are instant. Loop Subscriptions reports each event itself, so the 15-minute wait of the free plan never applies to them.
What Zapier does not do here: there is no search, so a Zap cannot find a subscription by customer name or email. Every action needs the Loop Subscription ID, and the practical source of that ID is a Loop trigger earlier in the same Zap. There is no action to create a subscription either. To weigh other tools, see n8n vs Zapier and Make vs Zapier.
Zapier vocabulary in one minute
Seven words come back across this page. Here they are in plain English.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a subscription being paused. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or changes something for you, like skipping a subscription's next order.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts those, nothing else.
- Polling vs instant
- Zapier checks a polling trigger on a timer. An instant trigger is reported by the app as soon as the event happens. Loop's are all instant.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What a Loop Subscriptions Zap really costs
Zapier bills tasks, and a task is an action that worked. The Loop Subscriptions trigger never costs anything.
- Loop Subscriptions premium appNo, works on the free plan
- Triggers9, all instant
- Free plan100 tasks a month, two-step Zaps
- Failed actionNot billed
Every successful action counts on its own: a Zap with three actions uses three times the tasks of a one-action Zap, and a failed action is not counted. Loop Subscriptions is not a premium app, so the free plan accepts it: 100 tasks a month, unlimited Zaps, two steps per Zap. A Loop trigger followed by one action fits. A filter, say to react only to some cancellations, or a second action makes the Zap multi-step and needs a paid plan. The grid below is how often Zapier checks a polling trigger on each plan. It does not apply to the nine Loop Subscriptions triggers, which are all instant; it only matters when another app's polling trigger feeds a Loop action.
Connect Loop Subscriptions to Zapier in three steps
- 01
Open your Apps page
In your Zapier account, open the Apps page and click + Add connection. A connection is your Loop Subscriptions account linked to Zapier once, then reused by every Loop step.
- 02
Pick Loop Subscriptions
Search for Loop Subscriptions in the dialog, select it, then click Add connection. Use the account of the store whose subscriptions the Zap should watch or change.
- 03
Sign in and grant access
A new tab opens on Loop Subscriptions. Sign in, then grant Zapier access to the account. Back in the editor, the connection appears in the account list of each Loop trigger and action.
Your first Loop Subscriptions Zap
GoalWhen a subscription is cancelled in Loop, check the cancellation with a filter and update the matching contact in your CRM so sales and support see it.
- 01
Create the Zap
Create a Zap and choose Loop Subscriptions as the app that starts it. Pick
Subscription Cancelledin the event list, then your Loop connection. - 02
Test the trigger
Run the test. Zapier brings back the three most recent cancellations of the account, so you map fields on a real subscription instead of placeholders.
- 03
Add the filter
Click the plus icon and add a Filter step. Set the field to look at, the rule and the value. The filter makes this a multi-step Zap, so it needs a paid plan.
- 04
Update the CRM
Add your CRM's update action and map the subscription fields Loop returned into the contact. Test the action once and read what came back.
- 05
Publish
Click Publish. From now on each new cancellation that passes the filter reaches the CRM; earlier cancellations stay as they were.
The 9 Loop Subscriptions triggers
9 events start a Zap when something happens in Loop Subscriptions, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.
Recurring Order Payment Failed
Instant triggerIn Zapier“Triggers when a subscription recurring order payment is failed.”
Fires when the payment of a recurring subscription order fails, the moment a renewal stops bringing in revenue.
Recurring Order Processed
Instant triggerIn Zapier“Triggers when a subscription recurring order is processed via Loop on Shopify.”
Each recurring order that Loop processes on Shopify starts the Zap, one run per renewal.
Subscription Cancelled
Instant triggerIn Zapier“Triggers when a subscription is cancelled in Loop from any portal or programatically.”
Reacts to a cancellation, whether it came from one of Loop's portals or was triggered programmatically by another system.
Subscription Expired
Instant triggerIn Zapier“Triggers when a subscription is expired in Loop from any portal or programatically.”
Starts the Zap when a subscription reaches the expired state in Loop, from any portal or another system.
Subscription Paused
Instant triggerIn Zapier“Triggers when a subscription is paused in Loop from any portal or programatically.”
When a subscription is put on hold, from a portal or another system, this trigger hands the details to Zapier.
Subscription Reactivated
Instant triggerIn Zapier“Triggers when a subscription is reactivated in Loop from any portal or programatically.”
Catches the comeback: a cancelled or expired subscription switched back on in Loop starts the Zap.
Subscription Rescheduled
Instant triggerIn Zapier“Triggers when a subscription is rescheduled in Loop from any portal or programatically.”
Runs when the schedule of a subscription changes in Loop, for instance a next order moved to another date.
Subscription Resumed
Instant triggerIn Zapier“Triggers when a subscription is resumed in Loop from any portal or programatically.”
Fires as a paused subscription starts again, whether the subscriber resumed it or another system did.
Subscription Updated
Instant triggerIn Zapier“Triggers when a subscription is updated in Loop from any portal or programatically.”
The broadest trigger of the nine: any update to a subscription in Loop starts the Zap.
The 7 Loop Subscriptions actions
Loop Subscriptions gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Cancel Subscription
ActionIn Zapier“Cancels a subscription in Loop. You can optionally provide a cancellation reason, add a comment, notify the customer, or schedule the cancellation for the end of the current billing cycle.”
Ends a subscription in Loop, with an optional reason, a comment and a notification email to the customer.
Expire Subscription
ActionIn Zapier“Expires a subscription in Loop, preventing any future orders from being generated for the subscription.”
Expires a subscription so Loop generates no further orders for it.
Pause Subscription
ActionIn Zapier“Pauses a subscription in Loop either indefinitely or for a specified duration. Optionally, you can set an automatic resume date for the subscription.”
Puts a subscription on hold, with no end date or for a set duration, and can set a date for it to resume on its own.
Reactivate Subscription
ActionIn Zapier“Reactivates a canceled subscription in Loop, restoring it to an active state and allowing future orders to be generated according to its configured schedule.”
Brings a cancelled or expired subscription back to active, and future orders follow its configured schedule again.
Reschedule Next Order Date
ActionIn Zapier“Updates the next order date for a subscription in Loop by rescheduling its upcoming billing and delivery cycle.”
Moves the date of the upcoming order, and optionally every later one, with or without telling the customer.
Resume Subscription
ActionIn Zapier“Resumes a paused subscription in Loop, allowing it to continue generating future orders according to its configured schedule.”
Restarts a paused subscription, which then generates orders again on its configured schedule.
Skip Next Order
ActionIn Zapier“Skips the next scheduled order for a subscription without affecting future billing or delivery schedules.”
Skips only the next scheduled order, leaving later billing and deliveries as they were.
When a Loop Subscriptions Zap breaks
Zapier attaches no help article to Loop Subscriptions and documents no limit specific to the app. What breaks comes from Zapier's general rules.
Three cases explain most subscription Zaps that stall or spin. For anything else, see Zapier troubleshooting.
Past events are never replayed
A Zap only reacts to what happens after you publish it. Cancellations or failed payments from before are not picked up; handling them is a separate job.A Loop action sets off its own trigger
A Zap on Subscription Updated that runs a Loop action can update the subscription again, which starts the Zap again and burns through tasks.A bulk change gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.
Need help automating Loop Subscriptions with Zapier?
A person reads every message.



