What can I automate with the PyPI Stats integration?

Read PyPI download statistics from a workflow. Get a package's downloads over the last day, week and month, or its full daily series over the 180 days PyPI Stats keeps, with the total, the average per day, the busiest day and how the window compares with the one before it. Split those downloads by Python major version, by minor version to see whether 3.9 can be dropped, or by operating system to see which wheels are worth building. Compare several packages side by side, ranked with each one's share. Mirror traffic is excluded by default, so the figures are real installs. Every action reads: nothing here changes anything. No account or API key required. Lodol supports 6 actions for PyPI Stats, which you can combine with any other app in a workflow.

How do I connect PyPI Stats to Lodol?

Connect PyPI Stats once in your workspace and every action and trigger it supports can be added to a workflow, by you in the editor or by your AI.

All integrationsAnalytics

PyPI Stats

Read PyPI download statistics from a workflow.

Start Free Browse all integrations

actions: 6

Actions

Steps a workflow can run in PyPI Stats.

Get recent downloadsGet how many times a package was downloaded from PyPI in the last day, the last week and the last month. All three numbers come back every time; the period you choose picks which one lands in the single 'downloads' field, so a threshold or an alert has one number to read. Mirror traffic is already excluded, so these are real installs. The starting point for 'how is my package doing?'. No API key required.
Get download historyGet a package's daily download series, up to the 180 days PyPI Stats keeps. Comes back with the total, the average per day, the busiest day, and the same figure for the equal window immediately before, so a step can say 'up 12% on the month before' rather than only quoting a number. Roll the rows up by week or month for a chart, or ask for no series at all when only the totals matter. Mirror traffic is left out by default. No API key required.
Get downloads by Python major versionSplit a package's downloads by Python major version: how many came from Python 3, how many from Python 2, and how many from downloads that did not say which. Each category comes back with its total and its share, plus a daily series you can roll up by week or month. The step for 'is anyone still on Python 2?'. No API key required.
Get downloads by Python minor versionSplit a package's downloads by Python minor version: 3.13, 3.12, 3.11 and so on, each with its total and its share of the window. This is the step that answers 'can we drop support for 3.9 yet?' with a number instead of a guess. Comes with a daily series you can roll up by week or month. No API key required.
Get downloads by operating systemSplit a package's downloads by the operating system that asked for them: Windows, Linux, macOS (which PyPI records as Darwin), anything else, and the downloads that did not say. Each comes back with its total and its share, plus a daily series you can roll up by week or month. The step for deciding which wheels are worth building. No API key required.
Compare packagesCompare the recent downloads of several packages side by side, ranked biggest first with each one's share of the total. Answers 'are we still ahead of them?' in one step rather than several. Between two and ten packages; a package PyPI Stats has no figures for is listed as missing rather than failing the step. No API key required.