Detrack
LogisticsConnect AI agents to Detrack, a last-mile delivery management platform. Agents create and update delivery jobs, capture proof of delivery, and plan optimized driver routes so dispatch teams keep every delivery on schedule.
What This Integration Enables
Detrack is built for delivery operations that get argued about after the van has gone. Most last-mile tools treat the job record as the product. Detrack treats the evidence as the product: the signature, the photo, the timestamp, and the driver note captured at the door, exported as a PDF or TIFF that a human can look at. That is a different thing to automate. FlowRunner agents create and update jobs from your store or ERP, search across them by date, status, and D.O. number, and plan optimized driver routes from a depot. The operation that changes how the day actually runs is Get Proof of Delivery. It lands the captured document in FlowRunner file storage and hands back a URL you can attach to an order, an invoice, or a support ticket.
Detrack identifies jobs by their D.O. number plus a date, so an agent working across several days has to carry the date with it rather than assume the number is unique. That detail matters because reattempts create a second job for the same D.O. number on a different date, and a workflow that ignores it will read yesterday's failure as today's outcome. Agents that keep the date in hand can tell the difference between a delivery that failed once and one that has now failed twice, which is the fact a dispatcher actually needs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Orders into jobs, tracking back to the customer
An order clears in the storefront. The agent calls Create Job with the recipient, the time window, and the items, then sends the customer their tracking reference through Gmail or Slack depending on whether the recipient is a consumer or an internal team. Through the day the agent polls Search Jobs by date and status, and when a job moves to a completed state it calls Get Proof of Delivery and files the document against the order record. Nobody exports anything by hand, and the proof is attached before the finance team invoices for the delivery.
Failed deliveries triaged instead of blanket rebooked
The agent runs Search Jobs each evening filtered to failed statuses. Rather than calling Reattempt Job on all of them, it retrieves the proof image and driver note for each and sorts them by reason. A closed gate is a candidate for a same-address retry. An address that does not exist is a data problem. A refusal is a commercial problem. The routine cases are queued for reattempt automatically. The rest go to a person, because sending the same van to the same door tomorrow costs another stop and, for a refusal, is guaranteed to fail again.
Morning route build from the day's open jobs
Before the shift, the agent calls List Depots to resolve the starting point, uses List Jobs to gather the internal job IDs scheduled for the day, and calls Plan Route to produce an optimized sequence. Plan Route expects internal job IDs rather than D.O. numbers, so the agent resolves them from the list rather than reusing the customer-facing reference. It then posts the stop list to the driver's channel and logs the plan alongside the prior day's actual completions in Google Sheets, so route quality can be compared against what really happened.
Human-in-Loop Highlight
The gate sits on Reattempt Job. A failed delivery in Detrack carries a status and, usually, a photo the driver took at the door plus a short note. An agent can fetch both. It cannot look at a photo of a dark porch and know whether the customer was out, whether the business had already closed for the day, or whether someone stood there and refused the parcel. Those three cases have three different correct answers, and only one of them is a reattempt. So the agent gathers the evidence and stops: it posts the failed job, the proof image from Get Proof of Delivery, the driver note, and how many times this D.O. number has already been attempted, and asks the dispatcher a direct question. "Job 88431, second failed attempt, driver note reads refused at door. Reattempt tomorrow, return to sender, or hold for a customer call?" The dispatcher answers in one tap and the agent executes it. This is human-in-the-loop placed where the information genuinely runs out, not where an approval box was easy to add.
Agent Capabilities
12 actionsJobs
7- Create Job Creates a delivery or collection job from an upstream order. Used to push orders out of a store, ERP, or order management system into the dispatch board without manual entry.
- List Jobs Returns jobs for a given date. Used to gather the day's work before route planning or to feed a status dashboard.
- Get Job Retrieves a single job by D.O. number and date. Used when a workflow already knows which delivery it cares about, such as answering a customer status request.
- Update Job Modifies an existing job's details. Used to push address corrections, time window changes, or item updates that arrived after the job was created.
- Delete Job Removes a job. Used to clear a job that was created in error before a driver is dispatched against it.
- Reattempt Job Reschedules a failed delivery as a new attempt. Used after a failure has been reviewed and a retry is the right answer.
- Search Jobs Runs a structured search across jobs by date range, status, and D.O. number. Used for the recurring sweeps that drive exception handling and reporting.
Proof of Delivery
1- Get Proof of Delivery Exports a job's proof of delivery or shipping label as a PDF or TIFF, stores it in FlowRunner file storage, and returns a downloadable URL. Used to attach captured signatures and photos to the order, the invoice, or the support ticket that will reference them later.
Depots and Routes
4- List Depots Returns the configured depots. Used to resolve the correct starting point before planning a route.
- Create Depot Adds a new depot. Used when a new hub or satellite location comes online and routes need to originate there.
- List Routes Returns planned routes. Used to review or report on what was scheduled for a given day.
- Plan Route Builds an optimized route from a set of internal job IDs and a starting depot. Used each morning to turn the day's open jobs into a drivable sequence.
Frequently Asked Questions
What can FlowRunner do with Detrack?
FlowRunner agents can run Create Job, List Jobs, and Get Job in Detrack, plus 9 more actions.
Does connecting Detrack to FlowRunner require OAuth?
No. Detrack connects to FlowRunner with an API key, no OAuth flow required.
Can Detrack trigger a FlowRunner workflow automatically?
Detrack doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Detrack
$100 in credits. No card required. Connect in minutes.