Spiral gives your agent every tool with one account. Browse the tools →

Zapier · E-commerce

How to Use GitHub repository issue counts in Zapier

Fetch issue totals by state and label, excluding pull requests. Use it to measure a backlog without downloading individual reports; GitHub's search system supplies the counts.

Prompts to try with GitHub repository issue counts in Zapier

Copy an example into Zapier, or ask in your own words.

Every Monday, use GitHub repository issue counts for vitejs/vite to compare open and closed issue totals with last week's saved results.

GitHub repository issue countsZapier
Try asking
  • Every Monday at 9am: use GitHub repository issue counts to look this up and give me the result as a table.

  • Pull the latest numbers from GitHub repository issue counts and tell me what changed since last week.

  • Check GitHub repository issue counts and summarize what you find in three bullet points.

  • Pull the newest data from GitHub repository issue counts and give me the result as a table.

How to set up GitHub repository issue counts in Zapier

Pick the way that suits you. Each takes about two minutes.

Use the Spiral skill

  1. Send Zapier this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. 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

  1. 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
  2. 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.

  3. 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
    }
  4. Run GitHub repository issue counts in a workflow step

    Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds GitHub repository issue counts, prices it and runs it each time the step fires.

Use the Spiral CLI

  1. 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

  1. Create an API key

    In the console, under API keys.

  2. Run GitHub repository issue counts

    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": "github-com/repositories/issue_counts",
        "input": {
          "repo": "<repo>"
        }
      }'

Then paste one of the prompts above: Zapier finds GitHub repository issue counts on Spiral, shows the price and runs it.

GitHub repository issue counts providers and prices

Spiral runs GitHub repository issue counts through Alexandria. Open a card for today's price, with every fee included.

AlexandriaE-commerce
GitHub · Issue counts
github-com/repositories/issue_counts

Settings you can ask for

Ask Zapier for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Stateopen, closed, or allopen

Issue state to match.

Every API field of GitHub · Issue counts is on its tool page: open its card above.

What can you do with GitHub repository issue counts in Zapier?

Produce a recurring change report for selected public projects and packages on GitHub. A scheduled agent can compare saved observations of releases, repository status, issue totals, files, or advisories and report what changed.

Review a dependency before adoption

Build an adoption brief covering repository status, contribution concentration, license text, issue categories and totals, release history, and reported vulnerability or malware concerns for the exact packages under consideration.

Prepare a dependency upgrade review

Compare the installed version with published releases, read migration files and known issue reports, and check relevant advisories. Include project status and contribution concentration when deciding how much upstream support to expect.

Investigate a reported package incident

Read the advisory and affected package ranges, compare release notes and manifests, then inspect related issue categories, reports, and totals. Keep a documented vulnerability fix separate from a malicious-package report.

Assess upstream maintenance

Compare archive status, contribution concentration, release dates, issue categories, and backlog totals across candidate repositories. Read representative issue reports to explain the numbers.

Plan an open source contribution

Read contribution instructions, discover the repository's actual labels, and inspect suitable issues alongside backlog totals. Use project status and contribution distribution to understand the project's context before proposing work.

Compare migration destinations

Compare two public projects using their README files, repository metadata, contribution distribution, release notes, and issue evidence. Summarize which documented limitations matter for the planned migration.

Questions about GitHub repository issue counts in Zapier

Can Zapier use GitHub repository issue counts?

Yes. Add Spiral to Zapier as an MCP server, and Zapier can find and run GitHub repository issue counts like any built-in tool.

How much does GitHub repository issue counts 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 GitHub repository issue counts in Zapier?

No. Spiral runs GitHub repository issue counts on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up GitHub repository issue counts 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 GitHub repository issue counts runs?

GitHub repository issue counts runs in the background. Zapier starts the run, checks on it and gives you the json when it's ready.

Can I reuse anything that is public on GitHub?

Public visibility alone does not grant unrestricted reuse. GitHub says that without a license, default copyright restrictions apply to source code; its Advisory Database has a separate CC BY 4.0 license.

How current is GitHub's data?

Freshness depends on the record. Contributor results can be a few hours old because GitHub caches them, while a file selected by branch can change whenever new commits arrive.

Does a GitHub release history include every version tag?

No. GitHub excludes Git tags that have no associated release, and its latest-release lookup excludes prereleases and drafts.

Do GitHub issues include pull requests?

GitHub's underlying issue responses can contain both, with pull requests identified separately. An issue-only backlog should exclude pull requests before its totals are compared.

Where do GitHub's malware reports come from?

GitHub automatically publishes malware advisories from the npm security team and the OpenSSF Malicious Packages repository. These reports concern malicious packages and are separate from ordinary vulnerability advisories.

Get started

Start using GitHub repository issue counts in Zapier

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Zapier:

Set up Zapier

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options