Make your saved reading list easier to review
At a time you choose, fetch clean content from saved links and get a digest that helps you decide what is worth reading closely.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Exa Contents
Fetch clean, LLM-ready content for a list of URLs.
Why this helps
Saved articles can accumulate faster than you can open, skim, and remember why you kept them.
- Turn saved URLs into a more reviewable batch.
- Spend less time reopening articles just to find the key point.
- Choose what merits a deeper read with source links close by.
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 refresh saved reading links on a recurring schedule.
- 3Write one plain-language instruction to fetch readable content from URLs in your Notion reading list and return concise summaries with links.
- 4Choose the recurring trigger, reporting channel, and relevant reading-list context in your prompt.
- 5Test with a small set of real saved URLs and review the summaries.
Questions about this workflow
Does Exa discover new articles in this workflow?
This workflow fetches content from URLs already saved in your reading list.
Can the digest be sent to Notion?
Describe the desired destination in the prompt if you want the results recorded in a connected Notion space.
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.