Automated Farm360 Mortality Digest
Every morning, WebRun opens Innovasea Farm360, reads yesterday's recorded mortalities and causes for each cage, logs the counts to a Google Sheets tracker so the trend builds, and posts a short mortality digest to Slack with any cage above its normal daily rate flagged.
How do I get a daily mortality digest across every cage?
Every morning, WebRun opens Innovasea Farm360 and reads yesterday's recorded mortalities and causes for each cage. It logs the counts to a Google Sheets tracker so the trend builds, then posts a Slack digest flagging any cage above its normal daily rate, so a health problem surfaces the next morning instead of days later.
- Mortality spikes surface the next morning, not days later
- Every cage's losses are trended against its own normal rate
- A dated mortality history builds so health problems are traceable
Built for fish farms · aquaculture health managers · site managers · fish health 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.innovasea.comin a real browser with your saved login - no setup, no API keys. -
1
Innovasea Farm360 - read mortality records
innovasea.com
WebRun opens Innovasea Farm360 to read mortality records. - Open Farm360 and go to yesterday's mortality records
- Read the mortality count and recorded cause per cage
- Capture the count and cause for every active cage
Done when Yesterday's mortality count and cause are captured for every cage.
-
2
Google Sheets - log counts and causes
google.com
WebRun opens Google Sheets to log counts and causes. - Open the mortality tracker sheet
- Append a dated row per cage with the count, cause, and cumulative losses
- Compute each cage's rolling average so a spike above normal stands out
Done when Yesterday's mortalities are logged and each cage's rolling rate is updated.
-
3
Slack - post the mortality digest
slack.com
WebRun opens Slack to post the mortality digest. - Post an internal digest of yesterday's mortalities by cage
- Flag any cage above its rolling average with the count and cause
- Keep it internal to the farm team, no external contact
Done when The team has yesterday's mortality digest 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
How does it know a mortality spike is unusual?
It compares yesterday's count against each cage's own rolling average from the Google Sheets history. Any cage above its normal daily rate is flagged with the count and the recorded cause.
Does it report mortalities to anyone outside?
No. WebRun logs the counts to Google Sheets and posts an internal Slack digest for the farm team. It never reports figures to a regulator, buyer, or vet on its own.
Where do the counts and causes come from?
Straight from Farm360's mortality records. WebRun reads the count and cause your team already logged for each cage and never invents or reclassifies a cause.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.