Automated Environmental Lab Result Routing
When a lab-result email arrives in Gmail, WebRun reads the sample IDs and analyte data, looks up the matching project and sampling event in Locus Technologies, and sends the responsible consultant a Slack notification with the result summary and a direct link to the project record for their review.
How do I automatically route incoming environmental lab results to the right consultant?
When a lab-result email arrives in Gmail, WebRun reads the sample IDs and analyte data, looks up the matching project and consultant in Locus Technologies, and sends the responsible consultant a Slack notification with the result summary and any exceedance flags. The consultant then reviews and responds. No results reach the client without human review.
- Lab results reach the responsible consultant within minutes of the email arriving
- Analyte exceedances are flagged automatically against project action levels in Locus
- No result sits in a shared inbox unassigned while a project deadline approaches
Built for environmental data managers · remediation project managers · EHS analytical chemists · environmental consulting project 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
gmail.comin a real browser with your saved login - no setup, no API keys. -
1
Gmail - read incoming lab-result email
gmail.com
WebRun opens Gmail to read incoming lab-result email. - Monitor Gmail for emails from registered analytical laboratories
- Extract sample IDs, analyte names, detected concentrations, and reporting limits from the email or attachment summary
- Note the laboratory name, report date, and any flagged exceedances
Done when Sample IDs, analytes, and result flags are extracted from the lab email.
-
2
Locus Technologies - match sample IDs to project records
locustec.com
WebRun opens Locus Technologies to match sample IDs to project records. - Search Locus Technologies for the project and sampling event matching the received sample IDs
- Identify the responsible project manager and the client associated with the sampling event
- Note any action levels stored in Locus for the detected analytes to flag exceedances
Done when The lab results are matched to the correct project record and responsible consultant.
-
3
Slack - notify responsible consultant
slack.com
WebRun opens Slack to notify responsible consultant. - Send the responsible consultant a Slack notification summarising the lab results received
- Flag any detected concentrations that exceed action levels stored in Locus Technologies
- Include the project name, sampling event date, and a direct link to the Locus project record
Done when The consultant has a result summary in Slack and can open the Locus record to review and respond.
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 send lab results to the client automatically?
No. WebRun only notifies the responsible consultant internally via Slack. Any communication of results to the client is made by the consultant after their own review and interpretation.
What if the sample IDs do not match any project in Locus Technologies?
It flags the unmatched results in a Slack alert to the data manager so the project record can be checked or the sample ID corrected before the results are filed.
How does it know which concentrations are exceedances?
It compares detected concentrations against the action levels stored in the Locus Technologies project record for that site and analyte. Keep your Locus action levels current for accurate flagging.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.