Refresh linked web sources when your Notion brief changes
Update a research brief and ask Notis to scrape its referenced URL again, returning clean content for your next decision.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Firecrawl Scrape
Scrape one URL into clean, LLM-ready markdown or JSON.
Why this helps
A brief can change while its source material stays stale, leaving you to remember which pages need another look.
- Revisit a source when the brief's content changes.
- Keep source review connected to the working document.
- Receive clean markdown or structured JSON from the scraped URL.
Setup
Build it in a few focused steps.
- 1Connect Notion and Firecrawl to Notis once through the portal.
- 2Ask Notis to scrape the source URL referenced in a brief whenever that page's content is updated.
- 3Select the Notion Page Content Updated trigger and scope it to the relevant page or data source if needed.
- 4Choose a channel for run reports and test by updating a brief with a real source URL.
Questions about this workflow
Can I limit this to a specific brief?
The Page Content Updated trigger supports a page or data source scope, so choose the scope that matches your workflow.
What format can the scrape return?
Firecrawl Scrape can return clean markdown or JSON shaped around the information you request.
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.