Keep crawl follow-up moving without repeated manual checks
Let a scheduled check tell you when a crawl has progressed, so you can spend less attention refreshing job status.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check Crawl Status
Tool to check the processing status of a crawl job using snapshot id. call before attempting to download results to ensure data collection is complete.
Why this helps
Long-running data collection creates a stream of small status checks that interrupt focused work.
- Check active crawl progress on a regular cadence.
- Reduce repeated manual status polling.
- Make ready jobs easier to notice and review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Brightdata to Notis once in the portal.
- 2Create an automation and prompt Notis to check Brightdata crawl status for active snapshot IDs tracked in Notion.
- 3Choose a recurring Notis schedule, select a channel for run reports, and test with one real snapshot ID.
Questions about this workflow
What does the action need?
Check Crawl Status uses a snapshot ID for the crawl job.
Does the workflow download finished results?
No. It checks processing status; downloading scraped data is a separate Brightdata action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Brightdata. A trigger fires from one place; an action lands in another.
Notion triggers
Brightdata actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Trigger Site Crawl
Tool to trigger a site crawl job to extract content across multiple pages or entire domains. use when you need to start a crawl for a given dataset and list of urls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Browse Available Scrapers
Tool to list all available pre-made scrapers (datasets) from bright data's marketplace. use when you need to browse available data sources for structured scraping.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Filter Dataset
Tool to apply custom filter criteria to a marketplace dataset (beta). use after selecting a dataset to generate a filtered snapshot.
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 Available Cities
Tool to get available static network cities for a given country. use when you need to configure static proxy endpoints after selecting a country.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Available Countries
Tool to list available countries and their iso 3166-1 alpha-2 codes. use when you need to configure zones with valid country codes before provisioning proxies.
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.
Download Scraped Data
Tool to retrieve the scraped data from a completed crawl job by snapshot id. use after triggering a crawl or filtering a dataset to download the collected data.
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.
Check Crawl Status
Tool to check the processing status of a crawl job using snapshot id. call before attempting to download results to ensure data collection is complete.
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.
List Unlocker Zones
Tool to list your configured web unlocker zones and proxy endpoints. use to view available zones for web scraping and bot protection bypass.
Connect any two apps with Notis in the middle.
Notion and Brightdata, 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 Brightdata.