Automated Ancestry Hint Tracking for Researchers
Every morning, WebRun opens Ancestry, checks every client tree for new record hints, saves the matched documents into the right client folder in Google Drive, and posts the research team a Slack summary of what's new and which tree it belongs to.
How do I track new Ancestry hints across multiple client family trees?
WebRun checks every client tree on Ancestry each morning for new record hints, saves the matched documents into the right client folder in Google Drive, and posts the research team a Slack digest naming the ancestor, record type, and assigned researcher. Genealogy services get a sorted, filed lead list without manually opening every tree.
- New hints are filed and assigned the same morning they appear
- Researchers open Slack to a sorted list instead of checking each tree
- Client folders in Drive stay current with every matched record
Built for professional genealogists · heritage research services · family history consultants · archival research teams
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
www.ancestry.com/account/signinin a real browser with your saved login - no setup, no API keys. -
1
Ancestry - find new record hints across client trees
ancestry.com
WebRun opens Ancestry to find new record hints across client trees. - Open each client tree and check the hints queue
- Note which hint is new since the last check
- Record the ancestor, record type, and confidence for each
Done when Every tree has been checked and new hints are listed.
-
2
Google Drive - save matched records to the client folder
drive.google.com
WebRun opens Google Drive to save matched records to the client folder. - Save each new hint's record image or citation to the client's folder
- Name the file with the ancestor and record type
- Leave previously saved hints untouched
Done when Every new hint is filed in the right client folder.
-
3
Slack - notify the research team
slack.com
WebRun opens Slack to notify the research team. - Post the day's new hints to the research channel by client
- List the ancestor and record type for each
- Tag the researcher assigned to that tree
Done when The research team has today's hint digest with an owner for each tree.
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
Will it attach hints to the tree or change any records?
No. WebRun only reads the hints queue and files copies of the records. Attaching or rejecting a hint on the tree is left to the researcher.
How does it know which client a hint belongs to?
Each Ancestry tree maps to one client folder in Google Drive, so a hint on a given tree always files to the matching folder.
What if two researchers work the same tree?
The Slack post tags the researcher currently assigned, so hints do not sit unclaimed or get worked twice.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.