Skip to content
English
Go to inspiringvacations.com
  • There are no suggestions because the search field is empty.

Daily NL Runner

The Daily NL Runner is the page Melbourne Ops use to produce the day's naming lists for the Manila team. It checks each route, pulls the passengers, builds the Daily NL Master Google Sheet with one tab per naming list, logs the run, and drafts the team Slack message. It replaces running the Daily NL Trigger in a Claude chat.

Page: Daily NL Runner
Owner: Josh McKie
Last updated: 28 Oct 2026

At a glance

Who uses it Melbourne Ops, each signed in with their own Claude account.
When Every weekday between 8am and 9am Melbourne for the main batch, plus one-off lists later in the day when needed.
What it does Checks routes, pulls passengers from the data warehouse (iv-dw), builds the master sheet in Naming List Data Files, writes the Run Log rows, and drafts the Slack message.
What stays manual Choosing what's due (the Naming List Pipeline does this), posting the Slack message, MNL copying lists into supplier sheets, and sending to suppliers. Aurora 95-day preliminary lists are run by Josh.
Fallback The Tableau method. If there's no NL message in Slack by 9:30am Melbourne, MNL use the Tableau method.

Is it live?

  • Yes. Every run reads the data warehouse at the moment you press the buttons, and reads the Reference Sheet (Combined Groups, Route rules, Linked Routes) fresh each time.
  • The sheet, Run Log rows and Recent runs are real. They're created under the login of the person running it.
  • Two things don't update by themselves:
    • Which lists are due: you paste these from the Pipeline, which refreshes at 8:05am, 12:05pm and 4:05pm.
    • The naming list formatting rules: the page carries a copy of the naming-list-automation scripts. Josh republishes the page when the rules change.

Before your first run

Do this a day ahead, not at 8am.

  1. Page access: Josh shares the Daily NL Runner with you. Open it while signed in to claude.ai.
  2. Connectors: in claude.ai Settings → Connectors, check that iv-dw, Google Drive and Google Sheets are connected.
  3. Google access: check you can open each of these:
  4. Test run: paste one route, tick Test run, and go through all four steps. The first time, claude.ai asks you to allow each connector for the page; allow them. A test run makes a sheet called "TEST - Daily NL Master …" and writes nothing to the Run Log. Delete the TEST sheet afterwards.

Each morning: the four steps

First, open the Naming List Pipeline, tick today's lists and press the Naming List button. Copy the lines it gives you.

Step 1: Lists to run

  • Paste the lines into the box: one list per line, route date first, then the exact route name. Use the route name from the Pipeline, not the tour name.
  • Leave Daily NL Trigger selected for the main morning batch. Choose One-off list(s) for anything outside it, such as a same-day follow-up. A one-off run gets its own sheet and Run Log rows, and no Slack message unless you ask for one.
  • Check that Test run is not ticked, then press Check routes.

Step 2: Check routes and passengers

The routes. Each line is matched to its Perseus route and date and given a status:

Status What to do
Ready Nothing. It will run.
Check Read the purple note. For example: the name only nearly matched, it's not a core route, it's Third Party only, or it looks like a combined group. Untick it if it shouldn't run.
Not matched The name or date is wrong, or a tour name was pasted. Copy the line again from the Pipeline. If it offers a choice, pick the right route.
Not running Unticked, by you or by the page's rules (for example no passengers booked, or Exclude on the Route rules tab). Tick it to run it anyway.
  • Combined groups (for example the two Magical Morocco routes) are added and merged into one tab automatically.
  • Possible combined group: two routes with the same date, supplier and city pair that aren't on the Combined Groups tab. Stop and ask Josh before running.
  • Already in the Run Log: if a list was already run today, tick "This run replaces Run Log row N". The old row is then marked SUPERSEDED.
  • Unticked lines go in the Run Log as "Not run" with the reason, unless you untick that option.

The passengers. This fills in by itself under the routes. The page pulls every ticked list's passengers and counts them with the naming list rules. The first run of the day takes about a minute while the page loads its engine. If you change a tick, it updates within a few seconds.

  • Green "Every list matches pax_sold": carry on.
  • Red "doesn't match pax_sold": the list is still built, its tab name starts with DISCREPANCY, and it's logged Match = No. Carry on, but MNL must re-run that list through the Tableau method before sending. The page drafts a thread reply that tells them.
  • Open Bookings to chase to see passport, payment and name-check items by booking ID.

Nothing has been created yet. When you're happy, press Create the Google Sheet at the bottom of step 2.

Step 3: Create the sheet and log the run

  • The page copies the NL Master Template into Naming List Data Files as "Daily NL Master DD Mon YYYY" and fills one tab per list. It reads every cell back to check it, then adds the Run Log rows. A second run on the same day gets "(2)" added to the name.
  • Wait until every line says Done. Step 2 is locked from now on, so the sheet always matches what you checked.
  • If a line fails, read the message, fix the cause (usually reconnecting a connector), then press Carry on from this step.
  • If it says some cells differ, open the sheet and check those cells before MNL copy the list.

Step 4: Report

A summary of what ran: the sheet link, each tab's bookings and passengers, what to chase, anything odd in the data, and the Run Log rows. Press Copy the report if someone needs it.

Final Step: The team message

The draft appears in the right-hand column once the sheet is ready. The page never posts to Slack; you do.

  1. Pick the sign-off emoji. The page suggests one that hasn't been used recently.
  2. Press Copy message and paste it into #mnl-mel-allotment-tasks.
  3. Link the words "Naming List Pipeline" and "Master list" using the two Copy buttons, then post.
  4. If a list didn't match, post the drafted reply in the thread.

Don't change the wording: it's kept the same every day so the team can scan it quickly.

If something goes wrong

What you see What to do
A connector error (iv-dw, Drive or Sheets) Reconnect it in claude.ai Settings → Connectors, then press the step's button again.
"The lookup failed" or "didn't answer" on a route Wait a minute and press Check routes again. Check the line is the route name from the Pipeline.
A list is too big for the page Untick it and run that list with the Tableau method.
You need to start again Press Reset twice. It clears the page only: sheets and Run Log rows already made stay as they are. If a half-made sheet is left in the folder, delete it before running again.
Nothing works and it's getting late Tell MNL to use the Tableau method, then contact Josh, or Chamika if Josh is away.

Good to know

  • Recent runs (right-hand column) lists each run with its sheet link, list count, time taken and who ran it.
  • Privacy: passenger details are only in the generated sheet and the Run Log notes. The page doesn't keep passenger data, and Recent runs holds counts and links only. Slack messages carry booking IDs at most, never names or passport details.
  • Sharing: only Josh can share the page. New users need the access listed under "Before your first run".