Check for new coverage as an incident develops
Incident notes often change as new information arrives. Use a page update to prompt a headline scan for relevant reporting.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Search News Headlines
Search global news and return headlines only, without article text.
Why this helps
Following an incident can pull attention into repeated manual searches while other work waits.
- Check for related headlines when incident notes are updated.
- Get a quick signal without reading full articles first.
- Keep news follow-up alongside the incident record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Opoint to Notis once in the portal.
- 2Create an automation with a plain-language instruction to search Opoint headlines for reporting related to the incident page when it changes.
- 3Select the Notion Page Updated trigger for the incident page and choose a report channel.
- 4Update a test incident note and review the headline scan.
Questions about this workflow
Will small changes also trigger a search?
The Page Updated trigger fires when a block within the specified page is updated. Use the prompt to describe when the incident context warrants a search.
Can this retrieve an article after I find a useful headline?
Yes. A separate workflow using Fetch Articles by Id can retrieve specific articles when you have their site and article IDs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Opoint. A trigger fires from one place; an action lands in another.
Notion triggers
Opoint actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Fetch Articles by Id
Fetch specific articles by their site and article id pairs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search News with Filters
Search news with structured expression lines and typed filter ids.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Resolve Filter Ids
Translate a country, site, language, or media name into a search filter id.
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.
Search News Headlines
Search global news and return headlines only, without article text.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search News
Search global news by keyword, phrase, or boolean query with filters.
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.
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 Opoint, 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 Opoint.