Integration
Connect ilert and Returnless
When New or Updated Incident fires in ilert, your agent runs Find customers in Returnless, or Request Created in Returnless to Find User on Call in ilert. 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 ilert and Returnless 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 ilert and Returnless can do together
From ilert to Returnless
When New or Updated Incident in ilert
then Find customers in Returnless
When New or Updated Incident in ilert
then Add note in Returnless
From Returnless to ilert
When Request Created in Returnless
then Find User on Call in ilert
When Return Created in Returnless
then Add Alert in ilert
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 ilert and Returnless
Triggers and actions 3 triggers · 28 actions
Trigger
New or Updated IncidentTriggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.
Action
Accept IncidentAccepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.
Action
Add AlertCreates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).
Action
Add maintenance windowCreates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.
Action
Create IncidentCreates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.
Action
Find User on CallFinds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.
Action
Get alertReturns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.
Action
Get incidentReturns a single ilert incident by its id, including its status, severity, affected services and responders.
Action
Get maintenance windowFetches a maintenance window by ID. An error occurs if the maintenance window is not found.
Action
List Alert SourcesReturns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.
Action
List incidentsReturns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.
Action
List usersReturns the users in your ilert account, with their name, email, role and contact settings.
Action
Resolve IncidentResolves an ilert alert (formerly called an incident), closing it and stopping further escalation.
Trigger
Request CreatedTriggers when a customer creates a new return request that needs approval.
Trigger
Return CreatedTriggers when a new return is created, including a request once it is approved.
Action
Add noteAdds an internal note to a return or return request.
Action
Add RequestCreates a return request in Returnless for items from an existing sales order.
Action
Approve a RequestApproves a return request in Returnless so the customer can send the items back.
Action
Approve a Request Without ShipmentApproves a pending return request without a return shipment, so the customer keeps the items.
Action
Find customersReturns the customers in your Returnless account that match an email address.
Action
Find productsReturns the products in your Returnless account that match a SKU.
Action
Find RequestsFinds a Request in your Returnless account.
Action
Find ReturnsFinds returns (return orders) in Returnless by return number.
Action
Find sales ordersFinds sales orders in Returnless by order number.
Action
Get customerReturns a single Returnless customer by its id.
Action
Get Request (By Request ID)Returns a single return request (return order) from Returnless by its ID.
Action
Get Return (By Return ID)Returns a single return in Returnless, with all of its details, by its return ID.
Action
Get sales orderReturns a single sales order by its ID, including its customer, address and order details.
Action
List return reasonsReturns the return reasons configured in your Returnless account.
Action
Reject RequestRejects a pending return request in Returnless.
Action
Update returnChanges the status of a return, such as Checked, Approved or Resolved.
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 ilert
ilert to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ilert to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ilert to MailchimpMailchimp marketing automation and email platform.
ilert to StripeStripe is a payment processing platform for online businesses.
ilert to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
ilert to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Returnless
HubSpot to ReturnlessHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ReturnlessGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ReturnlessGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ReturnlessGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ReturnlessGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ReturnlessMailchimp marketing automation and email platform.
Questions
ilert and Returnless, answered
What can start an automation from ilert?
Any of ilert's 1 trigger in the catalog, including New or Updated Incident. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Returnless when something happens in ilert?
Any of Returnless's 16 actions, including Update return, Add note, Add Request and Approve a Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Returnless to ilert?
Yes. When something happens in Returnless, your agent can act in ilert too. This page covers both directions: Returnless's triggers and ilert's actions are listed here as well.
Do I have to build a connector for ilert or Returnless?
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 ilert and Returnless 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.