---
title: "Connect Commerce Layer to Qase - APIANT.ai"
description: "When \"New Attachment\" fires in Commerce Layer, your agent runs \"Add project\" in Qase."
canonical: "https://apiant.ai/connect/commerce-layer-to-qase"
---

# Connect Commerce Layer to Qase

When **New Attachment** fires in [Commerce Layer](https://apiant.ai/connections/commerce-layer), your agent runs **Add project** in [Qase](https://apiant.ai/connections/qase). Describe the whole flow and it is built, tested on every scenario and kept running.

Commerce Layer **13** triggers Commerce Layer **28** actions Qase **27** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Commerce Layer and Qase to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Commerce Layer can start in Qase

- When **New Attachment** in Commerce Layer then **Add project** in Qase
- When **New Customer** in Commerce Layer 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 Commerce Layer and Qase

## Triggers and actions 13 triggers · 55 actions

- Trigger

**New Attachment**

Triggers when a new Attachment is created.

- Trigger

**New Customer**

Triggers when a new Customer is created.

- Trigger

**New Customer Address Event**

Triggers when a customer address is created.

- Trigger

**New Customer Password Reset Event**

Triggers when a customer password reset is requested.

- Trigger

**New Customer Subscription Event**

Triggers when a given customer_subscription event (one of create or destroy) is fired.

- Trigger

**New Price**

Triggers when a new Price is created.

- Trigger

**New Price Import**

Fires when a new price import is created in Commerce Layer.

- Trigger

**New Price List**

Triggers when a new Price List is created.

- Trigger

**New Shipping Category**

Triggers when a Shipping Category is created.

- Trigger

**New SKU**

Triggers when a new SKU is created.

- Trigger

**New SKU Import**

Triggers when a new SKU import is created.

- Trigger

**New Stock Item Import**

Triggers when a new Stock Item import is created.

- Trigger

**New Stock Transfer Event**

Triggers when a given stock transfer event (one of create, upocoming, picking, in_transit, complete, cancel is fired).

- Action

**Add Customer Address**

Adds an existing address to a customer's address book.

- Action

**Add Customer Password Reset**

Requests a password reset for a customer, returning the reset token to send them.

- Action

**Add Customer Subscription**

Subscribes a customer email to a list, identified by a reference such as a newsletter id.

- Action

**Add Stock Transfer**

Moves a quantity of a SKU from one stock location to another.

- Action

**Balance Change Gift Card**

Change balance of a gift card.

- Action

**Create Address**

Creates a postal address that can be attached to customers, orders and stock locations.

- Action

**Create Attachment**

Creates a new Attachment.

- Action

**Create Customer**

Creates a new Customer.

- Action

**Create Gift Card**

Creates a new Gift Card.

- Action

**Create Price Import**

Creates a new Price Import.

- Action

**Create Price List**

Creates a new Price List.

- Action

**Create SKU**

Creates a new SKU.

- Action

**Find Attachment**

Finds a Attachment by name.

- Action

**Find Customer**

Finds a customer by id or reference.

- Action

**Find Gift Card**

Finds a gift card by id or reference.

- Action

**Find Price**

Finds a price by price list.

- Action

**Find Price Import**

Finds a Price Import by status.

- Action

**Find Price List**

Finds a Price List by name.

- Action

**Find Shipping Category**

Finds an Shipping Category by name.

- Action

**Find SKU**

Finds an SKU by code.

- Action

**Find SKU Import**

Finds an SKU Import by status.

- Action

**Find Stock Item Import**

Finds a Stock Item Import by status.

- Action

**Get Address**

Retrieves one address by id.

- Action

**Get Customer Address**

Retrieves one customer address link by id.

- Action

**Get Customer Password Reset**

Retrieves a customer password reset by id, returning customer_email, reset_password_token and reset_password_at.

- Action

**Get Customer Subscription**

Retrieves one customer subscription by id.

- Action

**Get Stock Transfer**

Retrieves one stock transfer by id.

- Action

**Update Customer Reference**

Update customer data setting external identifier.

- Action

**Add defect**

Adds a new defect to a Qase project.

- Action

**Add milestone**

Creates a milestone in a Qase project.

- Action

**Add project**

Create a new project.

- Action

**Add run**

Create a new test run in a project.

- Action

**Add test case**

Create a new test case in a project.

- Action

**Add test run result**

Create a result for a test run.

- Action

**Complete run**

Mark a specific test run as completed.

- Action

**Delete project**

Delete a project by code.

- Action

**Delete run**

Delete a test run by id.

- Action

**Delete test case**

Delete a test case by id.

- Action

**Find entities by QQL**

Searches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.

- Action

**Get defect**

Get a specific defect by id.

- Action

**Get project**

Get a project by its code.

- Action

**Get run**

Retrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.

- Action

**Get test case**

Get a specific test case by id.

- Action

**Get test run result**

Get a test run result by hash code.

- Action

**List defects**

Returns all defects in a Qase project, optionally filtered by status.

- Action

**List milestones**

Get all milestones in a project.

- Action

**List projects**

Lists every project available to the connected Qase account.

- Action

**List runs**

Get all test runs in a project.

- Action

**List test cases**

Get all test cases in a project.

- Action

**List test run results**

Get all results for a project's test runs.

- Action

**Resolve defect**

Marks a specific defect in a Qase project as resolved.

- Action

**Update defect**

Update an existing defect.

- Action

**Update run**

Update a specific test run.

- Action

**Update test case**

Updates an existing test case in a Qase project. Only the fields you fill in are changed.

- Action

**Update test run result**

Update a test run result.

## Each app on its own

- [ **Commerce Layer** Commerce Layer is a lightning fast, super flexible and ultra secure REST API that lets you build...](https://apiant.ai/connections/commerce-layer)
- [ **Qase** Test management platform for organizing test cases, tracking manual and automated test runs, and reporting...](https://apiant.ai/connections/qase)

Reviews

## What our customers say

## More from Commerce Layer

- [ **Commerce Layer to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/commerce-layer-to-hubspot)
- [ **Commerce Layer to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/commerce-layer-to-salesforce)
- [ **Commerce Layer to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/commerce-layer-to-slack)
- [ **Commerce Layer to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/commerce-layer-to-google-sheets)
- [ **Commerce Layer to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/commerce-layer-to-gmail)
- [ **Commerce Layer to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/commerce-layer-to-google-calendar)

## More into Qase

- [ **Salesforce to Qase** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-qase)
- [ **HubSpot to Qase** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-qase)
- [ **Slack to Qase** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-qase)
- [ **Google Sheets to Qase** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-qase)
- [ **Gmail to Qase** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-qase)
- [ **Google Calendar to Qase** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-qase)

Questions

## Commerce Layer and Qase, answered

###

### What can start an automation from Commerce Layer?

Any of Commerce Layer's 13 triggers in the catalog, including New Attachment, New Customer, New Customer Address Event and New Customer Password Reset Event. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Qase when something happens in Commerce Layer?

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 Commerce Layer?

Qase has no triggers in the catalog today, so automations start in Commerce Layer. 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 Commerce Layer 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 Commerce Layer 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.
