Check Classroom submissions on a steady schedule
Have Notis check selected coursework on a recurring schedule so you do not have to remember to revisit each item.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Student Submissions
Tool to list student submissions for a specific coursework. use when you need to fetch or paginate student submissions by course and coursework, optionally filtering by user, state, or timeliness.
Why this helps
Submission follow-up depends on remembering to check multiple coursework items at the right time.
- Create a predictable moment for submission review.
- Surface missing or late work for follow-up.
- Reduce repeated manual checks across courses.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Classroom to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to review submissions for selected coursework on a schedule.
- 3Describe which coursework to inspect and what submission states to report in one plain-language instruction.
- 4Choose a recurring Notis schedule, select a run-report channel, and test with one real coursework item.
Questions about this workflow
Can it check more than one coursework item?
Describe the coursework scope in your instruction and verify the results with a real example.
Does it change student submissions?
This action lists submissions for review; it does not change their state.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Classroom. A trigger fires from one place; an action lands in another.
Notion triggers
Google Classroom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List CourseWorkMaterials
Tool to list courseworkmaterials in a course. use after confirming a valid courseid; supports pagination and ordering.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Announcement
Tool to create an announcement in a course. use after confirming the course id is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Announcement
Tool to delete an announcement. use after confirming the announcement id.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get Announcement
Tool to get an announcement. use when you need to fetch an announcement by course and announcement id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Announcements
Tool to list announcements in a course. use after you have the course id to page through announcements.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Patch Announcement
Tool to update fields of an announcement. use when you need to modify specific details of an existing announcement after confirming which fields to update.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Create Course
Tool to create a new course. use when a teacher needs to establish a classroom course before enrollment.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Delete Course
Tool to delete a course. use when you need to remove a course after confirming the course id.
Connect any two apps with Notis in the middle.
Notion and Google Classroom, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google Classroom.