Integration
Connect Hellotracks to Wachete
When something happens in Hellotracks, your agent does the next thing in Wachete. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Hellotracks and Wachete to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Hellotracks and Wachete
Triggers and actions 7 triggers · 22 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. POST /api/createaccount (Hellotracks API).
Action
Add placeCreate a new saved place/geofence. POST /api/createplace (Hellotracks API).
Action
Archive JobArchives a job by ID.
Action
Auto-assign jobsAutomatically assign a set of unassigned jobs to available members. POST /api/autoassign (Hellotracks API).
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. POST /api/deleteaccount (Hellotracks API).
Action
Distribute jobAssign/distribute one or more jobs to members for dispatch. POST /api/distributejobs (Hellotracks API).
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. POST /api/createreport (Hellotracks API); RPC-style call returning report data.
Action
Optimize routeCompute an optimized route ordering for a member's assigned jobs. POST /api/routeoptimization (Hellotracks API); RPC-style call returning route data.
Action
Restore jobRestore a previously archived job. POST /api/restorejobs (Hellotracks API).
Action
Update JobUpdates a job by ID.
Action
Update memberEdit an existing team member's fields. POST /api/editaccount (Hellotracks API).
Action
Update placeEdit an existing saved place/geofence. POST /api/editplace (Hellotracks API).
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.