Keep training requesters posted on their project
Every morning, WebRun opens Cognota, finds requests whose project stage changed since the last run, and drafts a clear, jargon-free status update email in Gmail for the original requester, explaining what moved and what happens next, leaving each message unsent for you to approve.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep training requesters updated on their project status?
WebRun watches Cognota each morning for projects that advanced a stage and drafts a plain-language update email in Gmail for the original requester, explaining what moved and what happens next. It skips internal-only changes and leaves every message unsent for your approval, so stakeholders stay informed without you writing each note by hand.
- Requesters hear about real progress instead of chasing you for it
- Every update waits as a draft for your approval before it sends
- Trivial internal stage moves never reach a stakeholder's inbox
Built for L&D managers · training coordinators · learning business partners · instructional design 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
app.cognota.comin a real browser with your saved login - no setup, no API keys. -
1
Cognota - detect project stage changes
WebRun opens Cognota to detect project stage changes. - Open Cognota and list projects whose stage changed since the last run
- For each, read the old stage, the new stage, and the linked original requester
- Capture the requester name and email and the expected next step
- Skip internal-only stage moves that a requester does not need to hear about
Done when Every requester-relevant stage change is listed with the requester and next step.
-
2
Gmail - draft requester status updates
WebRun opens Gmail to draft requester status updates. - Draft a plain-language update email in Gmail to the requester
- State what moved, in words a non-L&D stakeholder understands, and what happens next
- Give a realistic next-step date and invite any questions
- Save the message as a Gmail draft and leave it unsent for you to review and send
Done when A status update is drafted in Gmail for each requester whose project advanced, awaiting your approval.
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 email requesters without me?
No. Every status update is saved as a Gmail draft and left unsent. You review each one and send it yourself, so no stakeholder hears from you on a change you have not approved.
Will requesters get a note for every tiny change?
No. It skips internal-only stage moves and drafts an update only when the change is one a requester would actually care about, so people are kept informed without being flooded.
How does it know who the requester is?
It reads the original requester linked to each project in Cognota, so the update goes to the person who asked for the training, addressed by name from their intake record.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.