Integration
Connect Hellotracks and Trengo
When something happens in Hellotracks or Trengo, your agent does the next thing in the other. 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 Trengo 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 and Trengo can do together
From Hellotracks to Trengo
When Completed Job in Hellotracks
then Add internal note to ticket in Trengo
When New Job in Hellotracks
then Add ticket in Trengo
From Trengo to Hellotracks
When New Internal Note in Trengo
then Add member in Hellotracks
When New Outbound Message in Trengo
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 Trengo
Triggers and actions 8 triggers · 34 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.
Trigger
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
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 Trengo
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TrengoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TrengoGoogle Sheets
Gmail to TrengoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hellotracks and Trengo, 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 Trengo when something happens in Hellotracks?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Hellotracks?
Yes. When something happens in Trengo, your agent can act in Hellotracks too. This page covers both directions: Trengo's triggers and Hellotracks's actions are listed here as well.
Do I have to build a connector for Hellotracks or Trengo?
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.