Research new product ideas without opening a dozen tabs
Add an idea to Notion and let Exa find relevant market evidence, alternatives, and sources to help you choose a next step.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Exa Search API
Search the web and extract contents from the results.
Why this helps
Ideas pile up while researching each one requires a fresh round of searching and note-taking.
- Get a first pass on demand and market signals as soon as an idea is captured.
- Keep research attached to the Notion idea for later review.
- Spend focused time judging evidence instead of collecting links.
Setup
Build it in a few focused steps.
- 1Connect Notion and Exa to Notis once through the portal.
- 2Create an automation in the portal or tell Notis in any connected channel what you want it to do.
- 3Use one plain-language instruction: when a new product idea is added to Notion, search for market demand, competing solutions, and relevant evidence, then summarize the findings with source links.
- 4Select the Notion New Page trigger and choose a channel for run reports.
- 5Test with one real idea and check that the summary is useful in context.
Questions about this workflow
What does the workflow research?
The prompt can ask Exa to search for demand signals, comparable products, and evidence relevant to the idea.
Does it decide whether I should build the idea?
No. It gathers sources and summarizes evidence so you can make the decision.
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.
Exa Contents
Fetch clean, LLM-ready content for a list of URLs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Exa Search API
Search the web and extract contents from the results.
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 Exa, 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 Exa.