Agent setup guide
Load Board Poster
Turns each new McLeod order into a Truckstop load post with a suggested rate, posted once a broker approves it.
What it does
Turns each new McLeod order into a Truckstop load post with a suggested rate, posted once a broker approves it.
- Starts on each new order in your McLeod LoadMaster / PowerBroker server.
- AI reads the order: lane, pickup and delivery windows, equipment (mapped to Truckstop's codes with your equipment map), weight, commodity and the customer rate. Covered, incomplete or excluded orders are skipped with the reason.
- Pulls a Truckstop Rate Insights estimate for the lane and suggests the all-in rate to post under your rules, never above the customer rate minus your minimum margin.
- The rate per mile shown to the broker is recalculated in code (posted rate ÷ miles) — never by the AI; a wrong AI figure is corrected and flagged.
- A broker approves or edits the rate and note in Reviews; approved loads are posted to the Truckstop load board with your contact details.
- Every order, estimate, decision and Truckstop load ID is kept in the run history.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- McLeod API access (web services URL reachable from the internet) and Truckstop API access with Load Management and Rate Insights.
- Your equipment map (McLeod type → Truckstop code and IDs) and posting rules.
What it doesn't do
- It doesn't post to DAT or other load boards: Truckstop only.
- It doesn't book or vet carriers, or update the order in McLeod.
- The Truckstop estimate is a market estimate, not a guaranteed buy rate. When no usable estimate comes back, the broker sets the rate.
- Multi-stop loads are posted with the first pickup and last drop; extra stops go in the note.
- Coming soon until McLeod and Truckstop are approved.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.
Before you start
- A paid plan: agents run live, and the Free plan only runs Dry Runs.
- An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
- These apps, connected in Settings → Integrations: McLeod (LoadMaster / PowerBroker) and Truckstop.
- The app it watches, connected in Settings → Integrations (the agent starts from an app event).
- About 30 minutes.
Set it up step by step
Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.
1. Connect your AI provider
The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
2. Connect McLeod
Connect your McLeod server (web services URL + user or API token) in Settings → Integrations → McLeod. Your McLeod admin can provide these.
3. Connect Truckstop
Connect Truckstop with the client ID/secret Truckstop issued for your integration (Load Management + Rate Insights).
4. Pick the McLeod connection
Open the trigger “New order in McLeod” and pick your McLeod connection.
| Setting | What to enter | In step |
|---|---|---|
| McLeod connection | The McLeod server whose new orders start the agent. Pick your connected McLeod (LoadMaster / PowerBroker) account. | “New order in McLeod” |
5. Map equipment and write your posting rules
Open “Read the order and build the post” and “Suggest the posted rate” and replace the placeholders with your equipment map and posting rules.
| Setting | What to enter | In step |
|---|---|---|
| Equipment map | Replace the placeholder with each McLeod equipment type and its Truckstop equipment code (V, R, F…), equipment type ID and mode ID (from your Truckstop integration documentation). It starts as “[MAP YOUR MCLEOD EQUIPMENT TYPES TO TRUCKSTOP: EQUIPMENT CODE, EQUIPMENT TYPE ID AND MODE ID]” until you replace it. | “Read the order and build the post” |
| Posting rules (load step) | Replace the placeholder with when NOT to post (e.g. dedicated customers, loads already covered) and your minimum margin. It starts as “[DESCRIBE HOW YOU PRICE A POSTED RATE: TARGET MARGIN, MINIMUMS, WHEN NOT TO POST]” until you replace it. | “Read the order and build the post” |
| Posting rules (pricing step) | Replace the placeholder with how you price a posted rate: where in the market range to post, rounding, minimum per load and minimum margin. It starts as “[DESCRIBE HOW YOU PRICE A POSTED RATE: TARGET MARGIN, MINIMUMS, WHEN NOT TO POST]” until you replace it. | “Suggest the posted rate” |
6. Pick the Truckstop connection and contact
Open “Get the Truckstop rate estimate” and “Post the load on Truckstop”, pick your Truckstop connection in each and fill in the contact name and phone carriers will see.
| Setting | What to enter | In step |
|---|---|---|
| Truckstop connection (rate estimate) | Your Truckstop API connection, licensed for Rate Insights. Pick your connected Truckstop account. | “Get the Truckstop rate estimate” |
| Truckstop connection (posting) | Your Truckstop API connection used to post loads (usually the same one). Pick your connected Truckstop account. | “Post the load on Truckstop” |
| Contact name on posts | The name carriers ask for when they call about a load, e.g. your load board desk. | “Post the load on Truckstop” |
| Contact phone on posts | The number carriers call about your posted loads. | “Post the load on Truckstop” |
7. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
8. Switch the trigger on
Open the trigger and press “Activate app trigger”: from then on each new McLeod order starts a run. Assign the review step to your load board desk.
How it works
The agent is a normal workflow with 11 steps (2 AI steps, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.
- New order in McLeod — Starts on “New order” in McLeod (LoadMaster / PowerBroker) (an app event). Starts a run for each new order on your McLeod LoadMaster / PowerBroker server (checked every few minutes).
- Read the order and build the post — AI step (runs on your AI provider key). AI reads the McLeod order and pulls out the lane, pickup and delivery windows, equipment, weight and the customer rate, maps the equipment to Truckstop's codes and decides whether the load should be posted.
- Post this load? — Decision: picks the branch to follow. Orders that are already covered, incomplete or excluded by your rules are skipped (with the reason kept); the rest get a market rate and a suggested post.
- Get the Truckstop rate estimate — Truckstop: Get a Rate Insights estimate. Branch: Post. Asks Truckstop Rate Insights what carriers are being paid on this lane for this equipment and ship date.
- Suggest the posted rate — AI step (runs on your AI provider key). AI reads the Truckstop estimate, applies your posting rules and margin against the customer rate, and suggests the all-in rate to post with its reasoning.
- Check the math — Step. Recalculates the rate per mile (posted rate ÷ miles) in code — not by AI — and flags it for the broker if the AI got it wrong.
- Approve the post and rate — A person approves or rejects it in Reviews (the run waits). A broker checks the lane, windows and suggested rate in Reviews, edits the rate or note if needed, and approves it to post on Truckstop.
- Post the load on Truckstop — Truckstop: Post a load. Branch: Approved. Posts the approved load to the Truckstop load board with the lane, windows, equipment, your load number, the approved rate and your contact.
- Posted — Kept in the run history. The run history keeps the order, the estimate, the approved rate and Truckstop's load ID.
- Not approved — Kept in the run history. Branch: Rejected. Rejected posts are kept in the run history; nothing was posted.
- Not posted — Kept in the run history. Branch: Don't post. The run history keeps the order and why it wasn't posted.
Test it with Dry Run
Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.
Sample data fields
id, status, customer_id, order.__type, order.id, order.status, order.customer_id, order.equipment_type_id, order.commodity, order.weight, order.total_charge, order.stops.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
- Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.
Go live
- Open the trigger and press “Activate app trigger”: from then on each new McLeod order starts a run. Assign the review step to your load board desk.
- Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
- The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
- When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.
Questions
Does it post without a person checking?
No. Every post waits in Reviews until a broker approves the lane and rate; they can edit the rate first.
Does it post to DAT too?
Not yet. It posts to Truckstop only.
Does it book carriers?
No. It posts the load; carriers call you and you book them as usual.
Troubleshooting
- “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
- A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
- An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
- No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
- A run shows as paused: it's waiting for someone in Reviews to approve or reject it.
- A step failed: open the run in History and check that step in the Trace tab for the error and what it received.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .