Route crop scouting issues to the right person the moment they are logged
Every hour, WebRun checks Agrivi for newly logged crop scouting issues, reads the field, crop, severity, and pest or disease type, looks up the responsible agronomist in Google Sheets, and routes a Slack alert to the right advisor so critical issues are never left sitting unread.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically route crop scouting issues to the right agronomist?
Every hour, WebRun checks Agrivi for new scouting issues, reads field, crop, severity, and issue type, looks up the responsible agronomist in Google Sheets, and posts a tagged Slack alert with full context. Critical issues are flagged first so advisors can respond within the hour.
- Critical scouting issues reach the right advisor within the hour
- No scouting report sits unread overnight
- Field, crop, and severity context in every alert so advisors can prioritize immediately
Built for crop advisors · row-crop farm managers · produce growers · precision ag 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
agrivi.comin a real browser with your saved login - no setup, no API keys. -
1
Agrivi - read newly logged scouting issues
WebRun opens Agrivi to read newly logged scouting issues. - Open Agrivi and navigate to the scouting or field monitoring section
- Read any scouting issues logged since the last check
- Capture field name, crop, issue type (pest, disease, nutrient, or other), severity level, and any photo or notes attached
Done when All scouting issues logged since the last run are captured with field, crop, severity, and issue type.
-
2
Google Sheets - look up responsible agronomist for each field
WebRun opens Google Sheets to look up responsible agronomist for each field. - Open the agronomist routing sheet
- Look up the responsible agronomist or crop advisor for each affected field based on crop type and field assignment
- Note the appropriate Slack username for each advisor
Done when The responsible advisor and Slack username are identified for each new scouting issue.
-
3
Slack - route alert to the right advisor
WebRun opens Slack to route alert to the right advisor. - Post an alert in the crop scouting Slack channel for each new issue
- Tag the responsible agronomist directly so they receive a notification
- Include field name, crop, severity, issue type, and a link to the scouting record in Agrivi
- Flag critical-severity issues with a priority marker at the top of the message
Done when Each new scouting issue is routed to the right advisor in Slack with full field context.
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 recommend a treatment or spray product automatically?
No. WebRun routes the issue alert to the right advisor and includes the scouting details. Treatment decisions remain with your agronomist or crop advisor.
How does it know which advisor is responsible for which field?
You map each field and crop type to an advisor and Slack username in the Google Sheet routing table. Update the table as advisor assignments change.
What if the same issue has already been routed in a previous run?
WebRun tracks which scouting issue IDs it has already alerted on. Issues logged before the last run are skipped so advisors do not receive repeat notifications.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.