---
title: "Turvo Integration"
description: "Connect AI agents to Turvo, the transportation management system freight brokers and 3PLs run their loads in. Agents match carrier paperwork to loads, check carrier invoices against the agreed rate and accessorials, attach PODs, and move delivered loads to ready for billing."
url: https://flowrunner.ai/integrations/turvo
date_modified: 2026-11-16T14:50:08-08:00
---

# Turvo

[Logistics](https://flowrunner.ai/integrations/category/logistics-fulfillment)

Connect AI agents to Turvo, the transportation management system freight brokers and 3PLs run their loads in. Agents match carrier paperwork to loads, check carrier invoices against the agreed rate and accessorials, attach PODs, and move delivered loads to ready for billing.

[Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 triggers · 14 actions · Custom auth · available

[Turvo website](https://turvo.com/) · [Platform Documentation](https://app.turvo.com/lobby/documentation) · Capability data verified 2026-11-13

1.  A carrier emails a POD and invoice to the AP inbox
2.  Agent reads the load number, PRO and BOL from the PDF
3.  Find Load by Number matches the paperwork to the Turvo load
4.  Upload Document to Load attaches the POD as a POD
5.  Get Carrier Rate and Get Stop Times test each charge
6.  An accessorial missing from the rate goes to AP in Slack
7.  AP lead rules on extra charges before Ready for billing

## What This Integration Enables

A load in Turvo is not finished when the truck is empty. It is finished when the paperwork matches the money: the POD is on file, the carrier invoice agrees with the rate confirmation, and the customer can be billed. That gap between delivered and billed is where freight brokers and 3PLs lose days and margin, and it is the gap this connector is built around.

FlowRunner agents find a load by its number or any reference on it, and read the agreed carrier rate and the customer charges line by line. They read each stop's appointment against the actual arrival and departure, the carrier's dispatcher and driver contacts, and the rep assigned to the load. They read a load's full status history, including when a canceled load was canceled, by whom and why. They add an approved charge to what the customer is billed, attach and download documents, and move loads to a new status, including Ready for billing. They start from three events: a load reaching Delivered, a document added to a load, or any status change. The agent does the matching and the arithmetic. When a carrier invoice claims something the rate confirmation does not show, the agent stops and asks a person on Slack, email, WhatsApp or phone before the load goes to billing.

### Without FlowRunner

**Paperwork chased by email**: PODs and carrier invoices arrive in a shared inbox and get matched to loads by hand

**Invoices paid on trust**: Detention and lumper lines are checked against the rate confirmation only when someone has time

**Loads stall after delivery**: A delivered load waits for someone to notice the POD is in before it moves to billing

### With FlowRunner

**Filed on the right load**: Each POD lands on its load in Turvo with the load number confirmed, not guessed

**Checked line by line**: Every carrier invoice is compared to the agreed rate and accessorials before it is booked

**Billing queue kept current**: Loads with clean paperwork move to Ready for billing, and the rest come with a reason

## Flows you can build with Turvo

### [Emailed POD to ready to bill](https://flowrunner.ai/flows/turvo-emailed-pod-to-ready-to-bill)

A carrier emails a signed POD to the AP inbox in [Gmail](https://flowrunner.ai/integrations/gmail-service). The agent reads the load number, or the PRO or BOL number when the load number is missing, and calls Find Load by Number. That search covers active loads created in the last 180 days and returns found: false rather than failing, so an unmatched POD becomes an [automation exception](https://flowrunner.ai/concepts/automation-exceptions) instead of a document filed on the wrong load. On a match, Upload Document to Load attaches the PDF as a POD. A signed POD with nothing noted on it goes straight to Mark Load Ready to Bill. A missing signature or a shortage or damage note goes to the AP lead in [Slack](https://flowrunner.ai/integrations/slack) first.

[See the flow and import it](https://flowrunner.ai/flows/turvo-emailed-pod-to-ready-to-bill)

[](https://flowrunner.ai/flows/turvo-emailed-pod-to-ready-to-bill)

### Carrier invoice audit before booking

When a carrier invoice is added to a load, On Document Added fires. The agent calls Download Document to pull the file into FlowRunner storage, reads its lines, and calls Get Carrier Rate. That returns the agreed total with linehaul, fuel, detention, lumper, TONU and layover broken out. For a detention or layover line, Get Stop Times shows the minutes on site and minutes late at each stop, so the claim is checked against what Turvo recorded. If the invoice matches, the agent books it with Create Bill in [QuickBooks Online](https://flowrunner.ai/integrations/quickbooks-online). If it does not, the variance goes to the AP lead with both sets of numbers side by side.

### Delivered loads with missing paperwork

On Load Delivered fires for each load that reaches Delivered. The agent calls List Load Documents to see whether a POD is already attached. If it is, the agent reads Get Customer Charges and posts the billing summary to the billing channel in [Slack](https://flowrunner.ai/integrations/slack). If it is not, Get Load Carrier returns the dispatcher's name, email and phone, and the agent asks for the POD by text with Send SMS in [Twilio](https://flowrunner.ai/integrations/twilio). The load stays where it is, so nothing reaches the billing queue without proof of delivery behind it.

### TONU claims checked against the cancellation cutoff

A carrier invoices a truck-ordered-not-used fee on a load the shipper canceled. Turvo has no separate history feed, so the agent calls Get Load Status History, which reads every status change from the load itself. It returns when the load was canceled, by whom, the reason and the note, the first pickup appointment, and the minutes between the cancellation and that pickup. The agent compares those minutes with the cutoff in the carrier agreement. A cancellation inside the cutoff makes the TONU payable, checked against the TONU total from Get Carrier Rate. A cancellation well ahead of the cutoff goes to the AP lead in [Slack](https://flowrunner.ai/integrations/slack) with the timestamps, so the dispute rests on Turvo's own record.

## Human-in-Loop Highlight

The gate sits on Mark Load Ready to Bill, because that call commits the load to billing on its current charges. Say a carrier invoice for load 48213 carries a $275 detention line, and Get Carrier Rate shows no detention on the agreed rate. The agent does not pay it and does not ignore it. It reads Get Stop Times and posts to the AP channel: "Blue Line Trucking billed $275 detention on load 48213. The agreed rate has no detention line. Turvo shows the truck arrived 10 minutes early and spent 215 minutes at the delivery stop. Approve the detention, pay the agreed rate only, or dispute with the carrier?" Approving it may mean billing the customer the same detention, which is a pricing call, not a matching task. If the AP lead says to rebill it, the agent asks the rep Get Load names on the load before calling Add Customer Charge. That line goes onto what the customer is invoiced, and the connector has no action that takes a customer charge off again. The load moves to Ready for billing only after those answers. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) where the money is: the agent reconciles every load, and the person decides the ones where the paperwork disagrees.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

## Agent Capabilities

14 actions

### Loads

6

-   **Get Load** Reads one load by its Turvo ID: status, pickup and delivery dates, the delivered timestamp, every stop with its appointment and actual arrival and departure, every carrier with its dispatcher and driver contact, and every customer. It also returns the users on the load with role, email and phone, the assigned rep, and the customer account's owner, and for a canceled load, when, by whom and why. Used when a trigger or an earlier step has already identified the load, and to find the person who should answer for it.
-   **Find Load by Number** Finds a load by its load number or a reference on it, such as a PO, BOL, PRO, container, route or truck number, and returns the first match in full. Used to match emailed paperwork to its load. It returns found: false instead of failing, which lets the flow route an unmatched document to a person.
-   **Search Loads** Lists loads by status and date window, one page at a time, as summaries. Used for sweeps, such as every load delivered this week that is not yet ready for billing.
-   **Get Stop Times** Returns every stop in route order with its type, location, time zone, appointment, and actual arrival and departure, plus minutes on site and minutes late. Used to test a detention or layover charge against the times Turvo recorded.
-   **Get Load Status History** Returns every status change on a load, oldest first, with when it changed, who changed it and the stop it was recorded at, plus the current status with its note and location. For a canceled load it adds the cancellation details, the first pickup appointment and the minutes between them. Used to check a TONU claim against a cancellation cutoff.
-   **Get Load Carrier** Returns the carrier on a load with the dispatcher's name, email and phone, the driver's name, phone and email, and every other contact on that carrier order. Used to chase a missing POD or ask about a late stop.

### Rates and Charges

3

-   **Get Carrier Rate** Reads the agreed carrier pay on a load with every line item, plus linehaul, fuel, detention, lumper, TONU, layover and accessorial totals. Used to check a carrier invoice before it is paid.
-   **Get Customer Charges** Reads what the customer is billed on a load, line by line, with the same accessorial totals. Used to prepare billing and to compare margin against the carrier rate.
-   **Add Customer Charge** Adds one billable line, such as approved detention, a lumper fee or a layover, to what the customer is billed on a load, priced as rate times quantity with a note. The charges already on the load are kept, and the result returns the customer's charges after the change with the same totals as Get Customer Charges. Used to pass an approved accessorial through to the customer.

### Status

2

-   **Update Load Status** Moves a load to a new status, such as Delivered, Ready for billing or Carrier paid. Pickup and delivery statuses name the stop they happened at. Used when the flow confirms an event the load record has not caught up with.
-   **Mark Load Ready to Bill** Moves a load to Ready for billing so it lands in the billing queue. Used once the POD is attached and the carrier's charges are checked, and held back whenever they are not.

### Documents

3

-   **List Load Documents** Lists the documents attached to a load, such as rate confirmations, BOLs, PODs and invoices, with type, status and file names. Used to confirm a POD exists before billing.
-   **Download Document** Downloads every file in a load's document into FlowRunner file storage and returns a link to each. Used to send a carrier invoice to extraction, email it, or archive it.
-   **Upload Document to Load** Attaches a file to a load as a POD, BOL, rate confirmation, carrier invoice or other document. Turvo fetches the file from a URL, and a FlowRunner file link works.

## Triggers

3 triggers

### Event Triggers

3

-   **On Load Delivered** Fires once for each load that reaches Delivered, with the full load: stops, carriers, dates and the delivered timestamp. It starts the delivered-to-billed sweep. It reports active loads created in the last 180 days, and not loads delivered before the trigger was switched on.
-   **On Document Added** Fires when a document such as a POD, BOL, invoice or rate confirmation is added to a load. It starts carrier invoice checks and POD filing. Setup is manual: the trigger's callback URL goes into Turvo's Admin Console as a webhook subscription to the DOCUMENT\_SAVED event.
-   **On Load Status Changed** Fires when a load's status changes, for example to Delivered or Ready for billing. It keeps downstream systems and the billing team in step with the load. Setup is manual, through the same Turvo webhook settings with the SHIPMENT\_STATUS\_UPDATE event.

## Frequently asked questions

### What can FlowRunner do with Turvo?

FlowRunner agents can run Get Load, Find Load by Number, and Search Loads in Turvo, plus 11 more actions.

### Does connecting Turvo to FlowRunner require OAuth?

Turvo uses a custom authentication method to connect to FlowRunner.

### Can Turvo trigger a FlowRunner workflow automatically?

Yes. Turvo supports 3 triggers that can start a FlowRunner workflow automatically.

**Work at Turvo?** This integration exposes Turvo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current.

## Need a custom Turvo automation? Our team can build it for you.

Tell us the process. Our implementation team at Midnight Flow builds it around how you work, tests it on your real data, and keeps it running, in your own FlowRunner workspace.

[Have us build it](https://midnightflow.ai/packages/custom?utm_source=flowrunner.ai&utm_medium=referral&utm_campaign=general&utm_content=integrations.aside&utm_term=turvo)

---
Markdown version of https://flowrunner.ai/integrations/turvo. Site index: https://flowrunner.ai/llms.txt
