Skip to content
Rookiefeed

Send each morning's new carriers to your CRM or sheet

Rookiefeed can POST each morning's new carriers that match your filters, plus watchlist changes, to a webhook. Setup for Zapier, GoHighLevel and Google Sheets.

By Jake Marsh. Last reviewed

What gets sent, and when

Each morning, right after the 7am Central email, Rookiefeed sends one HTTPS POST per new carrier that matches your dashboard filters and states. The body is one JSON object whose data has the same fields as the CSV: MC and USDOT numbers, legal name, contact, phone, cell, email, address, fleet size, equipment, insurance on file and authority status. Each row is sent once, even when it appears in several mornings' data.

If you use the watchlist, every change on a carrier you watch (insurance cancellation filed or lapsed, a new insurer, authority revoked, inactive or reinstated, new contact details) is sent the same morning as its own event, type watchlist.change.

Webhooks come with the State, Regional and Nationwide plans, at no extra cost. The webhook runs on its own: pausing the email or switching it to Mondays only doesn't change what the webhook gets.

Set it up on your dashboard

  1. Get a webhook URL from the app you want the carriers in (the recipes below show where Zapier, GoHighLevel and Google Sheets give you one). It must start with https://.
  2. Sign in, open the dashboard and click Webhook.
  3. Paste the URL and click Add webhook. Copy the signing secret that appears and keep it somewhere safe: it is shown only once. You can make a new one at any time.
  4. Click Send test event. The dashboard tells you what your endpoint answered, and your app now has a sample to map fields from.
  5. From the next morning, the carriers arrive by themselves. Recent deliveries and any errors are listed on the same page.

Payload examples

A new carrier (type is feed.row). The id is unique per row and subscriber, so use it to skip duplicates if a retry ever delivers twice.

feed.row
{
  "id": "evt_feed_123_987654",
  "type": "feed.row",
  "created_at": "2026-11-16T12:31:07.000Z",
  "feed_date": "2026-11-16",
  "data": {
    "event": "Authority granted",
    "event_date": "2026-11-16",
    "mc_number": "MC1234567",
    "usdot_number": "4567890",
    "authority_type": "Motor Carrier of Property (Except Household Goods)",
    "first_time_authority": "yes",
    "applied_date": "2026-10-20",
    "days_application_to_grant": 27,
    "legal_name": "Example Freight LLC",
    "dba_name": null,
    "contact_name": "Jordan Example",
    "contact_name_2": null,
    "phone": "(555) 010-0142",
    "cell_phone": "(555) 010-0142",
    "email": "dispatch@example.com",
    "email_type": "business",
    "street": "100 Example Rd",
    "city": "Dallas",
    "state": "TX",
    "zip": "75201",
    "power_units": 1,
    "tractors": 1,
    "trailers": 1,
    "drivers": 1,
    "fleet_size": "1",
    "operation": "interstate",
    "hazmat": "no",
    "equipment_guess": "Dry van",
    "cargo": "General Freight",
    "usdot_added": "2026-10-14",
    "bipd_insurance_on_file": 750000,
    "insurer": "Example Mutual Insurance Company",
    "insurance_effective": "2026-11-10",
    "authority_status_now": "Active",
    "best_phone": null,
    "best_phone_type": null,
    "filing_service_contact": null,
    "contact_score": null,
    "authority_granted_date": "2026-11-16"
  }
}

A watchlist change (type is watchlist.change). change is one of insurance_cancellation_filed, insurance_lapsed, insurance_restored, insurer_new, authority_revoked, authority_inactive, authority_reinstated, authority_granted or contact_changed; before and after hold only the fields that changed.

watchlist.change
{
  "id": "evt_watch_123_4321",
  "type": "watchlist.change",
  "created_at": "2026-11-16T12:31:09.000Z",
  "feed_date": "2026-11-16",
  "data": {
    "change": "insurance_cancellation_filed",
    "change_label": "Insurance cancellation filed",
    "summary": "Liability insurance cancellation filed by Example Mutual Insurance Company, effective 2026-12-16",
    "detected_on": "2026-11-16",
    "watched_number": "MC1234567",
    "mc_number": "MC1234567",
    "usdot_number": "4567890",
    "legal_name": "Example Freight LLC",
    "dba_name": null,
    "city": "Dallas",
    "state": "TX",
    "authority_status": "Active",
    "authority_reason": null,
    "insurance": "cancel_pending",
    "insurer": "Example Mutual Insurance Company",
    "liability_limit": 750000,
    "insurance_effective": "2026-11-10",
    "cancellation_effective": "2026-12-16",
    "contact_name": "Jordan Example",
    "phone": "(555) 010-0142",
    "cell_phone": "(555) 010-0142",
    "email": "dispatch@example.com",
    "street": "100 Example Rd",
    "zip": "75201",
    "before": {
      "insurance": "on_file",
      "cancel_effective": null
    },
    "after": {
      "insurance": "cancel_pending",
      "cancel_effective": "2026-12-16"
    }
  }
}

The test button sends type test with the example carrier above and "test": true in data. Every request also carries the headers Rookiefeed-Event-Id and Rookiefeed-Event-Type.

Zapier (Catch Hook)

  1. In Zapier, click Create, then Zaps.
  2. For the trigger, pick Webhooks by Zapier and the event Catch Hook. Leave Pick off a Child Key empty and continue.
  3. Copy the webhook URL Zapier shows (it starts with https://hooks.zapier.com/hooks/catch/) and add it on your Rookiefeed dashboard under Webhook.
  4. Click Send test event on the dashboard, then Test trigger in Zapier. Pick the request that arrives.
  5. Add your action: HubSpot, Salesforce, Pipedrive, a Google Sheets row, a Slack message or anything else. Map fields from the sample, for example Data Legal Name, Data Phone, Data Email and Data Mc Number.
  6. To send only new carriers (not test events or watchlist changes) to that action, add a Filter by Zapier step: Type exactly matches feed.row.
  7. Publish the Zap.

Catch Hook doesn't hand the request headers to later steps. If you want to check the signature in Zapier, use Catch Raw Hook instead and a Code by Zapier step with the Node example under Checking the signature.

GoHighLevel (inbound webhook)

  1. In your GoHighLevel sub-account, open Automation and create a new workflow from scratch.
  2. Add a trigger and pick Inbound Webhook. Copy the URL it shows.
  3. Add that URL on your Rookiefeed dashboard under Webhook and click Send test event.
  4. Back in the trigger, click Fetch Sample Requests, pick the test request and save the trigger.
  5. Add the action Create Contact (or Create/Update Contact). Map email to inboundWebhookRequest.data.email, phone to inboundWebhookRequest.data.phone, company name to inboundWebhookRequest.data.legal_name and first name to inboundWebhookRequest.data.contact_name. Put the MC number in a custom field if you keep one.
  6. Optional: add an If/Else branch on inboundWebhookRequest.type so feed.row creates contacts and watchlist.change adds a tag or a task to an existing one.
  7. Add a tag such as new-authority so you can build a smart list or a follow-up workflow, then save and publish.

Google Sheets (Apps Script doPost)

  1. Open a new Google Sheet. Click Extensions, then Apps Script.
  2. Delete the sample code and paste the script below. Save.
  3. In Apps Script, open Project Settings, then Script Properties, and add ROOKIEFEED_SECRET with your signing secret as the value. (Do this after step 6 if you don't have the secret yet; until then the script accepts every request.)
  4. Click Deploy, then New deployment. Pick the type Web app, set Execute as to Me and Who has access to Anyone, then Deploy and allow access.
  5. Copy the web app URL (it ends in /exec).
  6. Add it on your Rookiefeed dashboard under Webhook and click Send test event. A Carriers tab appears with a header row and the test carrier.
Code.gs
// Rookiefeed -> Google Sheets. Paste into Extensions > Apps Script, then deploy as a web app.
const SECRET = PropertiesService.getScriptProperties().getProperty("ROOKIEFEED_SECRET");

function doPost(e) {
  const body = e.postData.contents;
  if (SECRET && !verify(body, e.parameter.rf_signature, SECRET)) {
    return ContentService.createTextOutput("bad signature");
  }
  const event = JSON.parse(body);
  const book = SpreadsheetApp.getActiveSpreadsheet();
  const tab = event.type === "watchlist.change" ? "Watchlist" : "Carriers";
  const sheet = book.getSheetByName(tab) || book.insertSheet(tab);
  const data = event.data;
  const fields = Object.keys(data).filter((k) => data[k] === null || typeof data[k] !== "object");
  if (sheet.getLastRow() === 0) sheet.appendRow(["event_id", "type"].concat(fields));
  const header = sheet.getRange(1, 1, 1, sheet.getLastColumn()).getValues()[0];
  sheet.appendRow(header.map((h) => (h === "event_id" ? event.id : h === "type" ? event.type : data[h] == null ? "" : data[h])));
  return ContentService.createTextOutput("ok");
}

function verify(body, header, secret) {
  if (!header) return false;
  const parts = {};
  header.split(",").forEach((p) => {
    const i = p.indexOf("=");
    parts[p.slice(0, i)] = p.slice(i + 1);
  });
  const t = Number(parts.t);
  if (!t || Math.abs(Date.now() / 1000 - t) > 300) return false;
  const mac = Utilities.computeHmacSha256Signature(t + "." + body, secret, Utilities.Charset.UTF_8);
  const hex = mac.map((b) => ("0" + (b & 0xff).toString(16)).slice(-2)).join("");
  return hex === parts.v1;
}

Apps Script can't read request headers, so for URLs on script.google.com we also send the signature as the rf_signature query parameter; the script checks that. Each new carrier becomes a row on the Carriers tab and each watchlist change a row on the Watchlist tab. If you change the script, deploy a new version (Deploy, Manage deployments, edit, New version) or the old code keeps running.

Checking the signature

Every request carries a Rookiefeed-Signature header like t=1763296267,v1=5f2c.... t is the send time in Unix seconds and v1 is an HMAC-SHA256, in hex, of the timestamp, a period and the raw request body, keyed with your signing secret. Recompute it over the body exactly as received, compare, and reject requests more than 5 minutes old.

Node.js
import crypto from "node:crypto";

// rawBody: the request body exactly as received (before JSON.parse).
export function verifyRookiefeed(rawBody, header, secret) {
  const parts = Object.fromEntries(String(header).split(",").map((p) => p.split("=")));
  const t = Number(parts.t);
  if (!t || Math.abs(Date.now() / 1000 - t) > 300) return false;
  const expected = crypto.createHmac("sha256", secret).update(`${t}.${rawBody}`).digest("hex");
  const got = String(parts.v1 ?? "");
  return got.length === expected.length && crypto.timingSafeEqual(Buffer.from(got), Buffer.from(expected));
}

Retries, timeouts and limits

Answer with any 2xx status to accept an event. We wait up to 10 seconds, don't follow redirects (except the one Apps Script sends after it runs) and read only the start of your answer. If the request fails or times out we try again after 5 minutes, 30 minutes, 2 hours, 6 hours, 12 hours: 6 tries over about a day. After that the event is marked failed on your dashboard.

The URL has to be a public https address on the standard port. Private, local and reserved addresses are refused. Each event is one carrier and stays well under 64 KB.

Questions or a CRM that needs something different: email hello@greatwork.company.

Not a subscriber yet? See plans or build a free list.