Track every queen change across your hives
Every Monday, WebRun opens MyApiary, reads the queen management records for each colony, updates a Google Sheet with the current queen's age, source, and marking colour, and posts your team a Slack digest of the past week's requeens plus any colony whose queen is past your replacement age.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep a queen replacement history for every hive automatically?
Every Monday WebRun opens MyApiary, reads each colony's queen management records, and updates a Google Sheet with the current queen's age, source, and marking colour plus a dated history line for any requeen. It then posts your team a Slack digest of the week's queen changes and any colony past your replacement age, oldest first.
- Every hive keeps a dated queen history without manual bookkeeping
- Overdue colonies surface each Monday so requeening gets planned in time
- Supersedures and manual requeens are recorded distinctly and accurately
Built for queen rearers · commercial beekeepers · apiary managers · breeding programmes
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.myapiary.comin a real browser with your saved login - no setup, no API keys. -
1
MyApiary - read queen management records
WebRun opens MyApiary to read each colony's queen records. - Open MyApiary and go to the queen management records
- For each colony read the current queen's introduction date, source, and marking colour
- Capture any queen change, supersedure, or loss logged in the past week
- Note each queen's age against your requeen threshold
Done when Every colony's current queen and any recent queen event has been read.
-
2
Google Sheets - update the queen history per hive
WebRun updates the per-hive queen history sheet. - Open the Queen History sheet
- Update each hive row with the current queen's introduction date, source, marking colour, and age
- Append a dated line to the history log for any requeen or supersedure this week
- Flag rows where the queen is older than your replacement threshold
Done when The sheet shows the live queen and full change history for every hive.
-
3
Slack - digest recent and overdue requeens
WebRun posts the weekly requeen digest to Slack. - Post a weekly digest to your beekeeping channel
- List each requeen and supersedure from the past week with the hive ID and queen source
- List colonies whose queen is now past the replacement age, oldest first
- Link to the Queen History sheet for the full record
Done when Your team has this week's requeen digest and overdue list in Slack.
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
Does it requeen or change anything in MyApiary?
No. WebRun only reads your queen records in MyApiary. It maintains the Google Sheet and posts the Slack digest, and never edits colony records or schedules any hive work on its own.
How does it decide a colony is overdue for a new queen?
It compares each queen's introduction date against the replacement age you set, for example two seasons. Any queen past that age is listed in the digest, oldest first, so you can plan requeening.
What if a queen was superseded rather than replaced by me?
Supersedures are read straight from MyApiary and logged as their own dated history line, marked as a supersedure rather than a manual requeen, so the record stays accurate.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.