Integration
Connect ilert to Qase
When New or Updated Incident fires in ilert, your agent runs Add project in Qase. 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 Qase 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 can start in Qase
When New or Updated Incident in ilert
then Add project in Qase
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 Qase
Triggers and actions 1 trigger · 39 actions
- New or Updated Incident
Triggers 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.
- Accept Incident
Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.
- Add Alert
Creates 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).
- Add maintenance window
Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.
- Create Incident
Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.
- Find User on Call
Finds 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.
- Get alert
Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.
- Get incident
Returns a single ilert incident by its id, including its status, severity, affected services and responders.
- Get maintenance window
Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.
- List Alert Sources
Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.
- List incidents
Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.
- List users
Returns the users in your ilert account, with their name, email, role and contact settings.
- Resolve Incident
Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.
- Add defect
Adds a new defect to a Qase project.
- Add milestone
Creates a milestone in a Qase project.
- Add project
Create a new project.
- Add run
Create a new test run in a project.
- Add test case
Create a new test case in a project.
- Add test run result
Create a result for a test run.
- Complete run
Mark a specific test run as completed.
- Delete project
Delete a project by code.
- Delete run
Delete a test run by id.
- Delete test case
Delete a test case by id.
- Find entities by QQL
Searches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.
- Get defect
Get a specific defect by id.
- Get project
Get a project by its code.
- Get run
Retrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.
- Get test case
Get a specific test case by id.
- Get test run result
Get a test run result by hash code.
- List defects
Returns all defects in a Qase project, optionally filtered by status.
- List milestones
Get all milestones in a project.
- List projects
Lists every project available to the connected Qase account.
- List runs
Get all test runs in a project.
- List test cases
Get all test cases in a project.
- List test run results
Get all results for a project's test runs.
- Resolve defect
Marks a specific defect in a Qase project as resolved.
- Update defect
Update an existing defect.
- Update run
Update a specific test run.
- Update test case
Updates an existing test case in a Qase project. Only the fields you fill in are changed.
- Update test run result
Update a test run result.
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 Qase
HubSpot to QaseHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to QaseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to QaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ilert and Qase, 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 Qase when something happens in ilert?
Any of Qase's 27 actions, including Update defect, Update run, Update test case and Update test run result. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qase to ilert?
Qase has no triggers in the catalog today, so automations start in ilert. If you need the other direction, ask: your agent reads Qase's API documentation and adds it.
Do I have to build a connector for ilert or Qase?
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 Qase 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.