Integration
Connect Loop Returns to Svix
When New Return Created fires in Loop Returns, your agent runs Add message in Svix. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Loop Returns and Svix to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Loop Returns can start in Svix
When New Return Created in Loop Returns
then Add message in Svix
When Return Status Updated in Loop Returns
then Resend message in Svix
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Loop Returns and Svix
Triggers and actions 2 triggers · 101 actions
Trigger
New Return CreatedTriggers when a new return is created in Loop.
Trigger
Return Status UpdatedTriggers when a Loop return changes state (for example open to closed or cancelled).
Action
Add Product to CollectionAttach a product to a collection.
Action
Add Product to Collection by External IDAttach a product to a collection by commerce `external_id`.
Action
Advanced Shipping NoticeThis endpoint will pull all packages by tracking statuses/timeframe. The ASN endpoint will return an array of
Action
Cancel Draft ReturnCancel a draft return.
Action
Cancel ReturnCancel a return in Loop. Canceling a return will allow a customer to make another return with the same
Action
Close ReturnClose a return. Closing a return will not fulfill any outcomes such as exchanges or gift cards, and the
Action
Create Allowlist ItemCreate an allowlist entry.
Action
Create Blocklist ItemCreate a blocklist entry.
Action
Create Bulk OperationUploads a JSONL file of order, product or other jobs and starts a Loop bulk operation that runs them.
Action
Create DestinationCreate a destination.
Action
Create Fraud ReportAttach a fraud report to a return.
Action
Create Return NotePost a new note to a return.
Action
Delete Allowlist ItemDelete an allowlist entry.
Action
Delete Blocklist ItemDelete a blocklist entry.
Action
Delete CollectionDelete a collection.
Action
Delete Collection by External IDDelete a collection by its commerce `external_id`.
Action
Delete CustomerDelete a customer.
Action
Delete Customer by External IDDelete a customer by its commerce `external_id`.
Action
Delete DestinationDelete a destination.
Action
Delete InventoryDelete an inventory.
Action
Delete Inventory by External IDsDelete an inventory record identified by the product variant's `external_id` and the location's `external_id`. If more than one product variant in the shop shares the same `external_id`, this request returns `409 Conflict`.
Action
Delete LocationDelete a location.
Action
Delete Location by External IDDelete a location by its commerce `external_id`.
Action
Delete OrderDelete a specific order.
Action
Delete Order by External IDDelete a specific order by its commerce `external_id`.
Action
Delete Product by External IDDelete a product by its commerce `external_id`.
Action
Delete Product from CollectionDelete a product from a collection.
Action
Delete Product from Collection by External IDDelete a product from a collection by commerce `external_id`.
Action
Delete Product VariantDelete a product variant.
Action
Delete Product Variant by External IDDelete a product variant by the parent product's commerce `external_id` and the variant's commerce `external_id`.
Action
Detailed Returns ListPull a detailed list of returns created within a given timeframe.
Action
Finalize ItemsFinalizes the returning items and cart items of the draft return.
Action
Flag ReturnFlag a return in Loop for review. This will prevent automated processing and will require a human to go
Action
Get All DestinationsRetrieve all destinations.
Action
Get Allowlist ItemRetrieve an allowlist entry.
Action
Get Blocklist ItemRetrieve a blocklist entry.
Action
Get Bulk OperationGet the details about a specific bulk operation.
Action
Get CollectionGet details about a single collection.
Action
Get Collection by External IDGet details about a single collection by its commerce `external_id`.
Action
Get CustomerGet details about a single customer.
Action
Get Customer by External IDGet details about a single customer by its commerce `external_id`.
Action
Get Destination DetailsGet details for a single destination.
Action
Get Draft ReturnRetrieves the details of a draft return, including its current state, returning items, cart items, and
Action
Get InventoryGet inventory details for a product variant by location.
Action
Get Inventory by External IDsGet inventory details for a product variant at a location, identified by the variant's `external_id` and the location's `external_id`. If more than one product variant in the shop shares the same `external_id`, this request returns `409 Conflict`.
Action
Get LocationGet the details about a single location.
Action
Get Location by External IDGet the details about a single location by its commerce `external_id`.
Action
Get OrderGet details about a specific order.
Action
Get Order by External IDGet details about a specific order by its commerce `external_id`.
Action
Get Product by External IDGet the details about a single product by its commerce `external_id`.
Action
Get Product VariantGet the details about a single product variant.
Action
Get Product Variant by External IDGet the details about a single product variant by the parent product's commerce `external_id` and the variant's commerce `external_id`.
Action
Get Return DetailsGet the details of a specific return based on a return's ID,
Action
Get Return NotesGet notes on a specific return using the return's ID.
Action
Get Shipment InformationGet high level information from a Happy Returns shipment.
Action
Get Shipment ItemsGet all items for a Happy Returns shipment.
Action
Get ShipmentsGet information about all Happy Returns shipments created within a given timeframe.
Action
List Allowlist ItemsRetrieve a list of paginated allowlist entries.
Action
List Blocklist ItemsRetrieve a list of paginated blocklist entries.
Action
List Bulk Operation JobsRetrieve a list of bulk operation jobs.
Action
List Bulk OperationsRetrieve a list of bulk operations. The list can be sorted and paginated using the parameters below.
Action
List CollectionsRetrieve a list of collections. The list can be filtered, sorted, and paginated using the parameters below.
Action
List CustomersRetrieve a list of customers. The list can be filtered, sorted, and paginated using the parameters below.
Action
List InventoriesRetrieve a list of inventories. The list can be filtered, sorted, and paginated using the parameters below.
Action
List LocationsRetrieve a list of locations. The list can be filtered, sorted, and paginated using the parameters below.
Action
List OrdersList all orders.
Action
List ProductsRetrieve a list of products. The list can be filtered, sorted, and paginated using the body parameters below.
Action
List Product VariantsRetrieve a list of product variants. The list can be filtered, sorted, and paginated using the body parameters below.
Action
Look Up Order Return Eligibility by Order NameReport per-line-item return eligibility for an order, by its order name, without starting a return.
Action
Process ReturnProcess a return in Loop based on the return ID. Processing a return will archive it in Loop and
Action
Remove Cart ItemRemoves a specific item from the draft return's cart.
Action
Remove Line ItemsRemove one or more line items from an open return.
Action
Remove Returning ItemRemoves a specific item from the draft return's ReturningItems.
Action
Set AddressSets the return shipping address for the draft return.
Action
Set Credit TypeSets the credit type for the draft return.
Action
Set CustomerSets the customer information for the draft return.
Action
Set Processing TypeSets the processing type (`regular` or `instant`) of the draft return.
Action
Set Returning Item Return TypeSets the return type for a specific returning item.
Action
Submit Draft ReturnSubmits the draft return.
Action
Unfinalize ItemsReopens the returning items and cart items of the draft return for modification.
Action
Update DestinationUpdate a destination.
Action
Upsert InventoryUpsert inventory details for a product variant by location. If the inventory exists, it will be updated; if it doesn't exist, it will be created.
Action
Add applicationCreates a new Svix application, the destination your webhook messages are sent to (usually one per customer).
Action
Add endpointCreates a new webhook endpoint (a destination URL) on a Svix application.
Action
Add event typeCreates a new event type in Svix, or unarchives an existing one with the same name.
Action
Add messageCreates a new message (webhook) in a Svix application and dispatches it to all of the application's subscribed endpoints.
Action
Delete applicationDeletes a Svix application and its endpoints.
Action
Delete endpointDeletes an endpoint from a Svix application so it no longer receives messages.
Action
Get applicationReturns a Svix application by its id or your own UID.
Action
Get endpointReturns a webhook endpoint of a Svix application, including its URL, subscribed event types, channels and status.
Action
Get endpoint secretReturns the signing secret of a webhook endpoint, used to verify that incoming webhooks were sent by Svix.
Action
Get messageReturns a single message (webhook) sent to an application, by its message ID or event ID, including its payload.
Action
List applicationsReturns the applications in your Svix organization, optionally excluding those without active endpoints.
Action
List endpointsReturns the endpoints (webhook destination URLs) configured on a Svix application.
Action
List event typesReturns the event types defined in your Svix environment.
Action
List message attemptsReturns the delivery attempts made for a message, with each attempt's endpoint, URL, status and response.
Action
List messagesReturns the messages (webhooks) sent to a Svix application, optionally filtered by channel, tag, event type or date range.
Action
Resend messageResends an existing webhook message to one of the application's endpoints.
Action
Rotate endpoint secretRotates an endpoint's webhook signing secret. The previous secret stays valid for a grace period (24 hours by default).
Action
Update applicationUpdates an existing Svix application's name, UID, throttle rate or metadata. Only the values you fill in are changed.
Action
Update endpointUpdates selected settings of a webhook endpoint in a Svix application, such as its URL, description, subscribed event types or channels. Fields left blank are unchanged.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Loop Returns
Loop Returns to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Loop Returns to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Loop Returns to MailchimpMailchimp marketing automation and email platform.
Loop Returns to StripeStripe is a payment processing platform for online businesses.
Loop Returns to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Loop Returns to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Svix
HubSpot to SvixHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SvixSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SvixSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SvixGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SvixGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SvixGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Loop Returns and Svix, answered
What can start an automation from Loop Returns?
Any of Loop Returns's 2 triggers in the catalog, including New Return Created and Return Status Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Svix when something happens in Loop Returns?
Any of Svix's 19 actions, including Update application, Update endpoint, Add application and Add endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Svix to Loop Returns?
Svix has no triggers in the catalog today, so automations start in Loop Returns. If you need the other direction, ask: your agent reads Svix's API documentation and adds it.
Do I have to build a connector for Loop Returns or Svix?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Loop Returns and Svix without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.