Google Classroom integrations and automation

Teachers who automate Google Classroom usually want help with the chores around a course rather than the teaching itself: knowing who has not turned in an assignment, posting the week’s announcement on time, or keeping a gradebook spreadsheet aligned with what is in Classroom. The Classroom API models this as courses, which hold students, teachers, courseWork (assignments and questions), announcements and topics, and studentSubmissions, one per student per piece of coursework.

A submission’s state is the field to watch. It moves from NEW or CREATED to TURNED_IN when the student submits, to RETURNED when the teacher hands it back, and to RECLAIMED_BY_STUDENT if the student withdraws it. The late flag marks work turned in after the due date, and assignedGrade and draftGrade hold the teacher’s marks. Filtering studentSubmissions by state for one courseWork item gives a clean missing-work list without opening each student’s page.

Permissions are tighter than in most Google APIs. The connected account must be a teacher of the course, or a domain administrator, to read rosters and submissions, and each data type has its own scope, such as coursework for students, rosters and announcements. An important limit: grades and submission states can only be changed through the API on coursework that was created by the same Google Cloud project. Assignments a teacher made by hand in the Classroom interface can be read but not graded programmatically, so plan to create assignments through the workflow if you intend to write grades back.

Classroom can send push notifications for roster and coursework changes through Google Cloud Pub/Sub registrations, which require a Pub/Sub topic and expire after a week. For most class routines a daily or weekly schedule is simpler and matches the rhythm of school days.