Integration
Connect Hellotracks to PractiTest
When something happens in Hellotracks, your agent does the next thing in PractiTest. Describe it 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 Hellotracks and PractiTest to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Hellotracks can start in PractiTest
When Completed Job in Hellotracks
then Add Instance in PractiTest
When New Job in Hellotracks
then Add Issue in PractiTest
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 PractiTest
Triggers and actions 5 triggers · 41 actions
Trigger
Alert triggeredFires 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 JobTriggers when a job reaches a completed state.
Trigger
Member clocked in or outFires 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 JobTriggers when a job is created.
Trigger
Updated JobTriggers when a job is created, assigned, completed, archived, or otherwise updated.
Action
Add memberCreate a new team member (worker) account.
Action
Add placeCreate a new saved place/geofence.
Action
Archive JobArchives a job by ID.
Action
Auto-assign jobsAutomatically assign a set of unassigned jobs to available members.
Action
Create JobCreates or updates a job. If External ID matches an existing job, the existing job is updated.
Action
Delete JobDeletes a job by ID.
Action
Delete memberDelete a team member account.
Action
Distribute jobAssign/distribute one or more jobs to members for dispatch.
Action
Find JobFinds a job by External ID.
Action
Find MemberFinds a member by exact email, username, name, or UID.
Action
Generate reportGenerate a report (e.g. timesheet/activity) for a date range.
Action
Get companyGet the authenticated company account's profile/settings.
Action
List placesGet the company's saved places/geofences.
Action
Locate memberGet a member's current/last known GPS location.
Action
Optimize routeCompute an optimized route ordering for a member's assigned jobs.
Action
Restore jobRestore a previously archived job.
Action
Update JobUpdates a job by ID.
Action
Update memberEdit an existing team member's fields.
Action
Update placeEdit an existing saved place/geofence.
Action
Add InstanceAdds a test to a test set in a PractiTest project as a new instance.
Action
Add IssueCreates an issue in a PractiTest project.
Action
Add TestCreate a new test case in a project.
Action
Create a RunUploads a new run result for a test instance in a PractiTest project — typically automated test results from CI, or a manual run with step results.
Action
Create RequirementCreates a new requirement.
Action
Delete IssueDeletes a specific issue from a PractiTest project.
Action
Delete RequirementDeletes a specific requirement from a PractiTest project.
Action
Delete TestDeletes a specific test from a PractiTest project.
Action
Get IssueRetrieves a single issue from a PractiTest project, including its attributes and custom field values.
Action
Get RequirementRetrieves a single requirement from a PractiTest project by its system id.
Action
Get RunRetrieve a single test run by id.
Action
Get TestRetrieve a single test by id.
Action
List InstancesLists the test instances in a PractiTest project, optionally filtered by test set, test, name or display id.
Action
List IssuesLists the issues in a PractiTest project, optionally narrowed by filter, display ids, title or PTQL query.
Action
List ProjectsLists the projects in the PractiTest account. With a personal API token, only the projects that user can access are returned.
Action
List RequirementsReturns all requirements in a PractiTest project, optionally narrowed by filter, display ids, name or PTQL query.
Action
List RunsList all test runs in a project.
Action
List TestsList all tests in a project.
Action
List UsersLists the users in the PractiTest account, optionally filtered by email address or to active users only.
Action
Update IssueUpdates an existing issue in a PractiTest project. Only the fields you fill in are changed.
Action
Update RequirementUpdate a requirement's fields.
Action
Update TestUpdates a specific test in a PractiTest project. Only the fields you fill in are changed.
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 Hellotracks
Hellotracks to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Hellotracks to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Hellotracks to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Hellotracks to MailchimpMailchimp marketing automation and email platform.
Hellotracks to StripeStripe is a payment processing platform for online businesses.
Hellotracks to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into PractiTest
HubSpot to PractiTestHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PractiTestSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PractiTestSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PractiTestGoogle Sheets
Gmail to PractiTestGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PractiTestGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hellotracks and PractiTest, 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 PractiTest when something happens in Hellotracks?
Any of PractiTest's 22 actions, including Create a Run, Create Requirement, Update Issue and Update Requirement. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PractiTest to Hellotracks?
PractiTest has no triggers in the catalog today, so automations start in Hellotracks. If you need the other direction, ask: your agent reads PractiTest's API documentation and adds it.
Do I have to build a connector for Hellotracks or PractiTest?
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.
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.