Bring relevant market context to new interview notes
Capture the conversation in Notion, then let Exa find research related to the problem or market discussed.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Exa Search API
Search the web and extract contents from the results.
Why this helps
Interview notes are easy to collect but harder to place in a wider market context while conversations keep coming.
- Find sources relevant to the problem described in a new interview.
- Compare individual feedback with broader public information.
- Keep the synthesis close to the original notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Exa to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to research newly created interview notes.
- 3Give Notis one instruction to search for the problem or market context described in the page and summarize findings with sources.
- 4Select the Notion Page Created trigger, scoped to the interview parent page or data source if useful, and choose a reporting channel.
- 5Test with one real interview note and review the relevance of the results.
Questions about this workflow
Does it analyze private interview content?
The prompt can use the page content available to the Notion integration to guide a public web search. Avoid including sensitive details in the search instruction.
Can I use it for every page?
Scope the Page Created trigger to an interview data source or parent page when appropriate.
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.