Process a list of research URLs together
Update your Notion research list and have Firecrawl batch scrape its known URLs so source review is grouped into one job.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Firecrawl Batch Scrape
Scrape up to 500 known URLs as one durable job.
Why this helps
Opening many saved URLs one by one breaks concentration and makes source review feel bigger than it needs to be.
- Process multiple known URLs as one durable job.
- Reduce repetitive page opening and copying.
- Keep grouped source review connected to the Notion list update.
Setup
Build it in a few focused steps.
- 1Connect Notion and Firecrawl to Notis once through the portal.
- 2Ask Notis to batch scrape the known URLs in your Notion research list when a page changes.
- 3Select All Page Events or scope the workflow using the Notion page context in your instruction.
- 4Choose a run-report channel and test with a real list containing a few URLs.
Questions about this workflow
How many URLs can the batch include?
Firecrawl Batch Scrape supports up to 500 known URLs per job.
Does it discover URLs from a website?
Batch Scrape processes known URLs. Use Firecrawl Map to list website URLs first.
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.
Firecrawl Scrape
Scrape one URL into clean, LLM-ready markdown or JSON.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Firecrawl Search
Search the web and optionally scrape every result.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Firecrawl Crawl
Crawl a whole website into clean content, page by page.
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.
Firecrawl Map
List a website's URLs, fast, without scraping content.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Firecrawl Batch Scrape
Scrape up to 500 known URLs as one durable job.
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.
Firecrawl Agent
Autonomous multi-page web research into structured JSON.
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 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.