Find the useful pages behind a new research reference
Add a research subpage and have Firecrawl map its reference website, helping you find relevant pages without wandering through the site.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Map multiple URLs
Maps a website by discovering urls from a starting base url, with options to customize the crawl via search query, subdomain inclusion, sitemap handling, and result limits; search effectiveness is site-dependent.
Why this helps
A single reference can lead to an unplanned browsing session when you need to identify its related pages and supporting material.
- Discover related pages when a reference is added to a research hub.
- Reduce unstructured browsing across unfamiliar websites.
- Build a consistent trail from a research note to related material.
Setup
Build it in a few focused steps.
- 1Connect Notion and Firecrawl to Notis once through the portal.
- 2Ask Notis to create an automation or open Automations and choose New Automation.
- 3Describe in one plain-language instruction how Firecrawl should map the public site associated with a new research subpage.
- 4Choose the Notion Page Added to Page trigger for your research hub, set a report channel, and test with one subpage containing a public site.
Questions about this workflow
Which pages trigger this?
The trigger fires for a new subpage under the specified parent Notion page.
Does a mapped URL include the page contents?
Mapping discovers URLs. Scrape or crawl actions retrieve page content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Firecrawl. A trigger fires from one place; an action lands in another.
Notion triggers
Firecrawl actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel a crawl job
Cancels an active or queued web crawl job using its id; attempting to cancel completed, failed, or previously canceled jobs will not change their state.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Start a web crawl
Initiates a firecrawl web crawl from a given url, applying various filtering and content extraction rules, and polls until the job is complete; ensure the url is accessible and any regex patterns for paths are valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Extract structured data
Extracts structured data from web pages by initiating an extraction job and polling for completion; requires a natural language `prompt` or a json `schema` (one must be provided).
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.
Get the status of a crawl job
Retrieves the current status, progress, and details of a web crawl job, using the job id obtained when the crawl was initiated.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Map multiple URLs
Maps a website by discovering urls from a starting base url, with options to customize the crawl via search query, subdomain inclusion, sitemap handling, and result limits; search effectiveness is site-dependent.
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.
Scrape URL
Scrapes a publicly accessible url, optionally performing pre-scrape browser actions or extracting structured json using an llm, to retrieve content in specified formats.
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.
Search
Performs a web search for a query, scrapes content from the top search results using firecrawl, and returns details in specified formats.
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 Firecrawl, 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 Firecrawl.