---
title: "Connect Pipefile to Qase - APIANT.ai"
description: "When \"File Request Created\" fires in Pipefile, your agent runs \"Add project\" in Qase."
canonical: "https://apiant.ai/connect/pipefile-to-qase"
---

# Connect Pipefile to Qase

When **File Request Created** fires in [Pipefile](https://apiant.ai/connections/pipefile), 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.

Pipefile **1** trigger Pipefile **10** 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 Pipefile 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 Pipefile can start in Qase

- When **File Request Created** in Pipefile then **Add project** in Qase
- When **File Request Created** in Pipefile 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 Pipefile and Qase

## Triggers and actions 1 trigger · 37 actions

- Trigger

**File Request Created**

Triggers when a file request is created.

- Action

**Add File Request From Template**

Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.

- Action

**Create Contact**

Add to contacts

- Action

**Delete Contact**

Delete a contact by id. Returns 204 No Content on success.

- Action

**Get Contact**

Retrieve one contact by id.

- Action

**Get File Request**

Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.

- Action

**List Contacts**

Retrieve a paginated list of contacts, filterable by name/email/phone partial match.

- Action

**List File Request Templates**

Retrieve the list of file request templates available for creating new file requests, with optional name search.

- Action

**Search File Requests**

Finds all file requests matching this search query (contact name, email, tags, etc).

- Action

**Send Request**

Create and send a new request

- Action

**Update Contact**

Update name/email/phone of an existing contact by id.

- 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

- [ **Pipefile** Pipefile streamlines the collection of personal, financial, and otherwise sensitive documents to keep your...](https://apiant.ai/connections/pipefile)
- [ **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 Pipefile

- [ **Pipefile to Channels** Channels is a data-driven phone system that lets you make and take calls directly in the browser.](https://apiant.ai/connect/pipefile-to-channels)
- [ **Pipefile to Cleanvoice** API that removes filler words, silences, background noise, and mouth sounds from audio and video recordings.](https://apiant.ai/connect/pipefile-to-cleanvoice)
- [ **Pipefile to DeBounce** DeBounce is an email verification service that allows you to validate your email addresses and remove...](https://apiant.ai/connect/pipefile-to-debounce)
- [ **Pipefile to Digimon Information** The Digimon API is a public reference catalogue of creatures from the Digimon franchise.](https://apiant.ai/connect/pipefile-to-digimon-information)
- [ **Pipefile to Disify** Disify checks email addresses for disposable and temporary providers.](https://apiant.ai/connect/pipefile-to-disify)
- [ **Pipefile to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pipefile-to-salesforce)

## 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

## Pipefile and Qase, answered

###

### What can start an automation from Pipefile?

Any of Pipefile's 1 trigger in the catalog, including File Request 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 Pipefile?

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 Pipefile?

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