Detrack is a delivery management software that offers real-time vehicle tracking, electronic proof of delivery, and automated customer notifications.
Detrack is a delivery management software that offers real-time vehicle tracking, electronic proof of delivery, and automated customer notifications. On Nagent, Detrack is exposed as a fully-configurable internet of things integration that any agent can call — 19 actions, and API key authentication. No code is required to wire Detrack into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Detrack to automate the kinds of tasks internet of things teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Detrack into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Detrack, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DETRACK_ADD_COLLECTIONAdd a new collection job in Detrack. A collection is a pickup job where items are collected from a location. The Delivery Order (do) number must be unique per date. Include the country name in the address for better geocoding.
Input parameters
Delivery Order number - must be unique per date. This serves as the tracking identifier.
Date of the collection job in YYYY-MM-DD format
Zone or region classification for the collection
List of items to collect. Each item requires sku, desc, and qty.
Phone number of the collection contact
Full address of the collection location. Include country name for better geocoding accuracy.
Vehicle name or identifier to assign this collection to
Webhook URL to receive collection status updates
Name of the sender or company to collect from
Special instructions for the driver
Email address to send collection status notifications
Time window for collection (e.g., '09:00 AM - 12:00 PM' or '14:00')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_CREATE_BULK_DEPOTSTool to create multiple depot locations in one request. Use when you need to create several depots at once. Each depot requires at least a name and an address that can be geocoded. Include country name in addresses for accurate geocoding.
Input parameters
List of depot data objects to create. Each depot requires at least a name and address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_CREATE_DEPOTCreate a new depot in Detrack. A depot serves as a starting/ending point for delivery routes. Requires at least a name and an address that can be geocoded. The address should be complete and include the country name for accurate geocoding.
Input parameters
Depot data containing name, address, and optional fields.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_DELETE_ALL_COLLECTIONSTool to delete all collections in the account. Use when you need to purge every collection for a specific date after confirmation.
Input parameters
The collection date in YYYY-MM-DD format, e.g., '2014-02-28'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_DELETE_ALL_DELIVERIESTool to delete all deliveries for a specific date. Use when you need to purge deliveries in bulk before scheduling new ones.
Input parameters
The delivery date to delete all deliveries for. Format: YYYY-MM-DD.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_DELETE_DELIVERYTool to delete one or more deliveries by date and D.O. number. Use after confirming delivery entries to avoid accidental data loss (max 100 items per call).
Input parameters
List of deliveries to delete; must contain between 1 and 100 items
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_DELETE_DEPOTS_BULKTool to delete multiple depots in a single request. Use when you need to remove depots that are no longer needed.
Input parameters
List of depots to delete; each depot identified by its name
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_DELETE_JOB_BY_QUERYTool to delete a job by DO number using query parameters. Use when you need to delete a specific job by its DO number. Returns success status indicating whether the job was found and deleted.
Input parameters
Optional date filter in YYYY-MM-DD format to narrow down the job lookup.
Job type enumeration for delivery or collection jobs.
Delivery Order (DO) number to identify the job to delete. Must be unique.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_EDIT_DELIVERYEdit one or more existing deliveries by date and D.O. number. Use this tool to update delivery details such as address, recipient, phone, instructions, or vehicle assignment. The delivery must already exist in Detrack (identified by date + D.O. number combination). Limitations: - Maximum 100 deliveries per request - Date and D.O. must match an existing delivery
Input parameters
List of delivery records to update (1 to 100 items)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_GET_JOB_BY_DO_AND_DATETool to retrieve a specific job by its DO (Delivery Order) number and date. Use when you need to fetch detailed information about a specific delivery or collection job. Returns comprehensive job details including status, tracking, items, and proof of delivery information.
Input parameters
Date of the job in YYYY-MM-DD format. This must match the scheduled date of the job.
Job type enum for filtering jobs.
Delivery Order (DO) number to retrieve. This is the unique identifier for the job on the specified date.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_GET_JOB_BY_QUERYTool to retrieve a single job by DO number using query parameters. Use when you need to fetch detailed information about a specific delivery or collection job.
Input parameters
Date filter in YYYY-MM-DD format. Use to narrow search if DO number is not unique.
Job type enum for Detrack.
Delivery Order (DO) number to retrieve the job.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_LIST_DEPOTSTool to list all depot locations with pagination. Use when you need to retrieve depot information including addresses and coordinates. Supports pagination to handle large numbers of depots.
Input parameters
Page number for pagination. Defaults to 1.
Number of records per page. Defaults to 20.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_LIST_JOBS_V2Tool to list jobs with pagination and filtering using Detrack API v2. Use when you need to retrieve jobs with filters by date, type, assign_to, status, DO number, or search query. Supports sorting and pagination for efficient data retrieval.
Input parameters
Filter jobs by date in YYYY-MM-DD format.
Page number for pagination. Defaults to 1.
Attribute to be sorted. Add minus (-) prefix for descending order (e.g., '-date' for descending date, 'date' for ascending).
Enum for job type filter.
Number of records per page. Maximum 100. Defaults to 20.
Search query to filter jobs by DO number, address, delivery to, notify email, assign to, tracking number, or zone.
Filter jobs by status. Use comma to separate multiple statuses (e.g., 'Completed,In Progress').
Filter jobs by the vehicle/driver assigned to the job.
Filter jobs by Delivery Order (DO) number.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_SEARCHTool to search for deliveries, collections, or vehicles. Use after defining search criteria to retrieve matching jobs.
Input parameters
Query object containing search criteria. Supported keys: 'date' (YYYY-MM-DD format), 'do' (delivery order number), 'type' ('delivery' or 'collection'), 'status' (e.g., 'In Progress', 'Completed'), 'tracking_status' (e.g., 'info_recv', 'on_vehicle'), 'address', 'name', 'zone'.
Page number for pagination (1-based). Defaults to 1.
Number of jobs to return per page.
Sorting order: ASC (ascending) or DESC (descending).
Number of jobs to skip (for pagination).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_SEARCH_JOBSSearch jobs with advanced filters including date range, DO number, statuses, groups, vehicles, zones, and more. Use this to find specific jobs across multiple criteria using the v2 search API.
Input parameters
Page number for pagination. Defaults to 1.
Filter jobs by type: 'delivery' or 'collection'.
Number of records per page. Maximum 100. Defaults to 20.
General search query string to search across job fields like DO number, address, customer name, etc.
Filter jobs by status. Common values include 'completed', 'failed', 'in_progress', 'pending'.
End date for date range filter in YYYY-MM-DD format. Returns jobs scheduled up to this date.
Filter jobs by assigned driver name or ID.
Start date for date range filter in YYYY-MM-DD format. Returns jobs scheduled from this date onwards.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_UPDATE_DEPOTS_BULKUpdate multiple depot locations in a single request. Use this to modify depot details such as address, contact information, or coordinates. Each depot is identified by its name or ID. This is more efficient than updating depots individually when you need to update multiple depots at once.
Input parameters
List of depot records to update. Each depot must have at least a name.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_VIEW_ALL_COLLECTIONSView all collection jobs scheduled for a specific date in Detrack. Returns collection details including delivery order number, pickup address, status, tracking link, and items. Use this to retrieve all collections for a particular day by providing a date in YYYY-MM-DD format.
Input parameters
The collection date to view all collections for. Format: YYYY-MM-DD (e.g., '2026-01-27').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_VIEW_ALL_DELIVERIESTool to view all deliveries for a specific date. Use when you need to retrieve all delivery jobs on a given date.
Input parameters
The delivery date to view all deliveries for. Format: YYYY-MM-DD.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DETRACK_VIEW_ALL_VEHICLESRetrieve all vehicles registered in your Detrack account. Returns complete fleet information including real-time location, speed, connection status, and vehicle details. Use this to get an overview of your entire fleet or check which vehicles are currently active.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 78 agents privately built on Nagent that already use Detrack.
Build on Nagent
Connect Detrack to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Detrack, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Detrack is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Detrack is connected, you configure its 19 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Detrack steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Detrack event fires, the agent kicks off automatically.
Every Detrack action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Detrack ships with 19 pre-built internet of things actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Detrack together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Detrack-based workflows tailored to your business.