Resources · Zapier integration

Loop Returns Zapier integrationAutomate Loop Returns with Zapier.

Loop Returns Zapier integration: 4 triggers, 4 actions, 0 searches. Every new return, status change and label in Loop can start an automation the moment it happens, and four actions move a return along from another tool: process, close, flag or cancel.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Loop Returns Zapier integration does for your returns

The Loop Returns Zapier integration connects Loop, the exchange-first returns platform built for Shopify brands, to the rest of your tools. Loop reports new returns, status changes and labels to Zapier as they happen, and Zapier can act on a return in Loop by its ID. It needs Loop Plus or the Loop Integrations Add-On.

Three results come out of it. A team that hears about returns at once: New Return Created fires when a customer opens a return, so the support channel sees it without anyone watching the Loop dashboard. Returns that get a second look: a Zap can run Flag Return on the returns that meet a condition you set, so they stand out for a manual check. Status changes that travel: Return Status Updated fires when a return moves on, and the next step can update a sheet or another tool the team uses.

What Zapier does not do here matters just as much. There is no search step: a Zap cannot look up a return by order or customer, so every action needs the Return ID from an earlier step. Loop does not let Zapier create a return or a label either. Returns start in Loop; Zapier listens and nudges.

To weigh Zapier against the two other big names on broader criteria, read n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier words, in plain English

Seven words come back on every line below. Here is what each one means in practice.

Zap
The automation you build on 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. Once the Zap is on, Zapier waits for it. Loop Returns offers four of them.
Action
What the Zap does once started: the step that writes, sends or moves something. Loop Returns has four, all acting on a return.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. All four Loop Returns triggers work this way.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
Cost

What a Loop Returns Zap really costs

Loop Returns is not a premium app on Zapier, so it runs on the free plan. On the Loop side, though, the connection needs Loop Plus or the Loop Integrations Add-On.

  • Any Loop Returns trigger0 task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Loop sideLoop Plus or Loop Integrations Add-On

The four triggers cost nothing, however many returns come in. Each action that succeeds costs one task, whether it posts a message elsewhere or flags a return in Loop; a failed action is not counted. The free plan gives 100 tasks a month and Zaps of two steps: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below is Zapier's grid for polling triggers; it does not apply to Loop Returns, whose four triggers are all instant.

Connect

Connect Loop Returns to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. You need a Loop account on Loop Plus or with the Loop Integrations Add-On, and access to the store's returns.

  2. 02

    Pick Loop Returns

    Type Loop Returns in the search box of the dialog that opens, pick it from the list of results, then click Add connection. A new tab opens on the Loop side.

  3. 03

    Sign in and grant access

    Sign in to Loop in that tab and grant Zapier access to the account. The connection then shows up in Apps, and every Loop Returns step of every Zap reuses it.

First Zap

Your first Zap: flag the returns that need a check

GoalEach new return that meets the condition you set in a filter gets flagged in Loop, so the team checks it by hand.

  1. 01

    Set the trigger

    Build the Zap from Loop Returns and New Return Created. It is instant: Loop reports each return the moment a customer opens it, whatever your plan.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent returns of the connected account, so you build the filter on a real return and its real fields.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value. The Zap is now multi-step, so it needs a paid plan.

  4. 04

    Add Flag Return

    Pick Loop Returns and Flag Return, then map the Return ID that came with the trigger. Test the step and check in Loop that the return now carries its flag.

  5. 05

    Publish

    Click Publish. From then on, every new return that passes the filter gets flagged in Loop straight away, and the others go through untouched.

Triggers

The 4 Loop Returns triggers

4 events start a Zap when something happens in Loop Returns, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Label Updated

Instant trigger

In Zapier“Triggers when a label is updated.”

Fires when a label already attached to a return changes in Loop, and passes the new details to the steps that follow. It keeps any copy of that label elsewhere in step with Loop.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the team tracks labels in a sheet, and an edit in Loop should overwrite the old line rather than leave it stale.
Watch out
an update is not a creation. Pair it with a step that changes an existing record, not one that adds a new row each time.
2

New Label Created

Instant trigger

In Zapier“Triggers when a new label is created.”

Starts a Zap the moment Loop creates a new label for a return. The label's details become fields the next steps can map.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
whoever handles incoming parcels wants a line per label in a shared sheet, without opening Loop.
Watch out
a later change to that label will not fire this trigger again. Add a second Zap on Label Updated if the copy has to follow edits.
3

New Return Created

Instant trigger

In Zapier“Triggers when a new return is created.”

Goes off each time a customer opens a return in Loop. The return arrives in Zapier with its fields, including the Return ID every Loop action needs.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
support should hear about every return in its chat channel, or some returns should be flagged for a manual look.
Watch out
this is the natural source of the Return ID. Without a search step, a Zap that skips it has no clean way to point an action at a return.
4

Return Status Updated

Instant trigger

In Zapier“Triggers when the status of a return is updated.”

Fires whenever the status of a return changes in Loop, so other tools can follow each return from opening to close.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a customer service tool or a reporting sheet has to show where each return stands without anyone copying it over.
Watch out
Process Return, Close Return and Cancel Return change a status too. A Zap on this trigger that runs one of them can set itself off again.
Actions

The 4 Loop Returns actions

Loop Returns gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Return

Action

In Zapier“Cancels a return inside Loop.”

Cancels a return in Loop, picked by its Return ID, from whichever app holds the reason.

When to use it
a return was opened by mistake and is withdrawn in another tool, and Loop should drop it as well.
Watch out
cancelling is final from the Zap's side. Test it on a return you can afford to lose before you publish.
2

Close Return

Action

In Zapier“Closes a return inside Loop”

Closes a return inside Loop, named by its Return ID, once the case is settled elsewhere.

When to use it
the team settles certain returns in another tool, and Loop should not keep them open.
Watch out
closing changes the status, so a Zap built on Return Status Updated that closes returns can start itself again.
3

Flag Return

Action

In Zapier“Flags a return inside Loop.”

Puts a flag on a return in Loop, so it stands out for someone to look at.

When to use it
returns that meet a condition you set in a filter need a human check before anyone processes them.
Watch out
the filter is what decides which returns get flagged, and it makes the Zap multi-step, so it needs a paid plan.
4

Process Return

Action

In Zapier“Processes a return inside Loop.”

Pushes a return through processing in Loop from another app, using its Return ID.

When to use it
a check done outside Loop clears the return, and processing should follow without someone clicking in the dashboard.
Watch out
make sure the trigger really means the return is ready. A Zap cannot undo processing for you.
When it breaks

When a Loop Returns Zap breaks

Zapier ties no help article to Loop Returns and documents no rate limit for it. What breaks comes from Zapier's own rules and from the Return ID every action needs.

Four cases come back most often. When a Zap stops for a reason not listed here, the Zapier troubleshooting page goes further.

  • The Zap keeps restarting itself

    A Zap on Return Status Updated that processes, closes or cancels the same return changes its status, which fires the trigger again and burns tasks.

  • The action has no Return ID

    Every Loop action needs a Return ID, and no search can find one. Start the Zap on a Loop trigger that carries it, or the step cannot run.

  • Older returns never show up

    A Zap only reacts to what happens after you publish it. Returns opened before are not picked up and need a separate one-off export.

  • A wave of returns is held back

    After a bulk import or a migration, a trigger can return a huge batch at once, and Zapier's flood protection can hold that batch back.
Need help

Need help automating Loop Returns with Zapier?

A person reads every message.

FAQ

Loop Returns and Zapier: common questions

01Is the Loop Returns Zapier integration free?
On the Zapier side, yes, within the free plan's limits. Loop Returns is not a premium app, so the free plan accepts it, with 100 tasks a month and Zaps of two steps. New Return Created followed by one chat message fits. Add a filter to flag only some returns, or a second action, and the Zap becomes multi-step, which needs a paid plan. On the Loop side, the connection needs Loop Plus or the Loop Integrations Add-On.
02How many tasks does a Loop Returns Zap use?
One task per action that succeeds, each time the Zap runs. A Zap that posts every new return in team chat uses one task per return. A Zap that flags some returns and also notifies the team uses two for each return that passes the filter, and none for the others, since the filter stops them before any action. The triggers cost nothing, and a failed action is not counted. Busy return periods multiply runs, so estimate the volume first.
03Does Loop Returns work in real time with Zapier?
Yes. All four Loop Returns triggers are instant: Loop tells Zapier the moment a return is created or changes status, or a label is created or updated, and the Zap starts right away, whatever the plan. The plans' interval grid, from 15 minutes on Free down to 1 on Team and Enterprise, only concerns polling triggers, and this app has none. In the editor, such Zaps show a lightning bolt. The actions then run in order.
04What does connecting a Loop Returns account take?
A Loop account on Loop Plus or with the Loop Integrations Add-On, plus access to the store's returns. In Zapier, open Apps, click + Add connection, search for Loop Returns and click Add connection. A tab opens: sign in to Loop and grant Zapier access. Every Loop Returns step then reuses that connection. Before setting up an action, plan where the Return ID will come from, since all four require it.
05Why does a Loop Returns Zap keep triggering itself?
Because the action changes what the trigger watches. A Zap that starts on Return Status Updated and then runs Process Return, Close Return or Cancel Return changes the status of that same return, and Loop reports the change, which starts the Zap again. Each round costs tasks. Add a filter that lets through only the status that should lead to the action, or start the Zap from New Return Created instead.
06What if the Loop Returns operation for the job is missing?
Then the Zap works with the eight that exist: four triggers and four actions. Zapier offers no step to create a return or a label in Loop, none to edit a return's details, and no search to find a return by order or customer. Returns begin in Loop, and Zapier picks them up from there. When the job needs something else, it usually stays in Loop itself, with Zapier passing the news on.
07Zapier, Make or n8n for Loop Returns?
Compare them on criteria rather than on a name. Coverage first: on Zapier, Loop Returns offers four instant triggers and four actions, so check what the other platform exposes for the same app. Speed next: the four triggers fire straight away on every Zapier plan. Then volume: Zapier bills one task per successful action, and return-heavy periods multiply runs. Last, the Loop side: connecting Loop to Zapier needs Loop Plus or the Loop Integrations Add-On, a cost to count in.
Same platform

Other docs you might need on this stack.

Browse all integrations