---
title: "Connect Hellotracks to Qase - APIANT.ai"
description: "When \"Completed Job\" fires in Hellotracks, your agent runs \"Add project\" in Qase."
canonical: "https://apiant.ai/connect/hellotracks-to-qase"
---

# Connect Hellotracks to Qase

When **Completed Job** fires in [Hellotracks](https://apiant.ai/connections/hellotracks), 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.

Hellotracks **5** triggers Hellotracks **19** 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 Hellotracks 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 Hellotracks can start in Qase

- When **Completed Job** in Hellotracks then **Add project** in Qase
- When **New Job** in Hellotracks 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 Hellotracks and Qase

## Triggers and actions 5 triggers · 46 actions

- Trigger

**Alert triggered**

Fires when a configured alert (late arrival, idle, zone entry/exit, low battery, etc.) triggers. Webhook key alert_triggered via /v1/webhooks or /api/setwebhooks (Hellotracks API).

- Trigger

**Completed Job**

Triggers when a job reaches a completed state.

- Trigger

**Member clocked in or out**

Fires when a worker turns location tracking on (clock-in) or off (clock-out) from the mobile app. Webhook key clock_in_out via /v1/webhooks or /api/setwebhooks (Hellotracks API).

- Trigger

**New Job**

Triggers when a job is created.

- Trigger

**Updated Job**

Triggers when a job is created, assigned, completed, archived, or otherwise updated.

- Action

**Add member**

Create a new team member (worker) account.

- Action

**Add place**

Create a new saved place/geofence.

- Action

**Archive Job**

Archives a job by ID.

- Action

**Auto-assign jobs**

Automatically assign a set of unassigned jobs to available members.

- Action

**Create Job**

Creates or updates a job. If External ID matches an existing job, the existing job is updated.

- Action

**Delete Job**

Deletes a job by ID.

- Action

**Delete member**

Delete a team member account.

- Action

**Distribute job**

Assign/distribute one or more jobs to members for dispatch.

- Action

**Find Job**

Finds a job by External ID.

- Action

**Find Member**

Finds a member by exact email, username, name, or UID.

- Action

**Generate report**

Generate a report (e.g. timesheet/activity) for a date range.

- Action

**Get company**

Get the authenticated company account's profile/settings.

- Action

**List places**

Get the company's saved places/geofences.

- Action

**Locate member**

Get a member's current/last known GPS location.

- Action

**Optimize route**

Compute an optimized route ordering for a member's assigned jobs.

- Action

**Restore job**

Restore a previously archived job.

- Action

**Update Job**

Updates a job by ID.

- Action

**Update member**

Edit an existing team member's fields.

- Action

**Update place**

Edit an existing saved place/geofence.

- 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

- [ **Hellotracks** Hellotracks is a field service platform for dispatching jobs, tracking mobile teams, and managing job status.](https://apiant.ai/connections/hellotracks)
- [ **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 Hellotracks

- [ **Hellotracks to Chartimagegenerator** Edge-rendered chart image API that converts Chart.js configurations into cached PNG/SVG images.](https://apiant.ai/connect/hellotracks-to-chartimagegenerator)
- [ **Hellotracks to Sendinblue** Email and SMS marketing platform with CRM and marketing automation, now rebranded as Brevo.](https://apiant.ai/connect/hellotracks-to-sendinblue)
- [ **Hellotracks to User.com** UserEngage is a marketing automation system that connects all data about your customers with all the...](https://apiant.ai/connect/hellotracks-to-user-com)
- [ **Hellotracks to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hellotracks-to-hubspot)
- [ **Hellotracks to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/hellotracks-to-salesforce)
- [ **Hellotracks to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/hellotracks-to-slack)

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

## Hellotracks and Qase, answered

###

### What can start an automation from Hellotracks?

Any of Hellotracks's 5 triggers in the catalog, including Completed Job, New Job, Updated Job and Alert triggered. Describe the moment in plain language and your agent picks the right one.

###

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

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

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