Detrack MCP integration for AI agents.
Connect AI agents to Detrack through 7 structured actions, including get job, create job, and delete job. Review authentication, inputs, workflows, and safet…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Detrack integration exposes
The Detrack Agent App exposes 7 provider-backed actions for productivity and location work. Its current contract lets an authorized agent retrieve one detrack job by d.o. number and date, create a delivery or collection job in detrack api v2, and delete one detrack job identified by d.o. number and date. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Detrack account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Detrack capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_jobREADRetrieve one Detrack job by D.O. number and date.
INPUTS: doNumber / date / type
create_jobWRITECreate a delivery or collection job in Detrack API V2.
INPUTS: type / doNumber / date / address / startDate
delete_jobHIGH IMPACTDelete one Detrack job identified by D.O. number and date.
INPUTS: doNumber / date / type
list_depotsREADList depots available in the connected Detrack account.
INPUTS: page / limit
list_jobsREADList and filter delivery or collection jobs from Detrack API V2.
INPUTS: page / limit / sort / type / date
search_jobsREADSearch Detrack jobs with structured operational and customer filters.
INPUTS: type / doNumber / doNumbers / dateFrom / dateTo
update_jobWRITEUpdate selected fields on one Detrack job identified by D.O. number and date.
INPUTS: doNumber / date / type / address / startDate
INPUT CONTRACTS
Know what the action needs before it runs.
get_job
doNumberREQUIRED- The D.O. number of the job.
dateREQUIRED- The job date in YYYY-MM-DD format.
typeOPTIONAL- The Detrack job type.
create_job
typeOPTIONAL- The Detrack job type.
doNumberREQUIRED- The D.O. number for the job. Detrack may allow automatic generation when configured, but this action requires an explicit stable identifier.
dateREQUIRED- The date when the job is performed in YYYY-MM-DD format.
addressOPTIONAL- The address where the job is performed.
startDateOPTIONAL- The date when the job starts in YYYY-MM-DD format.
delete_job
doNumberREQUIRED- The D.O. number of the job.
dateREQUIRED- The job date in YYYY-MM-DD format.
typeOPTIONAL- The Detrack job type.
list_depots
pageOPTIONAL- The one-based result page number.
limitOPTIONAL- The number of depots per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Job
Retrieve one Detrack job by D.O. number and date. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_jobControl Create Job
Create a delivery or collection job in Detrack API V2. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_jobVerify with List Depots
List depots available in the connected Detrack account. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_depotsSAFETY BOUNDARY
Operate Detrack with explicit limits
- Authorize Detrack with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_job` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Detrack rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Detrack task completed successfully.
CONNECTION MODEL
API key
Detrack API key sent with the X-API-KEY header. Generate or view it under Integrations > API Key: https://help.detrack.com/en/articles/6553302-how-to-generate-your-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Detrack.