Capture Notion comment follow-ups in Monday
Give actionable comments a home in Monday, where the team can see and move the next step forward.
Trigger
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.
Action
Create item
Creates a new item on a monday.com board, optionally assigning it to a group and setting column values.
Why this helps
Useful decisions and requests can stay buried in a page discussion instead of becoming trackable work.
- Makes comment-driven work visible on the team's board.
- Reduces the need to revisit page discussions to find open requests.
- Creates a clear place to continue follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Monday to Notis once in the portal.
- 2Ask Notis to create a Monday follow-up item when a new Notion comment contains an actionable request.
- 3Select the Notion Comment Created trigger, choose a channel for run reports, and create the automation.
- 4Add one real actionable comment and check that the follow-up appears in Monday.
Questions about this workflow
Will every comment create a follow-up?
The trigger fires for new comments in the integration's accessible workspace. State in your instruction that only actionable requests should become Monday items.
Does Notion need comment access?
Yes. The Notion integration needs the Read comments capability, and an older connection may need to be re-authorized after enabling it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Monday. A trigger fires from one place; an action lands in another.
Notion triggers
Monday actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add users to board
Adds users to a monday.com board with a specified role.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive board
Archives a specified, existing, and unarchived board in monday.com; archived boards can typically be restored later.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Archive item
Archives an existing monday.com item, moving it from active board views to the archive where it can be potentially restored.
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.
Change simple column value
Changes a specific column's value for a monday.com item using a simple string, suitable for text, status, or dropdown columns; can create new labels if `create labels if missing` is true for status/dropdown columns.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create a Monday board
Creates a monday.com board; `template id` if used must be accessible, and `folder id` must be in `workspace id` if both are provided.
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 column
Creates a new column with a specified type and title on a monday.com board.
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 group
Creates a new group with the given `group name` on an existing monday.com board, identified by its `board 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.
Create item
Creates a new item on a monday.com board, optionally assigning it to a group and setting column values.
Connect any two apps with Notis in the middle.
Notion and Monday, 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 Monday.