Keep evolving research tied to current evidence
When your notes change, the question may change too. Ask Linkup to revisit the page's central question and bring back current sources.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get Natural Language Answer
This tool gets a natural language answer to a given question using linkup's api. it processes the question with provided parameters (query and depth) and returns a structured answer with text and sources used. it supports varying precision based on defined depth and is designed for natural language query responses.
Why this helps
Research notes can evolve while the sources and conclusions stay frozen.
- Revisit a question when new notes change its direction.
- Bring current web sources into ongoing research.
- See a concise answer without restarting the search manually.
Setup
Build it in a few focused steps.
- 1Connect Notion and Linkup to Notis once through the portal.
- 2Start an automation in the portal or tell Notis in plain language what should happen after a research page changes.
- 3In one instruction, ask Linkup to answer the page's main question using current sources and summarize findings relevant to the updated notes.
- 4Choose Page Content Updated scoped to a research page or database, set a report channel, and test with a real content edit.
Questions about this workflow
Will it monitor every page?
You can scope Page Content Updated to one page, a data source, or a parent page, or leave it workspace-wide if appropriate.
Can I see where the answer came from?
Yes. Get Natural Language Answer returns a structured answer with sources used.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Linkup. A trigger fires from one place; an action lands in another.
Notion triggers
Linkup actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Natural Language Answer
This tool gets a natural language answer to a given question using linkup's api. it processes the question with provided parameters (query and depth) and returns a structured answer with text and sources used. it supports varying precision based on defined depth and is designed for natural language query responses.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Linkup
This tool allows users to search and retrieve insights using the linkup api. it implements a search functionality via the post /search endpoint and supports various parameters including 'query', 'depth', and 'output type' (with options such as 'sourcedanswer', 'searchresults', and 'structured'). optional inclusion of images is available via the include images parameter.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Linkup, 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 Linkup.