Give questions in Notion a research starting point
A comment can become a prompt for focused web research, ready for the next decision or discussion.
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
Web Search
Search the web and optionally scrape each result to Markdown in one call.
Why this helps
Questions buried in comments can remain unanswered when nobody has time to switch context and investigate.
- Give research questions a clear next step.
- Bring source material back to the conversation context.
- Reduce the number of comments that need manual follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Context.dev to Notis once in the portal.
- 2Create an automation through the portal or by asking Notis in plain language.
- 3Use one instruction asking Notis to interpret a new comment in page context and search the web for relevant evidence.
- 4Pick Comment Created as the trigger and select a channel for run reports.
- 5Test with a real comment containing a question you can verify.
Questions about this workflow
Does this trigger require special Notion access?
Yes. The Notion integration needs the Read comments capability, and an existing connection may need to be re-authorized after enabling it.
Can I limit the workflow to a page?
The Comment Created trigger supports an optional page filter when setting up the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Context.dev. A trigger fires from one place; an action lands in another.
Notion triggers
Context.dev actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Extract Structured Data
Crawl a website and return JSON matching a caller-supplied JSON Schema.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve Brand
Resolve a company by domain, name, or ticker into a full brand profile.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Identify Transaction
Map a noisy card or bank descriptor to the real merchant and its brand data.
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.
Scrape Images
Extract every image asset from a page with metadata.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Web Search
Search the web and optionally scrape each result to Markdown in one call.
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.
Extract Styleguide
Extract a website's design system: colors, typography, spacing, shadows, and UI components.
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 Context.dev, 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 Context.dev.