Search npm packages after README changes
Turn documentation updates into a quick check for current libraries and ecosystem options.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Search NPM Packages
Tool to search for packages in the npm registry. Use when you need to find packages matching a search term. Results are returned in an 'objects' array; each element contains package metadata under a 'package' field and weekly download estimates under 'downloads.weekly'.
Why this helps
README updates can mention tooling choices that are already outdated or poorly supported.
- Keeps docs aligned with current options
- Avoids separate research tasks
Setup
Build it in a few focused steps.
- 1Connect GitHub and npm to Notis once.
- 2Create an automation in the portal.
- 3Prompt Notis to search npm for packages relevant to README changes.
- 4Select README changed and a report channel.
- 5Test with a README edit.
Questions about this workflow
Does this edit the README?
No. It searches npm and reports relevant package results.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Npm. A trigger fires from one place; an action lands in another.
GitHub 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).
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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).
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Registry Changes Feed
Tool to get a stream of registry changes for replication purposes. Returns CouchDB-style change feed for following registry updates.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get NPM Registry Meta
Retrieves npm registry metadata via meta endpoints. Use 'ping' to verify registry connectivity or 'whoami' to get the authenticated username.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
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.
GitHub 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.