Automated DataCamp Assignment Rollout
Every Monday, WebRun opens DataCamp, checks where your group is in the learning plan, stages the next track or course as an assignment with the due date you use, waits for your approval before creating it because creating it notifies every learner, then posts the rollout to Slack and messages the team lead on Telegram about anyone who has not opened last week's work.
How do I assign the next course to my whole team each week?
Every Monday WebRun opens DataCamp, checks where your group has reached in the learning plan, and stages the next track as an assignment with a due date. You approve it before it is created, then WebRun confirms every learner received it, posts the rollout to Slack, and flags anyone who has not opened it on Telegram.
- The next track is assigned on schedule with a due date every week
- Receipt is confirmed against the full group list, not assumed
- Learners who never opened last week are named before this week's deadline
Built for team leads · learning and development managers · data team managers · enablement 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.datacamp.comin a real browser with your saved login - no setup, no API keys. -
1
DataCamp - stage the next assignment
WebRun opens DataCamp to stage the next assignment. - Open DataCamp and check the group's progress against the learning plan
- Stage the next track or course as an assignment for the whole group with the due date you use, and leave it waiting for your approval because creating it notifies every learner
- Once approved, confirm every learner in the group received it and record who has already started
Done when The next assignment is approved, created and confirmed against the full group list.
-
2
Slack - post the rollout and who started
WebRun opens Slack to post the rollout and who started. - Post the assignment name, the due date and the number of learners it went to
- List who has already started and who has not opened it yet
- Add last week's completion rate so progress is visible week on week
Done when The team can see this week's rollout and its early progress in Slack.
-
3
Telegram - flag learners who have not opened it
WebRun opens Telegram to flag learners who have not opened it. - Message the team lead with anyone who never opened last week's assignment
- Include how many days are left before this week's due date
- Keep it internal. WebRun never messages a learner directly
Done when The team lead knows who is falling behind before the due date.
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 assign work to my team without asking?
No. The assignment is staged with its track, group and due date, and waits for your approval, because creating it sends a notification to every learner.
Does it message learners directly?
No. WebRun only posts internally to Slack and messages the team lead on Telegram. Any nudge to a learner is left for a person to send.
What if someone finished the track already?
They are recorded as complete and left out of the chase list. WebRun reads live progress each Monday rather than working from last week's copy.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.