Check a workflow configuration when a concern is raised
A comment can flag a changed source or unexpected extraction. Let Notis retrieve the Kadoa configuration so you can investigate without hunting for the workflow details.
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
Fetch workflow configuration
Tool to fetch an advanced workflow’s configuration details. Use when you have a workflow ID and need its steps and metadata.
Why this helps
A concern buried in a comment can be hard to follow up on when configuration details live in another tool.
- Make it easier to investigate a concern while its context is fresh.
- Reduce the time spent finding configuration details.
- Keep the discussion and workflow review connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kadoa to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to fetch Kadoa configuration when a Notion comment requests a workflow review.
- 3Describe in one plain-language instruction how to recognize a review request and identify the workflow to inspect.
- 4Pick Comment Created, choose a channel for run reports, and test with one real review comment.
Questions about this workflow
Does every comment need to trigger this?
Use the instruction to identify comments that request a workflow review and configure the trigger scope appropriately.
What does the configuration lookup provide?
Kadoa returns advanced workflow configuration details for the workflow Notis identifies.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kadoa. A trigger fires from one place; an action lands in another.
Notion triggers
Kadoa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Notification Channel
Tool to create a notification channel for alerts delivery.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Enable Data Validation
Tool to enable data validation on a specified workflow. Use after creating or updating a workflow to enforce its validation rules.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fetch workflow configuration
Tool to fetch an advanced workflow’s configuration details. Use when you have a workflow ID and need its steps and metadata.
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 locations
Tool to retrieve a list of all available locations. Use when you need to know supported locations before performing location-dependent operations. Use after authenticating with your API key.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Crawled Page Content
Tool to retrieve content of a crawled page. Use when you need the HTML or Markdown of a page from a specific crawling session.
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.
Get Crawled Pages
Tool to list pages crawled during a session. Use when you need to paginate through results after starting a crawl session.
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.
Get Crawl Status
Tool to fetch current status of a crawling session. Use when you need to check progress of a crawl by its session 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 Notification Event Types
Tool to retrieve supported notification event types. Use when you need to enumerate available notification triggers.
Connect any two apps with Notis in the middle.
Notion and Kadoa, 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 Kadoa.