Integration
Connect Enchant to Qase
When New Customer fires in Enchant, 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 Enchant 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Enchant can start in Qase
When New Customer in Enchant
then Add project in Qase
When New or Updated Ticket in Enchant
then Add defect 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 Enchant and Qase
Triggers and actions 3 triggers · 44 actions
Trigger
New CustomerTriggers when a new customer is added to the help desk.
Trigger
New or Updated TicketTriggers when a ticket is created or changes (new message, state, assignee, labels).
Trigger
New Ticket CreatedTriggers when a new ticket is created, optionally only in the inboxes you choose.
Action
Add Labels to TicketAdds one or more labels to a ticket, keeping its existing labels.
Action
Create AttachmentUploads a file as an attachment so its id can be added to a note or reply.
Action
Create ContactAdds an email address, phone number or Twitter handle to a customer.
Action
Create CustomerCreates a customer in your Enchant help desk, optionally with an email address.
Action
Create TicketCreates an email ticket for a customer, matched or created by email, with the customer's first message.
Action
Delete ContactDeletes one contact (email, phone or Twitter handle) from a customer.
Action
Find Customer by EmailFinds the customer with a given email address.
Action
Get AttachmentReturns an attachment's file name, MIME type and size.
Action
Get CustomerReturns one customer with their name, summary and contacts.
Action
Get TicketReturns one ticket by its id.
Action
List customersReturns customers from your Enchant help desk, optionally filtered by contact or creation date.
Action
List messagesReturns all replies and notes on a ticket, oldest to newest as Enchant lists them.
Action
List TicketsReturns up to 100 tickets, newest first, optionally filtered by state, inbox or assigned user.
Action
List UsersReturns the help desk's users (agents) with their names and email addresses.
Action
Remove Labels from TicketRemoves one or more labels from a ticket.
Action
Update CustomerUpdates a customer's name or summary. Only the fields you fill in change.
Action
Update TicketUpdates a ticket's state, assigned user, inbox or subject. Only the fields you fill in change.
Action
Add defectAdds a new defect to a Qase project.
Action
Add milestoneCreates a milestone in a Qase project.
Action
Add projectCreate a new project.
Action
Add runCreate a new test run in a project.
Action
Add test caseCreate a new test case in a project.
Action
Add test run resultCreate a result for a test run.
Action
Complete runMark a specific test run as completed.
Action
Delete projectDelete a project by code.
Action
Delete runDelete a test run by id.
Action
Delete test caseDelete a test case by id.
Action
Find entities by QQLSearches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.
Action
Get defectGet a specific defect by id.
Action
Get projectGet a project by its code.
Action
Get runRetrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.
Action
Get test caseGet a specific test case by id.
Action
Get test run resultGet a test run result by hash code.
Action
List defectsReturns all defects in a Qase project, optionally filtered by status.
Action
List milestonesGet all milestones in a project.
Action
List projectsLists every project available to the connected Qase account.
Action
List runsGet all test runs in a project.
Action
List test casesGet all test cases in a project.
Action
List test run resultsGet all results for a project's test runs.
Action
Resolve defectMarks a specific defect in a Qase project as resolved.
Action
Update defectUpdate an existing defect.
Action
Update runUpdate a specific test run.
Action
Update test caseUpdates an existing test case in a Qase project. Only the fields you fill in are changed.
Action
Update test run resultUpdate 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 Enchant
Enchant to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Enchant to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Enchant to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Enchant to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Enchant to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Enchant to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Qase
Salesforce to QaseSalesforce is a leading enterprise customer relationship management (CRM) platform.
HubSpot to QaseHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to QaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
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
Enchant and Qase, answered
What can start an automation from Enchant?
Any of Enchant's 3 triggers in the catalog, including New Customer, New or Updated Ticket and New Ticket Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qase when something happens in Enchant?
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 Enchant?
Qase has no triggers in the catalog today, so automations start in Enchant. 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 Enchant 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 Enchant 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.