--- title: "Connect Hellotracks and incident.io - APIANT.ai" description: "When \"Completed Job\" fires in Hellotracks, your agent runs \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/hellotracks-to-incident-io" --- # Connect Hellotracks and incident.io When **Completed Job** fires in [Hellotracks](https://apiant.ai/connections/hellotracks), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Add member** in Hellotracks. Describe the whole flow and it is built, tested on every scenario and kept running. Hellotracks **5** triggers Hellotracks **19** actions incident.io **1** trigger incident.io **10** 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 incident.io 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 and incident.io can do together ### From Hellotracks to incident.io - When **Completed Job** in Hellotracks then **Find Users On-Call** in incident.io - When **New Job** in Hellotracks then **Add follow-up** in incident.io ### From incident.io to Hellotracks - When **New Incident** in incident.io then **Add member** in Hellotracks - When **New Incident** in incident.io then **Add place** in Hellotracks 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 incident.io ## Triggers and actions 6 triggers · 29 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. - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. ## 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) - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) 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 incident.io - [ **HubSpot to incident.io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-incident-io) - [ **Google Sheets to incident.io** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-incident-io) - [ **Gmail to incident.io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-incident-io) - [ **Google Calendar to incident.io** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-incident-io) - [ **Google Drive to incident.io** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-incident-io) - [ **ActiveCampaign to incident.io** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-incident-io) Questions ## Hellotracks and incident.io, 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 incident.io when something happens in Hellotracks? Any of incident.io's 10 actions, including Create Incident, Add follow-up, Add incident update and Find Users On-Call. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from incident.io to Hellotracks? Yes. When something happens in incident.io, your agent can act in Hellotracks too. This page covers both directions: incident.io's triggers and Hellotracks's actions are listed here as well. ### ### Do I have to build a connector for Hellotracks or incident.io? 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 incident.io 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.