Integration

Zembula + Loop Returns

Zembula can look up a Loop Returns return by its order name, and the return lists a reason and exchange detail for each item. Zembula can show those in your email.

It's our business to grow yours

Book a demo

What Zembula can read from Loop Returns

Loop Returns manages returns and exchanges for Shopify merchants, and Zembula can read the data of a return for your email. Zembula can look up a return by its return ID, its order ID or its order name. The return links to its order. Each line item in a return lists the SKU, the quantity, the reason and the exchange detail.

A package view lists return packages by tracking status or time window. Loop also sends webhooks. They cover a return that is created, updated or closed, and a label that is created or updated. They also cover a restock request, a gift card request and a processed shipment.

Your team creates an API key in Loop Admin and sets its scopes. 0 instead. Loop allows 300 requests per minute for each API key and answers HTTP 429 above that. The return ID, order ID or order name reaches Zembula in the image URL, from a merge tag of your email service provider.

DataDetailLooked up byHow fresh
Return detailsOne return request with its order link.return id, order id or order nameopen time
Return line itemsSKU, quantity, reason and exchange detail of each item.return idopen time
Return packagesReturn packages with their tracking status.time window and tracking statusset at setup
Return eventsEvents such as return created, updated or closed.set at setupset at setup

How the data arrives

  • API: Zembula can read return details from the Loop API with a key that your team creates in Loop Admin.
  • Webhook: Loop sends webhooks for return, label, restock, gift card and shipment events.
  • ESP merge tags: The return ID, order ID or order name travels in the image URL from your merge tag.

What you need

  • An API key or a data export from Loop Returns. Zembula sets up the connection for you.
  • OAuth 2.0 for the Label, Webhooks and Ship by Loop APIs. Other endpoints accept API keys.
  • A return ID, order ID or order name in your email service provider, sent as a merge tag.

Limits to plan for

LimitWhat it means
300 requests per minute for each API key; HTTP 429 when exceeded.Plan for at most 300 return reads each minute for each key.

Ideas for email

  • Show the return reason and the exchange item in a return confirmation.
  • Show the returned item SKU in a win-back email.
  • Show the return details when a person opens a return update.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.