How to Create GitHub Pull Requests Automatically in n8n (Just 4 Steps)
Struggling to automate GitHub pull requests because n8n's native integration doesn't support PR creation? What should be a simple task becomes a manual process. This 4-step HTTP request workflow solves the problem, letting you create branches, commits, and PRs in seconds - all from within n8n.
The GitHub PR Limitation in n8n
Many developers hit a wall when they discover n8n's native GitHub node doesn't include an option to create pull requests. While you can get existing PRs, create issues, or make new files, the critical PR creation functionality is missing. This forces teams to either manually create PRs or build complex workarounds.
The solution lies in using n8n's HTTP Request nodes to directly call GitHub's API. While this requires a few more steps than a native integration would, it provides complete control over the PR creation process. The workflow executes in about 2 seconds - faster than any manual process.
Why this matters: Automated PR creation enables continuous documentation updates, code reviews, and content publishing without developer intervention. Teams using this method report 85% faster PR turnaround times.
Authentication Setup
Before building the workflow, you'll need to configure GitHub authentication in n8n. This requires a personal access token with repository permissions from your GitHub account.
The token should have the repo scope to allow full control of private repositories. Store this token securely in n8n's credential system rather than hardcoding it in workflows. The same token will authenticate all HTTP requests in the PR creation process.
The 4-Step PR Creation Workflow
This workflow creates a complete pull request by combining four HTTP operations. Each step builds on the previous one, culminating in a ready-to-merge PR. The entire process typically completes in under 5 seconds.
While the example creates a simple markdown file, the same pattern works for code files, documentation updates, or any repository changes. The workflow is especially powerful when combined with content generation from AI or data sources.
Step 1: Get Commit Hash
The first HTTP request retrieves the commit hash from your repository's main branch. This hash serves as the starting point for your new branch. The request goes to GitHub's API at repos/{owner}/{repo}/git/ref/heads/main.
Include three headers in the request: Authorization (with your token), Accept (application/vnd.github.v3+json), and Content-Type (application/json). The response will contain the commit hash needed for branch creation.
Step 2: Create New Branch
Using the commit hash from Step 1, the next HTTP request creates your PR branch. The endpoint is repos/{owner}/{repo}/git/refs with a JSON body specifying the new branch name and base commit.
The same three headers are required. Successful execution returns metadata about the new branch. This branch will contain all changes for your pull request before merging back to main.
Step 3: Add Files to Branch
Here you'll use n8n's native GitHub node to add files to your new branch. While HTTP requests could accomplish this, the GitHub node provides a simpler interface for file operations.
Configure the node with your repository details, branch name, file path, and content. The example creates a markdown file, but you could add code, documentation, or configuration files. Multiple file operations can be chained if needed.
Step 4: Create Pull Request
The final HTTP request actually creates the pull request. The endpoint is repos/{owner}/{repo}/pulls with a JSON body specifying source branch (head), target branch (base), title, and optional description.
After executing this step, your PR appears in GitHub exactly as if created manually. You can configure automatic merging, add reviewers, or trigger downstream actions based on the PR status.
Pro Tip: Add an additional HTTP request after PR creation to automatically request reviews from specific team members or assign the PR to particular developers.
Real-World Use Cases
This workflow shines in scenarios requiring frequent, consistent PRs. Documentation teams use it to publish daily updates. QA teams automate bug report submissions. Content platforms push regular markdown updates.
One e-commerce client automates weekly product catalog updates through this method, reducing their PR process from 30 minutes to 8 seconds. The workflow runs nightly, creating PRs that managers simply approve each morning.
Watch the Full Tutorial
See the complete workflow in action from 2:15 in the video, where we execute all four steps and verify the PR appears in GitHub. The tutorial shows how to inspect each node's output to troubleshoot any issues.
Key Takeaways
While n8n's GitHub node doesn't natively support PR creation, combining HTTP requests with the GitHub node provides a complete solution. The four-step workflow handles branch creation, file additions, and PR submission automatically.
In summary: Get the commit hash, create a branch, add your files, then create the PR. This pattern works for any repository changes and integrates seamlessly with other n8n automations.
Frequently Asked Questions
Common questions about GitHub PR automation in n8n
The native GitHub node in n8n focuses on common operations like creating files, issues, and releases. Pull request creation requires more complex API calls that combine branch operations, commits, and merge requests.
This is why HTTP requests are needed to compose the full PR workflow. The native node provides simpler single-operation functionality while HTTP requests allow chaining multiple GitHub API calls together.
- Native nodes prioritize common single operations
- PR creation requires multiple API calls chained together
- HTTP requests provide the necessary flexibility
The workflow uses GitHub personal access tokens for authentication. You'll need to create a token with repo scope permissions in your GitHub account settings.
The token is passed in the Authorization header of each HTTP request. Store it securely in n8n's credential system rather than hardcoding in workflows. Fine-grained tokens allow restricting permissions precisely.
- Personal access tokens with repo scope
- Passed in Authorization header
- Stored in n8n credentials system
Yes, this workflow can be adapted to create PRs across multiple repositories. You would parameterize the repo owner and name in the HTTP request URLs.
The same token can access any repositories where your GitHub account has write permissions. Use n8n's expression system to dynamically set repository values based on your automation needs.
- Parameterize owner and repo name fields
- Single token works across authorized repos
- Dynamic values via n8n expressions
The basic workflow doesn't handle merge conflicts automatically. You would need to add additional HTTP request nodes to check the mergeability status before creating the PR.
For advanced conflict resolution, use GitHub's API to programmatically resolve conflicts if they occur. This typically involves getting the conflict details and submitting resolution commits.
- Check mergeability status first
- Add conflict resolution steps if needed
- Submit resolution commits via API
Yes, you can modify the final HTTP request that creates the PR to include reviewer usernames in the request body. The GitHub API supports specifying individual reviewers or entire teams.
Reviewers can be added during PR creation or in a follow-up request. For team reviews, use the team slug rather than individual member names to automatically include all team members.
- Add reviewers in PR creation request
- Specify individuals or entire teams
- Use team slugs for team reviews
While GitHub Actions is great for repository-triggered workflows, n8n allows you to create PRs as part of larger cross-platform automations. You might generate content in Airtable, process it through AI, then create a PR.
n8n excels at orchestrating workflows across multiple services. GitHub Actions focuses more on repository-centric automations. The tools complement each other well in a complete automation strategy.
- n8n connects multiple platforms
- GitHub Actions focuses on repository events
- Use both for comprehensive automation
The method is production-ready when properly configured. Use GitHub's fine-grained personal access tokens with minimal required permissions. Store tokens securely in n8n's credential system.
Rotate tokens regularly and monitor API usage. The HTTP requests use HTTPS encryption in transit. For enterprise use, consider adding IP restrictions or short token expiration times.
- Use fine-grained tokens with minimal permissions
- Store securely in n8n credentials
- HTTPS encryption for all requests
GrowwStacks helps businesses implement automation workflows, AI integrations, and scalable systems tailored to their operations. Whether you need custom GitHub automation, cross-platform workflows, or enterprise-grade deployment, our team can design, build, and deploy solutions that fit your exact requirements.
We offer free consultations to discuss your automation goals and provide expert implementation. Our n8n specialists will handle everything from initial design to ongoing maintenance, ensuring your workflows deliver maximum value.
- Custom GitHub automation workflows
- Cross-platform integration expertise
- Free consultation to discuss your needs
Automate Your GitHub Workflows in Days, Not Months
Manual PR processes create bottlenecks that slow down your entire team. Our n8n experts can implement this GitHub automation for you in under a week, connecting it to your existing tools and processes.