Automated Code.org Section Setup Checks
Every Monday, WebRun opens the Code.org teacher dashboard, checks each section for an assigned course and joined students, notes the section code, drafts a Twilio reminder to the teachers with gaps for your approval, and posts the setup checklist to Microsoft Teams.
How do I check every Code.org class section is set up before term starts?
WebRun opens the Code.org teacher dashboard every Monday and checks each section for an assigned course and joined students, flagging any that are missing either. It drafts a Twilio reminder to the teachers involved for your approval and posts the setup checklist to Microsoft Teams before week one.
- Week one is spent teaching, not fixing setup
- Sections with no course or no students are named every Monday
- No teacher is texted until you release the draft
Built for teachers · school IT coordinators · curriculum leads · district administrators
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
code.orgin a real browser with your saved login - no setup, no API keys. -
1
Code.org - check sections and students
WebRun opens Code.org to check sections and students. - Sign in to Code.org and open the teacher dashboard
- List every section with its section code and the teacher who owns it
- Check whether each section has a course assigned and how many students have joined
- Flag sections with no course, no students, or fewer students than the roster expects
Done when Every section is listed with its course, its joined student count, and any gap named.
-
2
Twilio - draft the teacher reminder
WebRun opens Twilio to draft the teacher reminder. - Draft an SMS per teacher whose section is missing a course or students
- Name the section, the section code, and exactly what is missing
- Queue every message in Twilio unsent for approval
- Send nothing to a teacher until you release it
Done when A reminder is queued for each teacher with an incomplete section, waiting on approval.
-
3
Microsoft Teams - post the setup checklist
WebRun opens Microsoft Teams to post the setup checklist. - Post the setup checklist to your staff channel in Microsoft Teams
- Show sections ready to teach and sections still missing something
- Count how many students have joined against how many are expected
Done when This week's section setup checklist is in Microsoft Teams.
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 text teachers without me seeing it first?
No. Every reminder is queued in Twilio unsent and waits for you to release it, so no teacher is messaged about their section without your approval.
Does it create sections or assign courses itself?
No. WebRun only reads the teacher dashboard. Creating a section, assigning a course, or adding a student stays a teacher action inside Code.org.
Does it report on individual students?
It counts how many students have joined each section and compares that to the expected roster size. It does not report a named student's work or progress.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.