Follow through when assessment access is revoked
Keep access administration aligned with the decision recorded in Notion.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Delete Access List Item
Tool to delete one or more codes from an access list. Use after confirming the list exists.
Why this helps
Revocation details can be logged correctly but left active in the assessment system if someone forgets the follow-up.
- Reduce the gap between a recorded decision and access cleanup.
- Keep access lists closer to the current enrollment state.
- Make a sensitive follow-up more reliable.
Setup
Build it in a few focused steps.
- 1Connect Notion and ClassMarker to Notis once in the portal.
- 2Write a prompt asking Notis to remove the identified code from the correct ClassMarker access list when a Notion access record is marked revoked.
- 3Pick Notion's Page Properties Updated trigger and choose a report channel.
- 4Test with one authorized revocation record and verify the code is removed from the intended list.
Questions about this workflow
What information does the action need?
The relevant access list and code must be identifiable from the Notion record or connected context.
How can I prevent removal on unrelated updates?
State that removal should occur only when the record's status is explicitly revoked.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Classmarker. A trigger fires from one place; an action lands in another.
Notion triggers
Classmarker actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Access List Item
Tool to add one or more access codes to an access list. Use after obtaining a valid access_list_id to grant exam access.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new question category
Tool to create a new question category. Use after confirming the parent category ID.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Group
Tool to create a new group. Use when you need to organize users into a specific group after planning your user structure.
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.
Create Question
Tool to create a new question with specified text, type, and category. Use after finalizing details. Set verify_only=True to validate without creating.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create ClassMarker User
Tool to create a new user in ClassMarker. Use after gathering user details to provision accounts. Provide user info and optional group assignments. Returns the complete API response.
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.
Delete Access List Item
Tool to delete one or more codes from an access list. Use after confirming the list exists.
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.
Delete API Key
Tool to delete an API key by its ID. Use when you need to revoke an API key immediately.
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 Group
Tool to delete a group by its ID. Use when you need to remove a group from ClassMarker.
Connect any two apps with Notis in the middle.
Notion and Classmarker, 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 Classmarker.