Integration
Connect Particle to Hellotracks
When something happens in Particle, your agent does the next thing in Hellotracks. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Particle and Hellotracks 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 Particle and Hellotracks
Triggers and actions 6 triggers ยท 20 actions
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
Action
Execute a logic functionRun a configured Particle Logic function and return its result.
Action
Get ledger instanceRetrieve the current data for a ledger instance (shared cloud/device key-value state).
Action
List devicesList all devices in your account or product fleet.
Action
Publish an eventPublish a custom event to the device cloud so other devices or integrations can subscribe to it.
Action
Set ledger instance dataUpdate the data stored in a ledger instance.
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).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.