That is the scheduled read catching it, which means the alert isn't reaching TrackFlo. Check that the alert is active, that its URL is exactly the hostname plus path above, and that the Authorization header is Bearer, a single space, then the token. A 401 response means the token doesn't match; ask us to confirm it.
McLeod PowerBroker Integration Guide
Updated last week
TrackFlo connects to your McLeod PowerBroker instance through its web services API, the same one your instance documents at https://<your-mcleod-host>/ws/docs/. Movements are read on a schedule; if you set up RapidAlerts, McLeod also pushes changes to TrackFlo the moment they happen, so the board updates in seconds instead of minutes. TrackFlo writes your team's tracking work back to the same movement in McLeod.
What TrackFlo reads
Active movements and their orders, stops, carrier, driver and equipment, every 10 to 20 minutes depending on your instance. A full resync runs four times a day as a backstop.
Recently completed movements, at least hourly, so delivered and voided loads leave the board.
Call-in history, so check calls made in McLeod appear on the TrackFlo timeline.
Movement and brokerage statuses, mapped to TrackFlo's shared status vocabulary.
Carrier contacts, every four hours.
Proof of delivery filed in McLeod Imaging, every 30 minutes, for delivered orders that don't have a POD in TrackFlo yet.
What TrackFlo writes
Call-ins with status, city and state, remarks and an ETA. Remarks end in
(via TrackFlo), so both systems can tell them apart from call-ins your team enters in McLeod.Stop arrivals and departures.
Driver, truck and trailer on the movement.
Proof of delivery as an imaged document, or by email to your team if you'd rather PODs not be filed in McLeod. We set this up with you during onboarding.
What your McLeod admin sets up
1. An API user
Create a McLeod user for TrackFlo and share its credentials with us. McLeod supports HTTP Basic and its own Token scheme. Which one your instance accepts varies by version and configuration, so we confirm it against your instance during onboarding rather than assume. A token can be created under Sys Admin → Smartphone Mobile Service, or minted from a Basic login with POST /users/login.
The user needs access to the movement, order, stop, call-in, carrier dispatch, imaging, payee and customer services. Your instance's /ws/docs/ page has a role filter that shows which services a user type can call.
2. Network access
If your instance sits behind a firewall, allow TrackFlo to reach its web services port. TrackFlo connects from a fixed IP address, which we give you during onboarding for your allowlist.
3. RapidAlerts (optional, recommended)
RapidAlerts are McLeod's outbound notifications: when a record changes, McLeod posts it to a URL. Without them TrackFlo still stays current through the scheduled reads above, but a change can take up to 20 minutes to reach the board. With them, it arrives in seconds.
Every URL starts with your tenant's webhook hostname, which we send you along with a bearer token:
https://<tenant>-integration-webhooks.trackflo.techStart with these four
These are the most time-sensitive changes on a load: the ones your trackers and customers notice when they're late. Set them up first.
Alert | Send it to | Why it matters |
|---|---|---|
Stop arrival |
| Marks the truck at pickup or delivery, so the load moves on the board and arrival exceptions clear |
Stop departure |
| Marks the truck loaded or empty and rolling to the next stop |
Movement status change |
| Movement and brokerage status, including voids, so a cancelled or delivered load leaves the board |
Call-in |
| Check calls entered in McLeod, with location, ETA and remarks |
Arrival and departure are both stop changes, so both go to /stop_update. One stop alert that fires on any stop change covers both, and also keeps appointments and added or deleted stops current.
Then, if you want everything in seconds
Alert | Send it to | What it keeps current |
|---|---|---|
Movement, carrier change |
| Carrier booked, replaced or removed, plus driver and equipment |
Movement, any other change |
| Everything else on the movement |
Every alert must:
Be an HTTP
POSTwith a JSON body.Send the header
Authorization: Bearer <token>, using the exact token we issue for your tenant. Any other value is rejected with401.Use McLeod's standard RapidAlert JSON. Stop and call-in alerts should carry the full record. A movement alert can be McLeod's short notification with only the id and the field that changed: TrackFlo reads the full movement back from McLeod before it updates anything.
TrackFlo answers 201 once it has received an alert, including one for a movement it doesn't track (an order type you've asked us to leave off the board, for example). It answers 200 when the body carries no record. McLeod does not need to retry either one: if TrackFlo can't apply an alert, the next scheduled read picks the change up.
4. Check that alerts are arriving
Confirm the hostname is reachable from your network:
https://<tenant>-integration-webhooks.trackflo.tech/healthreturns200.Enter a call-in on a live movement in McLeod.
Open the load in TrackFlo. The call-in should be on its timeline within a few seconds.
Record an arrival on one of the movement's stops. The stop should show as arrived in TrackFlo within a few seconds.
The call-in shows up, but only after several minutes
Call-ins arrive instantly, but stop changes lag
Each record type is its own alert. Check that the stop alert exists and points at /stop_update, not at the call-in or movement URL.
Status changes lag even though the status alert is set up
Check that the alert is active and points at /status_update. If it does, tell us the movement and the time of the change, and we check what arrived on our side.
Things to know
Status codes are yours. Brokerage status codes are configured per McLeod instance, so the mapping to TrackFlo statuses is built with you, not copied from another customer.
"Not found" is a 204. McLeod answers a lookup for a missing record with an empty success response rather than a 404. TrackFlo handles it; it is worth knowing if you ever read the API yourself.
Repeated alerts are harmless. McLeod sometimes posts the same change more than once. TrackFlo updates records in place, so a repeat changes nothing.
Deleted stops are cleaned up. McLeod reports a deleted stop as a stop alert with no record attached. TrackFlo checks the stop against McLeod and removes it from the load if it's gone. The scheduled reads remove it too if the alert never arrives.
Deleted movements leave the board. When a movement alert names a movement McLeod no longer has, TrackFlo confirms it with McLeod and takes that load off the board. If McLeod can't be reached, TrackFlo leaves the load alone.
TrackFlo's own call-ins come back to us. A call-in TrackFlo writes to McLeod triggers your call-in alert like any other. TrackFlo recognises its own by the
(via TrackFlo)suffix and doesn't duplicate it.Availability. McLeod-hosted instances have maintenance windows and occasional outages. TrackFlo retries and resumes; a gap in updates during a McLeod outage closes on the next successful read.