How to Use npm package version details in Zapier
Returns one npm release's dependencies, declared engine requirements, tarball location, and integrity metadata. Use it to review a specific release before an upgrade.
Prompts to try with npm package version details in Zapier
Copy an example into Zapier, or ask in your own words.
Every Monday at 9am: use npm package version details to look this up and give me the result as a table.
Pull the latest numbers from npm package version details and tell me what changed since last week.
Check npm package version details and summarize what you find in three bullet points.
Pull the newest data from npm package version details and give me the result as a table.
Check npm package version details every morning and tell me only when something changed.
How to set up npm package version details in Zapier
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send Zapier this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Add an MCP Client connection
In Zapier open Apps, click Add connection and search for MCP Client. Fill in the form:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Zapier never sees it, and you can remove it under Settings › Connected apps in the console.
- Run a Spiral tool in a Zap
Add an MCP Client step to a Zap and choose the Run Tool action with your Spiral connection. Pick a tool: discover finds the right model for a task, estimate_cost prices it and run runs it. For example, run with:
{ "provider": "fal", "model": "fal-ai/flux/schnell", "input": { "prompt": "a lighthouse at dawn" }, "wait": true } - Run npm package version details in a workflow step
Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds npm package version details, prices it and runs it each time the step fires.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run npm package version details
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "npmjs-com/packages/get_package_version", "input": { "url": "<url>" } }'
Then paste one of the prompts above: Zapier finds npm package version details on Spiral, shows the price and runs it.
npm package version details providers and prices
Spiral runs npm package version details through Alexandria. Open a card for today's price, with every fee included.
What can you do with npm package version details in Zapier?
Keep a weekly npm package watchlist with changes worth reviewing. Compare successive results to highlight changes in public package records or download measurements.
Compare dependency candidates
Find package names for schema validation, inspect published metadata and release requirements, and compare download totals, daily patterns, and version shares. Build a shortlist for a project trial.
Plan a major version migration
Review release requirements and downstream packages alongside download totals, daily trends, and version shares. Use the evidence to choose compatibility tests and prioritize migration documentation.
Prepare a weekly package review
Compare saved publisher listings, package metadata, release details, and returned dependent names. Add changes in download totals, daily patterns, and version shares to identify items worth reviewing.
Check package references in developer documentation
Resolve package names with search and suggestions, check publisher catalogs, and inspect package and release metadata. Use the results to correct package references and dependency requirements in a tutorial.
Check package identity before evaluation
Resolve a partial package name, compare search matches with publisher listings, and inspect repository and release metadata. Produce an identity check before testing the package.
More on npm package version details and Zapier
Overview
npm package version details in other agents
Questions about npm package version details in Zapier
Can Zapier use npm package version details?
Yes. Add Spiral to Zapier as an MCP server, and Zapier can find and run npm package version details like any built-in tool.
How much does npm package version details cost in Zapier?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Zapier plan is separate.
Do I need an Alexandria account to use npm package version details in Zapier?
No. Spiral runs npm package version details on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up npm package version details in Zapier?
About two minutes: add an MCP Client connection, then sign in to Spiral and approve, then run a Spiral tool in a Zap.
Does Zapier wait while npm package version details runs?
npm package version details runs in the background. Zapier starts the run, checks on it and gives you the json when it's ready.
How fresh are npm download statistics?
npm documents a daily process that aggregates the previous day's logs after UTC midnight. Download statistics therefore describe completed reporting days.
Why might a published package be missing from npm search?
npm says newly published packages can take up to two weeks to appear. Deprecated packages are excluded from search results.
Do npm download counts represent unique users?
No. npm counts successful package tarball responses, including downloads from automated builds, mirrors, and analysis robots.
How much download history can npm return at once?
npm limits download queries other than bulk queries to 18 months per request. Per-version download counts cover only the previous seven days.
Does npm search return every match in one response?
npm registry search returns at most 250 matches per request and supports offset pagination. The response also reports a total.
Start using npm package version details in Zapier
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Zapier:
set up https://spiral.ai/SKILL.md


