Automate MercuryGate Freight Billing with n8n: NWA Guide

Step 1: Set Your Trigger – Shipment Delivered in MercuryGate

First, we gotta identify when a shipment is actually done. In n8n, you'll set up a webhook or an HTTP request node that listens for a 'delivery confirmed' status update from MercuryGate. This is your green light. MercuryGate's API can push this information out, or you can schedule n8n to pull it regularly. The goal is real-time processing, so a webhook is usually the smarter play. This trigger ensures we only start the billing process when the actual work is completed, avoiding premature invoicing and subsequent corrections that waste time.

{
  "webhookUrl": "https://your.n8n.webhook.address/webhook-id",
  "method": "POST",
  "headers": {
    "Content-Type": "application/json"
  },
  "body": {
    "shipmentId": "{{ $json.shipmentId }}",
    "status": "DELIVERED",
    "deliveryDate": "{{ $json.deliveryDate }}"
  }
}

Step 2: Pull Shipment Details from MercuryGate

Once triggered, n8n needs to grab all the specific details for that completed shipment from MercuryGate. This means using MercuryGate's API to fetch the Bill of Lading (BOL) number, carrier details, actual freight charges, accessorials, and any proof of delivery (POD) documents. You'll use an HTTP Request node in n8n, pointing it at MercuryGate's API endpoint. Make sure you've got the right API keys and authentication set up. This data is the backbone of your invoice, so getting it all, and getting it right, is critical for accurate billing and avoiding disputes down the line.

Step 3: Transform Data for Your Accounting System

MercuryGate's data format ain't always what your accounting system, like QuickBooks Online or SAP Business One, expects. This is where n8n's 'Function' or 'Code' node comes in handy. You'll map the MercuryGate fields (e.g., `totalCharges`, `carrierName`, `bolNumber`) to the corresponding fields in your accounting system's invoice structure (e.g., `Amount`, `VendorName`, `ReferenceNumber`). This step ensures the data is clean, formatted correctly, and ready to be understood by your financial software. Skipping this leads to errors and manual fixes, defeating the whole purpose of automation.

let invoiceData = {
  "CustomerRef": {
    "value": items[0].json.customerID
  },
  "Line": [
    {
      "Amount": items[0].json.totalCharges,
      "DetailType": "SalesItemLineDetail",
      "SalesItemLineDetail": {
        "ItemRef": {
          "value": "FREIGHT_SERVICE"
        }
      }
    }
  ],
  "DocNumber": items[0].json.bolNumber,
  "TxnDate": items[0].json.deliveryDate
};
return [{ json: invoiceData }];

Step 4: Create Invoice in Your Accounting System

With the data transformed, it's time to create the actual invoice. You'll use n8n's dedicated integration nodes for QuickBooks, SAP, or whatever accounting platform you use. If a direct node isn't available, an HTTP Request node can hit your accounting system's API to create the invoice. Pass the perfectly formatted data from the previous step. This action generates a draft or final invoice, complete with all line items, customer details, and total amounts, ready for review or immediate dispatch. This is where the rubber meets the road, turning a completed shipment into a receivable asset.

Step 5: Update MercuryGate with Invoice Status and ID

Once the invoice is created in your accounting system, you need to close the loop. Use another HTTP Request node in n8n to send the new invoice ID and status (e.g., 'Invoiced', 'Awaiting Payment') back to MercuryGate. This keeps your TMS records accurate and provides a clear audit trail. Anyone looking at the shipment in MercuryGate will immediately see that it's been billed and reference the corresponding invoice number. This visibility is crucial for customer service, dispute resolution, and overall operational transparency, ensuring everyone is on the same page.

Step 6: Error Handling and Notifications

Things go wrong. Systems hiccup. You need a plan for when they do. Set up error handling paths in n8n. If an invoice fails to create, send an email or Slack notification to your billing team with the specific error message and shipment details. This way, issues are caught immediately and can be addressed manually without delaying payment. Don't just let errors silently fail; make sure someone knows about it so they can jump on it and keep the cash flowing. This proactive approach saves headaches and prevents lost revenue.