Logistics integration
DAT integration for AI workflows.
Beta — requires your DAT API access. Post loads, search the board and pull RateView lane rates from your workflows.
In short
Fluxo Flow connects to DAT with an API key or credentials you provide; workflows can post a load (JSON), search loads or trucks (JSON) and rateView lane rate lookup (JSON) and more. The integration is in beta.
Beta means it works but hasn't been tested against every account setup yet; actions and fields may still change. Found a problem? Tell us.
What you can do
Actions and triggers for DAT.
Actions
Post a load (JSON)
Posts a load to the DAT load board (Freight Posting API, POST /posting/v2/loads). You provide the body DAT's API reference specifies.
Search loads or trucks (JSON)
Creates a load or truck search (POST /search/v3/asset-queries). You provide the search criteria body DAT's API reference specifies.
RateView lane rate lookup (JSON)
Looks up lane rates (RateView, POST analytics /linehaulrates/v1/lookups). Needs a RateView Combo Pro or Premium seat.
Send a DAT API request
Calls any DAT freight API endpoint your access covers (posting, search, tracking), signed in as the connection's user.
Triggers
- None yet — start these workflows from a schedule, a webhook or another app.
Build it yourself
What teams build with DAT.
There's no ready-made template for DAT yet. These are the workflows to build: each step is a real node or DAT action.
Post a load after sign-off
- McLeod: New order
- Transformer: build the post body
- Human Review: broker approves
- DAT: Post a load (JSON)
Rate check before quoting
- Webhook trigger (quote request)
- DAT: RateView lane rate lookup (JSON)
- AI Generate: summarize the range
- Human Review: broker sets the rate
Scheduled truck search
- Scheduled trigger
- DAT: Search loads or trucks (JSON)
- Router: filter results
- Slack: Post a message
Step-by-step guides: Freight broker automation: six back-office workflows with DAT, Truckstop and McLeod
How to connect
Connect DAT in a minute.
Connects with an API key or credentials, tested before they're saved and encrypted at rest.
- Get DAT API access: a DAT load board subscription, a service account created by DAT, and a Connexion seat for the user requests run as (contact developersupport@dat.com).
- In Fluxo Flow open Settings → Integrations → DAT and enter the service account email/password and the DAT user's email.
- Use the DAT actions with the request bodies from DAT's API reference (developer.dat.com).
What you need on the DAT side
- A DAT load board subscription plus DAT API access: a service account created by DAT and a Connexion seat for the user requests run as (DAT developer support sets this up).
- RateView lookups need a RateView Combo Pro or Premium seat.
Permissions & limits
What it can access, and how fast it runs.
Limits and timing
- If DAT says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.
- Actions take the request bodies from DAT's API reference, which is available to DAT API customers.
- There's no new-matching-loads trigger yet: run a search on a schedule and filter the results.
FAQ
DAT questions, answered.
Why do the DAT actions take JSON?
DAT's API reference is only available to DAT API customers, so this beta connector signs in for you and sends the bodies DAT documents for your account. Ready-made forms will follow once the endpoints are verified with a DAT developer account.
Is there a “new matching loads” trigger?
Not yet. DAT's search results flow isn't publicly documented; until it's verified, run a search on a schedule and filter the results in your workflow.
What does a DAT user need?
A Connexion seat plus a seat for every service used (e.g. RateView Combo Pro or Premium for rate lookups). CarrierWatch and OnBoard aren't available over DAT's REST API.
Is the DAT integration finished?
It's in beta: it works, but it hasn't been tested against every account setup yet. Tell us if something doesn't behave as expected.
Can I use DAT on the Free plan?
You can connect it, build with it and Dry Run on the Free plan. Running workflows live (triggers, schedules, webhooks) needs a paid plan.
Can I call DAT endpoints the integration doesn't cover?
Yes, if DAT has an API: save a key in the encrypted credential vault and call it with an HTTP Request step.
Can I test a workflow without touching my real data?
Yes. Dry Run walks through every step with simulated app calls, so nothing is sent until you run it for real or activate its trigger.
Connect DAT to your first workflow.
Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.
Free to explore · No credit card · 30-day money-back guarantee on paid plans