Fetch broad registry download context for a changed watchlist
When your watchlist changes, bring in a broad npm download snapshot to help frame the package research around it.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get All Packages Download Count Point
Get total npm registry download statistics for all packages for a specified time period. Returns aggregate download counts across the entire npm registry with start/end dates. Supports preset periods (last-day, last-week, last-month, last-year) or custom date ranges (YYYY-MM-DD:YYYY-MM-DD).
Why this helps
Comparing package signals without broader context can make research feel harder to interpret than it needs to be.
- Add a broad registry reference to package research.
- Reduce the effort of finding ecosystem-wide download context.
- Keep research follow-up connected to watchlist changes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Npm to Notis once in the portal.
- 2Create an automation in the portal or ask Notis for broad npm download context when a watchlist changes.
- 3In one instruction, ask Notis to retrieve total registry downloads for a chosen preset period and explain that the result is broad context for the watchlist.
- 4Choose the Notion Page Properties Updated trigger for the watchlist page and a channel for run reports.
- 5Test by updating a real watchlist property and reviewing the returned period.
Questions about this workflow
Are these counts for packages on the watchlist?
No. This action returns aggregate downloads across the entire npm registry.
When is broad context useful?
It can help frame research conversations, but package-specific actions are better for evaluating individual dependencies.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Npm. A trigger fires from one place; an action lands in another.
Notion triggers
Npm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete User Token (Legacy)
Tool to delete a user authentication token using the legacy endpoint. Use when you need to revoke or remove a specific token from the npm registry.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Packages Download Count Point
Get total npm registry download statistics for all packages for a specified time period. Returns aggregate download counts across the entire npm registry with start/end dates. Supports preset periods (last-day, last-week, last-month, last-year) or custom date ranges (YYYY-MM-DD:YYYY-MM-DD).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get NPM Download Counts Point
Get npm package download statistics for a specified time period. Returns total download counts with start/end dates for single packages, scoped packages, or bulk queries (up to 128 packages). Supports preset periods (last-day, last-week, last-month, last-year) or custom date ranges (YYYY-MM-DD:YYYY-MM-DD).
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 NPM Package Download Counts Over Date Range
Tool to get download counts for an npm package over a specified date range. Use when you need historical daily download data.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All NPM Packages Download Counts by Period
Tool to get daily download counts for all npm packages over a specified period. Use when you need aggregate download statistics across the entire npm registry.
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.
Get Registry Changes Feed
Tool to get a stream of registry changes for replication purposes. Returns CouchDB-style change feed for following registry updates.
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.
Get NPM Registry Meta
Retrieves npm registry metadata via meta endpoints. Use 'ping' to verify registry connectivity or 'whoami' to get the authenticated username.
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.
Get NPM Package Version Downloads (Last 7 Days)
Tool to get download counts for specific versions of a package over the last 7 days. Use when you need to understand which versions are most popular.
Connect any two apps with Notis in the middle.
Notion and Npm, 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 Npm.