Skip to content

Automation · Operations and reporting

Answer who did not turn in an assignment, without opening Google Classroom

How an AI agent answers which students did not turn in a Google Classroom assignment, by name, and leaves the follow up on record.

How do I know who did not turn in an assignment without going course by course in Classroom?

The teacher asks about their course and the Met answers: how many turned it in, how many were late, how many already have a grade, and who did not turn it in, by name. A single tool does the cross between the course roster and the submissions, so the answer arrives in one message rather than in a spreadsheet built by hand. Everything is read only: the Met does not grade, does not create assignments and does not post announcements, because Meteor does not request Classroom's write permissions. It does not request the student email permission either, so it returns names and not addresses. That limit is deliberate, not a pending stage.

What starts it

When the customer writes

It starts when the teacher writes. There is no automation to configure: it is the Met assigned to the channel answering a question that today is answered by hand, looking at two screens and comparing names.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Met for academic support

It is an internal Met for the school or university: it works for the teacher and for coordination, not for families. The question it settles gets asked twenty times a week and today it costs opening Classroom, entering the course, entering the assignment and comparing against the roster.

Channels: WhatsApp · Website chat

What you need connected

6 steps · 11 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Locate the course being asked about

    The listing returns the courses the connected account can see and by default brings only the active ones, which is almost always what you want: last year's archived courses muddy any answer. It can be narrowed to courses where the account is a teacher. The detail adds section, subject, room and the direct Classroom link, for when somebody does want to open it.

  2. 2

    Find the assignment and its due date

    The assignment listing brings the published ones, with their due date, their maximum points and their link. One detail matters more than it looks: the date arrives in universal time, and the Met converts it to the workspace timezone before saying it out loud. A task due at eleven at night turns into one due the next day if nobody does that conversion.

  3. 3

    Answer who is missing in one go

    The summary crosses the course roster with the submissions and returns, in one call, how many turned it in, how many were late, how many already have a grade and who did not turn it in, by name. This is the step that justifies the automation: without it the Met would have to fetch the submissions, fetch the roster and match identifiers against names by hand, which is exactly what the teacher does today.

  4. 4

    Go into detail when the question is about one person

    And what about Camila needs something else: the submission listing returns the state of each one, whether it was late, the assigned grade and the draft one, and it accepts pulling every assignment in the course at once. Since it returns identifiers rather than names, the student roster is what puts names to them. The email comes back empty on purpose, and no setting changes that.

  5. 5

    Leave the follow up where it does not get lost

    A list of missing students that gets read and forgotten changed nothing. The Met leaves the note with the assignment, the date and the counts on the course or student record inside the CRM, and schedules the reminder to look again after the cutoff. That way Monday's conversation can be compared with Friday's instead of starting from scratch.

  6. 6

    Know who to escalate to inside the institution

    When a missing assignment stops being an oversight and becomes a case, somebody has to be told. The course teacher listing says who else teaches it, the announcement board shows what was communicated to the group and when, and the CRM contact search locates the homeroom teacher or the coordinator who applies. The Met assembles the case; who it escalates to is the institution's call.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

The named summary works per assignment, which is how the question actually gets asked: who did not hand in this week's exercise. For a wider look, the submission listing accepts pulling every assignment in the course at once, though there it returns identifiers and they have to be matched against the roster.

Yes, and there the minors' data limit usually does not apply. The automation is the same: courses, assignments, submissions and the summary of who is missing. What changes is how carefully you have to treat where that list goes.

Because Meteor does not request Classroom's email permission. It is a decision written into the connector: without it Google's interface returns a name and an identifier, which is enough to know who did not turn something in and not enough to build a contact list of minors.

The Classroom tools will fail with a permissions error until somebody connects the account again from Integrations. The rest of Google Workspace keeps working with what was already authorized: these are new permissions added on top, not a change to the earlier ones.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.