ActionGitHubUpdated June 2026

How do I merge a GitHub PR via API?

Short answer: You can merge pull request in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Merge Pull Request action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Merge Pull Request in GitHub — start free All 23 GitHub actions

Merge Pull Request in GitHub — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Repository Owner owner	string	Required	GitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository Name repo	string	Required	GitHub repository name — the part after / in owner/repo URLs. Not the full URL.
Pull Request Number pull_number	string	Required	GitHub pull request number — the integer shown after /pull/ in the PR URL (per-repo, not global).
Commit Title commit_title	string	Optional	Title for the merge commit (defaults to PR title)
Commit Message commit_message	string	Optional	Extra detail for the merge commit
Merge Method merge_method	options	Optional	Merge Method. Options: Merge Commit, Squash, Rebase

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project",
  "pull_number": "e.g. 99",
  "commit_title": "e.g. Merge PR #99: Fix login redirect",
  "commit_message": "{{trigger.commit_message}}"
}

Returns

{
  "sha": "abc123def456",
  "merged": true,
  "message": "Pull Request successfully merged"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Merge Pull Request.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitHub

2 Google Sheets triggers

HubSpot → GitHub

18 HubSpot triggers

FAQ

Questions about Merge Pull Request.

What does the Merge Pull Request action do in GitHub?

Merges an open pull request with the chosen merge method (merge, squash, rebase). Required checks must pass first or you'll get a 405.

What inputs does Merge Pull Request require?

Required: Repository Owner, Repository Name, Pull Request Number. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitHub returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Merge Pull Request support batch operations?

Yes. Run Merge Pull Request inside a Loop node to process arrays. TinyCommand handles GitHub's rate limits automatically so you don't have to throttle manually.

More actions