# Connect Loop Returns to Zendesk and automate your tasks

## Why integrate Loop Returns with Zendesk

The Loop Returns to Zendesk integration helps you sync data, automate manual tasks, and keep your stack aligned — without writing code.

### Update Shopify customer records when a return is initiated

When a customer starts a return in Loop, MESA updates their Shopify record with the relevant details — return reason, product, order value. Your team and connected tools have the full picture before the return is even completed.

### Trigger retention workflows the moment a return is filed

When a customer initiates a return in Loop, MESA kicks off the right response — a Klaviyo win-back flow, a Slack alert to the right team member, a loyalty point adjustment in Rivo. You act on the signal while the customer relationship is still recoverable.

### Route high-value return events to your team before they escalate

When a VIP customer, a large-order return, or a repeat returner is flagged in Loop, MESA notifies the right person through Slack or email with the order context already attached. Your team responds before the situation becomes a churn event.

### Create Zendesk tickets from Shopify order events automatically

When an order is flagged — a failed fulfillment, a return request, a delayed shipment — MESA opens a ticket in Zendesk with the order details already attached. Your support team works the issue without hunting for context.

### Keep Shopify customer data current when tickets are resolved

When a Zendesk ticket is closed or a resolution is logged, MESA updates the customer's record in Shopify — tags, notes, fields. Your store reflects what your support team learned without anyone syncing it manually.

### Route support tickets based on order and customer details

When a ticket arrives in Zendesk, MESA reads the associated Shopify data — order value, customer tier, product type — and applies the right tags, priority, or assignee. Every ticket lands with the right team from the start.

## Build any Loop Returns and Zendesk automation

MESA helps you connect apps to automate repetitive tasks. A trigger is an event that starts a workflow, and actions are the steps that occur when it's running.

###### Attachment Linked to Ticket Comment

Starts when an attachment is linked to a ticket comment.

- ID
- Subject
- Description
- Created At
- Updated At
- Status
- Priority
- Type
- Actor ID
- Requester ID
- Submitter ID
- Assignee ID
- Organization ID
- Group ID
- Brand ID
- Form ID
- External ID
- Is Public
- Tags
- Custom Status
- Via
- Event

###### Attachment Redacted from Ticket Comment

Starts when an attachment is permanently redacted from an existing comment on a ticket.

###### Comment Created

Starts when a comment is created.

###### Comment Made Private

Starts when a comment is made private.

###### Ticket Agent Assignment Changed

Starts when a ticket is reassigned to another agent.

###### Ticket Brand Updated

Starts when a brand associated with the ticket is updated.

###### Ticket Created

Starts when a ticket is created.

- ID
- Subject
- Description
- Created At
- Updated At
- Status
- Priority
- Type
- Actor ID
- Requester ID
- Submitter ID
- Assignee ID
- Organization ID
- Group ID
- Brand ID
- Form ID
- External ID
- Is Public
- Tags
- Custom Status
- Via

###### Ticket Custom Field Updated

Starts when a ticket's custom field is updated.

###### Ticket Status Updated

Starts when a ticket's status is updated.