Make new risks visible early
Notis can carry a newly flagged risk from a Notion tracker into Teams with the likely impact and a link for a quick response.
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
Post message to Teams channel
Posts a new text or html message to a specified channel in a microsoft teams team.
Why this helps
Risks can be documented in a tracker without prompting the team to adjust plans or offer help.
- Surface new risks early enough for a response.
- Give the team the risk and its source in one place.
- Encourage action without manual escalation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Microsoft Teams to Notis once.
- 2Create an automation in the portal or by asking Notis conversationally.
- 3Tell Notis to detect newly flagged risks and post the risk, possible impact, and page link in the appropriate Teams channel.
- 4Select Page Properties Updated for the risk data source and choose a channel for run reports.
- 5Flag one real test risk and verify the channel post.
Questions about this workflow
Can it avoid reposting an existing risk?
Ask Notis to act when a risk is newly flagged or materially changed, not on unrelated property updates.
What should a useful escalation contain?
Request a short risk summary, likely impact, suggested owner or next step, and a Notion link.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Microsoft teams. A trigger fires from one place; an action lands in another.
Notion triggers
Microsoft teams actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add member to team
Tool to add a user to a microsoft teams team. use when granting or updating membership for a user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Teams team
Tool to archive a microsoft teams team. use after confirming the team id; returns 202 if accepted.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get all chats
Retrieves all microsoft teams chats a specified user is part of, supporting filtering, property selection, and pagination.
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 all chat messages
Retrieves all messages from a specified microsoft teams chat using the microsoft graph api, automatically handling pagination; ensure `chat id` is valid and odata expressions in `filter` or `select` are correct.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create online meeting
Use to schedule a new standalone microsoft teams online meeting, i.e., one not linked to any calendar event.
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.
Create Team
Tool to create a new microsoft teams team. use when you need to provision a team with optional template, channels, and members.
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 Teams team
Tool to delete a microsoft teams team. use after confirming the target team id.
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.
Get team channel
Tool to get a specific channel in a team. use after obtaining valid team and channel ids to fetch channel details.
Connect any two apps with Notis in the middle.
Notion and Microsoft teams, 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 Microsoft teams.