Bill of Lading Field Extractor
Drop a bill of lading or packing list as raw text and get every field back as clean structured JSON.
A tiny data-entry clerk that never mis-keys. Paste the raw text of a bill of lading, packing list, or commercial invoice and it returns a normalized record (shipper, consignee, carrier, BOL number, piece and weight totals, line items, incoterms, hazmat flag) so your TMS or freight-audit agent ingests structured data instead of a wall of text. Flags anything missing so you know what to chase before the shipment moves. Example input: "BILL OF LADING BOL# 884213 Ship From: Acme Mfg, 14 Industrial Rd, Akron OH Ship To: Northwind DC, 200 Dock Ave, Columbus OH Carrier: Blue Line Freight PRO 55-7781 Pieces: 6 pallets Wt: 3,420 lb Class 70 Terms: Prepaid Items: 4x Pump A-22, 2x Valve kit V-9". Example output: strict JSON with bol_number, pro_number, shipper, consignee, carrier, pieces, weight_lb, freight_class, terms, hazmat, line_items[], and missing_fields[].
Who pays: Freight-audit and TMS ingestion agents: every inbound BOL or packing list has to become a structured record before it can be matched or paid.
Each accepted caller request triggers the 3-step flow once. Ordinary services may expose a free preview; payment-enabled calls may settle through x402; company or otherwise unready services may be unavailable.
The template opens with this intended price loaded. Launch publishes the service and its current call state. An ordinary service may preview; only a separately payment-enabled service exposes x402 terms for paid USDC calls.
The wired flow uses built-in nodes only. Any external action shows the Connection it needs for live use; a Connection is a reviewed link to your own webhook or account, and nothing external fires in preview.
Open Bill of Lading Field Extractor in the studio
The 3-step flow arrives wired, with its suggested price loaded, and ready for a free builder preview. Make it yours, then launch with its public call state reported.
Open this template →