[Integrations](https://spiral.ai/integrations) › [Zapier](https://spiral.ai/integrations/zapier) › [GitHub user pull requests](https://spiral.ai/integrations/zapier/github-user-pull-requests)

# How to Use GitHub user pull requests in Zapier

Get public pull requests authored by a GitHub account, with titles, repositories, states, creation times, and links. Use it to find proposed changes across repositories or build a dated change digest.

|  |  |
| --- | --- |
| Model | GitHub user pull requests |
| Available through | ScrapeCreators |
| Category | Data |
| Price | $0.0013 per run. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with GitHub user pull requests in Zapier

- Every Monday, use GitHub user pull requests for tiangolo covering the previous calendar week. Report newly seen proposal URLs with their titles, repositories, and states.
- Each morning, use GitHub user pull requests for antfu covering the previous seven days. Show newly seen open proposals in repositories whose names contain vite.
- Every Friday, use GitHub user pull requests for yyx990803 covering the previous 30 days. Group newly seen proposals by repository and include their creation dates and links.
- Each week, use GitHub user pull requests for sindresorhus covering the previous calendar month. Compare matching URLs with the previous report and list any changes in reported state.
- On the first of each month, use GitHub user pull requests for tiangolo covering the previous month. Prepare a reading list from titles mentioning documentation or CLI changes, with repository names and links.

## How to set up GitHub user pull requests 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 user pull requests in a workflow step**: Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds GitHub user pull requests, 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 user pull requests**: 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": "scrapecreators",
    "model": "scrapecreators/github-user-pull-requests",
    "input": {
      "handle": "torvalds"
    }
  }'
```

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

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

## GitHub user pull requests tools and prices

- [GitHub · Pull Requests](https://spiral.ai/tools/scrapecreators/scrapecreators/github-user-pull-requests) (ScrapeCreators): Up to $0.0013 per run.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| since |  | — | Only return pull requests created on or after this date. Use YYYY-MM-DD. |
| until |  | — | Only return pull requests created on or before this date. Use YYYY-MM-DD. |
| cursor |  | — | Cursor from the previous response. Defaults to 1. |

## What can you do with GitHub user pull requests in Zapier?

Receive a recurring digest of newly opened public proposals in open-source projects you follow. A scheduled agent can compare returned GitHub URLs with earlier results and revisit older creation windows for changes in reported state.

### Draft a proposed-change digest

Turn an open-source creator's public pull request titles into a dated digest, grouped by repository and linked to the original proposals.

### Find upstream fixes to investigate

Search returned titles for a dependency or bug mentioned in your project, then build a shortlist of pull request links for technical review.

### Prepare a documentation review queue

Identify titles suggesting renamed options, new commands, or deprecated behavior. Give documentation editors the repository, creation date, and proposal link.

### Review open proposals in a dependency

Keep returned open pull requests for repositories your product depends on, with titles and links for maintainers to inspect.

### Build a proposal chronology

Arrange retrieved pull requests by creation time to document when public changes were proposed. Keep closed proposals separate from claims about released features.

### Organize changes across repositories

Group an open-source creator's returned pull requests by destination repository so a project update can cover proposals spread across several codebases.

## Overview

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

## GitHub user pull requests in other agents

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

## More Zapier guides

- [GitHub user profile](https://spiral.ai/integrations/zapier/github-user-profile)
- [GitHub user repositories](https://spiral.ai/integrations/zapier/github-user-repositories)
- [GitHub user following](https://spiral.ai/integrations/zapier/github-user-following)
- [Mistral OCR 4.1](https://spiral.ai/integrations/zapier/mistral-ocr-4-1)
- [GitHub user followers](https://spiral.ai/integrations/zapier/github-user-followers)
- [Mistral OCR document extraction](https://spiral.ai/integrations/zapier/mistral-ocr-document-extraction)

## Questions about GitHub user pull requests in Zapier

**Can Zapier use GitHub user pull requests?**

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

**How much does GitHub user pull requests cost in Zapier?**

$0.0013 per run. 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 a ScrapeCreators account to use GitHub user pull requests in Zapier?**

No. Spiral runs GitHub user pull requests on its own ScrapeCreators account. You sign in to Spiral once and never paste a key.

**How long does it take to set up GitHub user pull requests 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 user pull requests runs?**

GitHub user pull requests runs in the background. Zapier starts the run, checks on it and gives you the json when it's ready.

**Does this include private pull requests?**

No. The endpoint documents public pull requests authored by the requested GitHub account; private repository activity is outside its stated coverage.

**What information comes back for each pull request?**

The documented response contains five pull request fields: title, repository, state, creation timestamp, and GitHub URL.

**Does a closed pull request mean the change shipped?**

No. GitHub allows pull requests to be closed without merging, so a closed state alone does not establish that the proposed code was incorporated.

**Is the returned data guaranteed to be accurate?**

ScrapeCreators explicitly does not guarantee data accuracy or availability. Its documented response provides a GitHub URL for checking the original pull request.

**Can public GitHub data be used for unsolicited outreach?**

GitHub prohibits using collected information for unsolicited emails or selling personal information to recruiters, headhunters, and job boards. Public visibility does not remove those restrictions.

