Your stack stays. Harpie joins it.
Forwarding operations run on a real mix: a TMS, a thousand emails a day, rate sheets, portals, and an accounting system that holds the truth. Harpie connects to all of it and works in place, no migration, no rip-and-replace.
Connection categories
What Harpie connects to
Categories below are connection patterns, not partnership claims. Each connection card declares exactly what is read, what may be written, and its permission scope.
TMS & forwarding systems
Shipment, quote, and milestone data, read and written in place.
Email & communication
RFQs, carrier replies, and customer threads, understood in context.
Spreadsheets & rate files
The rate sheets and trackers your operation already runs on.
Carrier portals & load boards
Bookings, tracking, and capacity where carriers publish them.
EDI / API connections
Structured messaging with partners that support it.
Accounting & ERP
The financial truth each shipment P&L reconciles against.
How connection works
Read first. Act when granted.
Every connection starts read-only. Write permissions are granted per agent and per action type as you expand.
01
Connect read-only
Harpie observes shipments, quotes, and messages without changing anything.
02
Map the operation
Workflows, document sets, and rate structures become a working model of your business.
03
Grant actions
You enable specific write actions per agent, update a milestone, send a quote, draft an invoice line.
04
Audit everything
Every read and write is logged with its agent, trigger, and result.
Harpie · Agentic workforce
Bring Harpie into your stack
Five agents. One operating intelligence. No migration, no long onboarding.