Automated Tour Guide Daily Manifest
Every morning, WebRun opens FareHarbor and pulls today's bookings by guide, compiles a manifest for each guide with guest names, party sizes, special requests, accessibility notes, and meeting points, logs the manifest to a shared Google Sheet, and posts each guide's run sheet to their Slack channel.
How do I automatically generate and send a daily manifest to my tour guides?
Every morning, WebRun pulls today's FareHarbor bookings by guide, compiles a full manifest with guest names, party sizes, meeting points, and special request notes, writes each guide's run sheet to Google Sheets, and posts it to Slack so every guide starts the day fully briefed without any manual prep.
- Every guide has their full manifest in Slack before the first tour of the day
- Operations managers spend zero time manually compiling run sheets
- Special requests and accessibility notes are surfaced at a glance, reducing on-tour surprises
Built for tour operators with multiple guides · activity companies · outdoor adventure businesses · group tour managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
fareharbor.comin a real browser with your saved login - no setup, no API keys. -
1
FareHarbor - pull today's bookings by guide
fareharbor.com
WebRun opens FareHarbor to pull today's bookings by guide. - Open FareHarbor and filter today's bookings by assigned guide
- For each guide, collect: tour name, start time, meeting point, guest names, party sizes, booking IDs, and any special requests or accessibility notes
- Note any tours at full capacity and any last-minute additions
Done when Each guide has a complete list of their tours and guest details for today.
-
2
Google Sheets - compile and log manifests
google.com
WebRun opens Google Sheets to compile and log manifests. - Open the daily manifest Google Sheet
- Write each guide's manifest into a dedicated tab, organised by tour start time
- Include a total headcount row per tour for quick reference
Done when All guides' manifests are written to the Google Sheet with headcounts.
-
3
Slack - post each guide's manifest
slack.com
WebRun opens Slack to post each guide's manifest. - Post each guide's manifest as a formatted message to the guides Slack channel or a dedicated DM
- Include tour name, start time, meeting point, guest list, and any flagged notes at the top
- Add a link to the full Google Sheet for reference
Done when Every guide has their day's manifest in Slack before the first tour starts.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Can it post each guide's manifest to a private Slack DM instead of a shared channel?
Yes. Configure the workflow with each guide's Slack handle and their manifests will be posted as direct messages, keeping guest details visible only to the relevant guide.
What if a booking is added or changed after the morning manifest is sent?
Run the workflow again at any time to generate an updated manifest. The Google Sheet is overwritten with fresh data and a new Slack message is posted to flag the update.
Does it include accessibility or dietary notes for guests?
Yes. It reads any special request or notes field from FareHarbor and surfaces those at the top of the relevant guest line in each guide's manifest.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.