Research integration use cases
A Notion integration idea prompts Exa to look for real-world use cases and documentation. Keep the research step attached to the moment it becomes relevant, without a separate search session.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Search
Performs a web search using the exa engine, useful for queries requiring advanced filtering, specific content categories, or ai-optimized prompting.
Why this helps
New integration-idea row naming two products and a use-case question can otherwise sit in Notion without the research needed for a decision.
- Turns a specific Notion signal into a targeted Exa action.
- Returns source links in the chosen Notis run-report channel.
- Uses a plain-language instruction so the scope stays easy to revise.
Setup
Build it in a few focused steps.
- 1Connect Notion and Exa to Notis in the portal once.
- 2Ask Notis to create an automation named “Research integration use cases” with this prompt: “For new integration-idea row naming two products and a use-case question, search public use cases and official documentation. Report the result with source links; skip items that do not meet the condition and avoid repeating a result for the same Notion item.”
- 3Choose the Notion event for new integration-idea row naming two products and a use-case question as the trigger, and select a channel for run reports.
- 4Test with one real Notion example and review the Exa result and source links.
Questions about this workflow
What must be in Notion first?
Use new integration-idea row naming two products and a use-case question. The instruction should skip incomplete or unrelated entries.
Does this write the research back to Notion?
No. This workflow runs an Exa action and reports the result through Notis; writing back would require a separate Notion action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Exa. A trigger fires from one place; an action lands in another.
Notion triggers
Exa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate an answer
Generates a direct, citation-backed answer to a clear natural language question or topic using exa's search, adept at both specific answers and detailed summaries for open-ended queries.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Import
Tool to create a new import to upload data into a webset. use when you need to initialize an import before uploading the data file.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create a Monitor
Tool to create a new monitor. use when you need to schedule automated updates for a webset without manual runs.
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.
Create Webset
Tool to create a new webset with search, import, and enrichment setup. use when you need to configure and seed a webset in one call.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete import
Tool to delete an existing import. use when you need to permanently remove an import by its id.
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.
Delete webset
Tool to delete a webset. use after confirming the webset id to permanently remove the webset and all its items.
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.
Find similar
Finds web pages semantically similar to a given url using embeddings-based search, optionally retrieving full text, highlights, or summaries for results.
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 contents from URLs or document IDs
Retrieves configurable text and highlights from a list of exa document ids or publicly accessible urls.
Connect any two apps with Notis in the middle.
Not just Notion and Exa. Any 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 Exa.