Give changed risks a quick outside signal scan
Add a focused community check when a risk record changes status or priority.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Search Hackernews Posts
Get relevant posts from hacker news based on a full-text query and optional filters. results can be limited using the size parameter.
Why this helps
Risk tracking can become stale when updates depend on someone remembering to search for new signals.
- Pair a risk update with a focused scan of public discussion.
- Make emerging concerns easier to notice.
- Avoid routine manual searches for every tracked risk.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hacker News to Notis once in the portal.
- 2Create an automation in the portal or tell Notis what outcome you need in plain language.
- 3Ask Notis in one instruction to search Hacker News for discussion related to an updated risk record and summarize notable signals; choose Page Properties Updated and a report channel.
- 4Change one real risk record and review its report.
Questions about this workflow
Can this track every property change in a database?
Yes, if you select the matching data source when choosing the Page Properties Updated trigger.
Can I restrict it to priority changes?
Describe that condition in the prompt; Notis can use the event details to decide whether to proceed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hackernews. A trigger fires from one place; an action lands in another.
Notion triggers
Hackernews actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Hackernews Frontpage
Get the frontpage posts of hacker news.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Hackernews Item
Get a specific item from hacker news using its id. limits response size to prevent context overflow.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Latest Hackernews Posts
Get the latest posts from hacker news based on optional filters. results can be limited using the size parameter.
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 Hackernews Today Posts
Get today's posts from hacker news.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Hackernews User
Get a specific user from hacker news using their username.
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.
Search Hackernews Posts
Get relevant posts from hacker news based on a full-text query and optional filters. results can be limited using the size parameter.
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 Hackernews, 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 Hackernews.