Skip to content
Notis

Give every new product idea a research starting point

Capture the idea in Notion and let Firecrawl investigate the relevant market context into structured findings you can review.

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

Firecrawl Agent

Autonomous multi-page web research into structured JSON.

Why this helps

Ideas are easy to capture and easy to leave unvalidated when research requires a separate setup session.

  • Move from idea capture to initial evidence automatically.
  • Collect findings in a consistent structured format.
  • Spend review time on decisions rather than assembling search queries.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Firecrawl to Notis once through the portal.
  • 2Ask Notis to use Firecrawl Agent to research each newly created product idea page and return structured market findings.
  • 3Select the Notion Page Created trigger, scoped to the idea page or its parent if appropriate.
  • 4Choose where run updates should appear and test with one real idea page.

Questions about this workflow

What can the agent research?

Describe the research questions in the plain-language instruction, such as audiences, alternatives, or market signals.

Will this publish the research automatically?

No. Firecrawl returns findings for you to review; the workflow does not publish or approve them.

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.

TriggerScheduled

Firecrawl Scrape

Scrape one URL into clean, LLM-ready markdown or JSON.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Firecrawl Search

Search the web and optionally scrape every result.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Firecrawl Crawl

Crawl a whole website into clean content, page by page.

ActionInstant

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.

TriggerInstant

Firecrawl Map

List a website's URLs, fast, without scraping content.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Firecrawl Batch Scrape

Scrape up to 500 known URLs as one durable job.

ActionInstant

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.

TriggerInstant

Firecrawl Agent

Autonomous multi-page web research into structured JSON.

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

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.