Turn training page activity into a progress check
When training work moves in Notion, pull the related Coassemble progress into the run report.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Get Trackings
Tool to retrieve tracking objects with filters. use when you need to fetch learner progress data filtered by course id, date range, identifier, or completion status.
Why this helps
Training signals can get buried in workspace activity while the founder is focused on the next task.
- Use existing workspace activity as a prompt to review progress.
- Reduce the need to remember a separate check.
- Keep a brief summary available for follow-up planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Coassemble to Notis once through the portal.
- 2Create the automation in the portal or tell Notis conversationally.
- 3Write one instruction asking Notis to check Coassemble tracking when a changed Notion page is relevant to training and summarize the useful progress context.
- 4Select the Notion All Page Events trigger and choose where reports should appear.
- 5Test with one real training-related page change.
Questions about this workflow
Will this run for unrelated page updates too?
The trigger covers all page events, so the instruction should clearly tell Notis how to recognize relevant training context.
Can this be used for high-volume workspaces?
Because the trigger is broad, use it where the event volume and report frequency remain useful for your workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Coassemble. A trigger fires from one place; an action lands in another.
Notion triggers
Coassemble actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Clients
Tool to retrieve a paginated list of clients. use when you need to browse or process organisation records sequentially.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Courses
Tool to retrieve all courses with optional filters and pagination. use when you need to list courses after setting identifier and client identifier, and control page size and number.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Trackings
Tool to retrieve tracking objects with filters. use when you need to fetch learner progress data filtered by course id, date range, identifier, or completion status.
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 Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Coassemble, 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 Coassemble.