Keep workday sessions visible with a recurring check
A consistent workday session check can reduce the effort of remembering to look up commitments before switching into delivery mode.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Organisation Session List
Tool to list sessions of an organisation. use after you have the organisation id to fetch paginated session records.
Why this helps
Founders can lose time repeatedly checking whether a session is coming up while juggling delivery and operations.
- Provides a regular view of scheduled sessions on working days.
- Helps the founder orient before client delivery.
- Reduces repeated manual schedule checks.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lessonspace to Notis once in the portal.
- 2Create an automation or ask Notis to retrieve the Lessonspace session list for a workday check.
- 3Choose a recurring weekday schedule and select a channel for run reports.
- 4Test one run on a workday and confirm the schedule information is useful.
Questions about this workflow
Can I choose which workdays it runs?
Set the recurring schedule to the workdays and times that suit your routine.
Does it open a room automatically?
No. This action retrieves session records. A separate workflow using Launch Space can open a known room.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lessonspace. A trigger fires from one place; an action lands in another.
Notion triggers
Lessonspace actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Demo Space
Tool to create a transient demo space for embedding in an iframe. use when you need a temporary environment to test lessonspace features.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Organisation Details
Tool to retrieve organisation details, including id, plan, and usage stats. use after authenticating with your organisation token.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Organisation Session List
Tool to list sessions of an organisation. use after you have the organisation id to fetch paginated session records.
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.
Launch Space
Tool to launch a lessonspace space. use after determining user id, role, and space id.
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 Lessonspace, 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 Lessonspace.