Loop Returns Connector

Connect Loop Returns so Applied can look up returns, create return links, and run guided return actions from Flows.

Use this Connector when support conversations depend on return status, exchanges, return deep links, or operational return actions.

Common use cases

• Look up detailed return information.
• Create a return deep link for a customer.
• Process, cancel, flag, or close a return after approval.
• Add return notes or inspect return history.
• Coordinate return workflows with order and customer context.

Some return actions are irreversible or customer-visible. Use confirmation steps before calling them from a Flow.

Before you begin

Before connecting Loop Returns, make sure:

• You can access Loop Admin for the store.
• Your team knows which return actions Applied should run.
• You know whether Applied needs only return lookup or broader order/developer access.
• You have a test return available for validation.

Get a Loop Returns API key

Loop API keys are created in Developer Tools.

1. In Loop Admin, go to Returns Management.
2. Open Tools & integrations.
3. Open Developer Tools.
4. Click Generate API key.
5. Add the scopes Applied needs.
6. Copy the API key.

Applied sends this key in the X-Authorization header.

Choose Loop scopes

Use the narrowest scopes that cover your workflows:

• Returns for return lookup, return details, processing, cancellation, closing, notes, grading, disposition, and return fraud report operations.
• Orders if Applied will create return deep links or manage order-related allowlist or blocklist workflows.
• Developer Tools if Applied support helps manage webhooks.

If Loop returns 401 Unauthorized, check both the token value and the scopes on the key.

Connect Loop Returns in Applied

1. Open Connectors.
2. Click New.
3. Choose Loop Returns.
4. Paste the Loop API key into the API token field.
5. Create the connection.

Validate the connection

After setup:

1. Look up a test return.
2. Confirm the return status and order name match Loop.
3. Create a return deep link only for a test order.
4. Run write actions such as cancel or close only in a controlled test case.

Common issues

Loop says the key is unauthorized

Confirm the key was copied from Developer Tools and includes the scope for the endpoint Applied is calling.

Return lookup works, but actions fail

Read scopes may not be enough. Add the relevant Returns write scope for the action your Flow runs.

Deep link creation fails

Confirm the API key includes the Orders scope required for return deep link workflows.

Provider docs

• Loop API authentication 
• Loop return actions 
• Loop webhook setup 

Next steps

• Understanding Connectors
• Automated Workflows
• Shopify Connector