Google Classroom

Files and knowledge

Google Classroom for AI agents. Managed auth, ready-made tools.

List classes and students, post announcements, create assignments and review submissions in Google Classroom on behalf of each of your users.

About Google Classroom

With the Google Classroom connector, your agent works in each user’s own Google Classroom. It can list classes and students, post announcements, create assignments and check student submissions, using only the tools your project allows.

Google Classroom is Google’s tool for teachers to manage classes, assignments and grades.

Tools

What your agent can do in Google Classroom.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Classroom connection.

  • List courses

    Read
    google_classroom_list_courses

    List the classes the user teaches or attends.

  • List students

    Read
    google_classroom_list_students

    List the students in a class.

  • List coursework

    Read
    google_classroom_list_coursework

    List the assignments and questions in a class.

  • Create an assignment

    Write
    google_classroom_create_coursework

    Create an assignment with a title, instructions and due date.

  • List submissions

    Read
    google_classroom_list_submissions

    List student submissions for an assignment and their state.

  • Post an announcement

    Write
    google_classroom_create_announcement

    Post an announcement to a class stream.

Control

Limits you can set.

You decide what your agent may do in Google Classroom, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read classes and submissions, and switch off google_classroom_create_announcement so it can never post to a class stream.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example coursework but not rosters. A call outside them is refused.

Get started

Connect Google Classroom
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Google Classroom

    Each end user authorizes their own Google Classroom account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Google Classroom account, once.
    const connection = await agent200
      .user("user_123")
      .connect("google_classroom");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Google Classroom tools

    Name the user, the model and the tools. The model decides which Google Classroom tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Who has not turned in the essay assignment yet",
        tools: ["google_classroom"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Google's own sign-in page. You never see or store their Google password.

  • What access is requested

    The scopes the connection needs, such as viewing classes, managing coursework or viewing rosters, listed on Google's authorization screen. Users can remove the app later from their Google Account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Classroom connector and how to use it.

Agent brief
Connector: Google Classroom, through Agent200. In code: "google_classroom".
What it does: List classes and students, post announcements, create assignments and review submissions in Google Classroom on behalf of each of your users.
Page: https://www.agent200.com/connectors/google-classroom/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Google Classroom's own page, through the authorization link Agent200 returns. Never ask a user for a Google Classroom password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: google_classroom_list_courses, google_classroom_list_students, google_classroom_list_coursework, google_classroom_list_submissions. Write tools: google_classroom_create_coursework, google_classroom_create_announcement. Name "google_classroom" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/google-classroom/framework/claude/
   https://www.agent200.com/connectors/google-classroom/framework/chatgpt/
   https://www.agent200.com/connectors/google-classroom/framework/claude-code/
   https://www.agent200.com/connectors/google-classroom/framework/muse/
   https://www.agent200.com/connectors/google-classroom/framework/grok-bot/
   https://www.agent200.com/connectors/google-classroom/framework/openai-dots/
   https://www.agent200.com/connectors/google-classroom/framework/claude-duet/
   https://www.agent200.com/connectors/google-classroom/framework/hermes-agent/
   https://www.agent200.com/connectors/google-classroom/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/google-classroom.md

Guides

Use Google Classroom with the AI you build on.

Step-by-step setup for Google Classroom with a specific model, assistant or agent framework.

FAQ

Google Classroom and Agent200, answered.

Who handles the Google Classroom OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Classroom.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Classroom connection, never another user's. It cannot reach anything the user or Google Classroom has not authorized.

Can I limit what my agent can do in Google Classroom?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with Google Classroom.
Your agent does the rest.

Your users connect their own Google Classroom accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)