[Integrations](https://spiral.ai/integrations) › [Zapier](https://spiral.ai/integrations/zapier) › [GitHub repository labels](https://spiral.ai/integrations/zapier/github-repository-labels)

# How to Use GitHub repository labels in Zapier

Fetch a repository's label names, descriptions, colors, and default-label flags. Use the actual label vocabulary to find relevant issues and build meaningful backlog counts.

|  |  |
| --- | --- |
| Model | GitHub repository labels |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with GitHub repository labels in Zapier

- Every Monday at 9am: use GitHub repository labels to look this up and give me the result as a table.
- Pull the latest numbers from GitHub repository labels and tell me what changed since last week.
- Check GitHub repository labels and summarize what you find in three bullet points.
- Pull the newest data from GitHub repository labels and give me the result as a table.
- Check GitHub repository labels every morning and tell me only when something changed.

## How to set up GitHub repository labels 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:

```text
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:

```json
{
  "provider": "fal",
  "model": "fal-ai/flux/schnell",
  "input": { "prompt": "a lighthouse at dawn" },
  "wait": true
}
```

4. **Run GitHub repository labels 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 labels, 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.

```bash
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 labels**: One request; the result comes back by polling or a webhook.

```bash
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/labels",
    "input": {
      "repo": "<repo>"
    }
  }'
```

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

Setup guide in the docs: https://spiral.ai/docs/quickstarts/zapier

## GitHub repository labels tools and prices

- [GitHub · Labels](https://spiral.ai/tools/alexandria/github-com/repositories/labels) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | HTTPS github.com/{owner}/{name} URL; deeper paths (issues, tree, ...) are accepted and reduced to the repository. Provide exactly one of repo or url. Pattern: ^(?:https?://)?(?:www\.)?github\.com/[A-Za-z0-9-]{1,39}/[A-Za-z0-9._-]{1,100}(?:[/?#].*)?$. |
| page | 1 to 1000 | 1 | 1-based page; has_next in the response says whether page+1 exists. |
| repo |  | — | Repository as `owner/name`, for example `firecrawl/firecrawl`. Provide exactly one of repo or url. Pattern: ^@?/?[A-Za-z0-9](?:[A-Za-z0-9-]{0,37}[A-Za-z0-9])?/[A-Za-z0-9._-]{1,100}(?:\.git)?/?$. |
| per_page | 1 to 100 | 100 | Records per page. |

## What can you do with GitHub repository labels 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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Zapier guides](https://spiral.ai/integrations/zapier)

## GitHub repository labels in other agents

- [Amp](https://spiral.ai/integrations/amp/github-repository-labels)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/github-repository-labels)
- [Claude](https://spiral.ai/integrations/claude-desktop/github-repository-labels)
- [Claude Code](https://spiral.ai/integrations/claude-code/github-repository-labels)
- [Cline](https://spiral.ai/integrations/cline/github-repository-labels)
- [Codex](https://spiral.ai/integrations/codex/github-repository-labels)
- [Cursor](https://spiral.ai/integrations/cursor/github-repository-labels)
- [Devin](https://spiral.ai/integrations/devin/github-repository-labels)
- [dots](https://spiral.ai/integrations/dots/github-repository-labels)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/github-repository-labels)
- [Gemini](https://spiral.ai/integrations/gemini/github-repository-labels)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/github-repository-labels)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/github-repository-labels)
- [goose](https://spiral.ai/integrations/goose/github-repository-labels)
- [Grok](https://spiral.ai/integrations/grok/github-repository-labels)
- [Grok Build](https://spiral.ai/integrations/grok-build/github-repository-labels)
- [Hermes](https://spiral.ai/integrations/hermes/github-repository-labels)
- [Instinct](https://spiral.ai/integrations/instinct/github-repository-labels)
- [Manus](https://spiral.ai/integrations/manus/github-repository-labels)
- [Muse](https://spiral.ai/integrations/muse/github-repository-labels)
- [Muse Code](https://spiral.ai/integrations/muse-code/github-repository-labels)
- [n8n](https://spiral.ai/integrations/n8n/github-repository-labels)
- [Notion](https://spiral.ai/integrations/notion/github-repository-labels)
- [OpenClaw](https://spiral.ai/integrations/openclaw/github-repository-labels)
- [opencode](https://spiral.ai/integrations/opencode/github-repository-labels)
- [Perplexity](https://spiral.ai/integrations/perplexity/github-repository-labels)
- [Raycast](https://spiral.ai/integrations/raycast/github-repository-labels)
- [VS Code](https://spiral.ai/integrations/vscode/github-repository-labels)
- [Windsurf](https://spiral.ai/integrations/windsurf/github-repository-labels)

## More Zapier guides

- [GitHub repository issues](https://spiral.ai/integrations/zapier/github-repository-issues)
- [GitHub repository search](https://spiral.ai/integrations/zapier/github-repository-search)
- [GitHub repository issue counts](https://spiral.ai/integrations/zapier/github-repository-issue-counts)
- [GitHub repository security advisories](https://spiral.ai/integrations/zapier/github-repository-security-advisories)
- [GitHub repository file](https://spiral.ai/integrations/zapier/github-repository-file)
- [GitHub security advisory](https://spiral.ai/integrations/zapier/github-security-advisory)

## Questions about GitHub repository labels in Zapier

**Can Zapier use GitHub repository labels?**

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

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

No. Spiral runs GitHub repository labels 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 labels 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 labels runs?**

GitHub repository labels 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.

