Make new Notion project pages easy to find
A new page can start with a useful trail back to the active work.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Add a comment to a card
Tool to add a comment to a Kanbanize card. Use when you need to add notes, updates, or any text-based information to an existing card.
Why this helps
New planning pages can be disconnected from the board where delivery is tracked.
- Connects planning pages with delivery context.
- Reduces searching across workspace pages.
- Adds a link for future reference.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kanbanize to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Ask Notis with one plain-language instruction to add a concise page summary and link to the matching card when the match is clear.
- 4Select the Notion Page Created trigger scoped to the project hub and set a run-report channel.
- 5Test with one real subpage and verify the link points to the right card context.
Questions about this workflow
Does this create a new Kanbanize card?
No. It comments on a matching existing card.
Can it work for any workspace page?
Scope the Notion trigger to the project hub or its data source to keep unrelated page activity out.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kanbanize. A trigger fires from one place; an action lands in another.
Notion triggers
Kanbanize actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a comment to a card
Tool to add a comment to a Kanbanize card. Use when you need to add notes, updates, or any text-based information to an existing card.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Board Milestone
Tool to check if a milestone is available on the specified board. Use when you need to verify milestone existence on a specific board. Returns True if the milestone is available (HTTP 204), False if not found (HTTP 404).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Check User Is Card Watcher
Tool to check if a user is a watcher of a specific card. Use when you need to verify if a user is watching a card.
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.
Delete Board
Tool to delete a board by its ID. Use when you need to permanently remove a board from Kanbanize. Note: The board must be archived before deletion.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Card
Tool to delete a card from the Kanbanize board. Use when you need to permanently remove a card and all its associated data from the board.
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 Tag
Tool to delete a tag from Kanbanize. Use when removing a tag and optionally replacing it with another tag for all affected cards.
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 Workflow
Tool to delete a workflow for the specified board. Use when you need to permanently remove a workflow from a board.
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 Board Block Reasons
Tool to get a list of block reasons available on a board. Use when you need to retrieve available block reasons for a specific board.
Connect any two apps with Notis in the middle.
Notion and Kanbanize, 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 Kanbanize.