GitHub
Every GitHub event in one universal stream
GitHub on Tiny Command takes an unusual shape: one trigger and twenty-three actions. The trigger, New GitHub Event, is the universal stream, every webhook event GitHub fires (push, pull_request, issues, release, deployment, workflow_run, check_run, label, comment, fork, star, watch, release, deployment_status, and dozens more) routes through it. Filter at the trigger by event type, repository, branch, or any payload field, so the workflow only runs on the events you actually care about. The action side covers the operational surface devs touch most: Create Issue, Update Issue, Add Labels to Issue, Search Issues, Create Pull Request, Merge Pull Request, Create Pull Request Review, Create Comment, Create Release, Create or Update File, plus the read endpoints for repositories, branches, commits, and workflow runs. The connection uses a GitHub App installation (preferred for repo-scoped access) or a personal access token, depending on whether you're automating org-wide or for yourself.
Workflows start when GitHub does.
1 real-time trigger, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Do anything GitHub can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add Labels | Adds labels to a GitHub issue or pull request by name. Used for AI-driven triage or auto-tagging based on file paths touched. |
| Create Comment | Adds a comment to a GitHub issue or pull request. Used for AI review summaries, build-status pings, or status broadcasts from CI/CD. |
| Create Issue | Creates a new issue in a GitHub repository with title, body, assignees, labels, milestone, and project. The default write for piping bug reports or alerts into GitHub. |
| Create Pull Request | Creates a new pull request in a GitHub repository from a head branch to a base branch with title, body, and draft flag. Used for auto-PRs from generated code or dependency updates. |
| Submit PR Review | Submits a review on a GitHub pull request: APPROVE, REQUEST_CHANGES, or COMMENT. Used for AI code review or for cross-system approval gating. |
| Create Release | Creates a new release for a repository with tag name, target commitish, name, body (release notes), draft, and prerelease flags. Used to automate releases from your CI pipeline. |
| Create or Update File | Creates or updates a file in a GitHub repository in a single commit, with branch, commit message, and content. The SHA is auto-fetched on update; the standard tool for small file commits without a full git client. |
| Delete File | Deletes a file from a GitHub repository in a single commit. The file's SHA is auto-fetched, so you only need to provide the path. |
| Get File | Gets the contents of a file in a GitHub repository at a specific ref. Returns base64-encoded content along with SHA, size, and download_url. |
| Get Issue | Retrieves a GitHub issue by its number with title, body, state, labels, assignees, and milestone. The standard read after a trigger fires with an issue number. |
| Get Pull Request | Gets details of a GitHub pull request: title, body, state, head/base, mergeable, reviewers, labels, and diff stats. Used to enrich a PR-event trigger. |
| Get Repository | Retrieves details of a GitHub repository: name, description, default branch, visibility, license, topics, and stats. Used to enrich a trigger or render repo info. |
| List Branches | Lists branches in a GitHub repository with their head SHA and protection status. Used to populate a branch picker before creating a PR. |
| List Commits | Lists commits on a repository branch with SHA, message, author, and date. Used for changelog generation, audit logs, or release-note drafts. |
| List Issues | Lists issues in a GitHub repository with filters for state, assignee, labels, milestone, and update time. Used for triage reports or warehouse export. |
| List Pull Requests | Lists pull requests in a repository with filters for state (open/closed/all), head, base, and sort. Used for review-queue dashboards and stale-PR cleanup. |
| List Releases | Lists releases for a GitHub repository with tag, name, body, and published_at. Used to render a changelog page or to feed release-notes feeds. |
| List Repositories | Lists repositories for the authenticated user or a specific organization. Used to populate a repo picker before any cross-repo automation. |
| List Workflow Runs | Lists workflow runs for a repository with status, conclusion, branch, and timing. Used for CI dashboards and for triggering downstream automation when a build completes. |
| Merge Pull Request | Merges an open pull request with the chosen merge method (merge, squash, rebase). Required checks must pass first or you'll get a 405. |
| Search Issues | Searches GitHub issues and pull requests across repositories using GitHub's search syntax (repo:, author:, label:, state:). Heavily rate-limited; cache results aggressively. |
| Search Repositories | Searches GitHub repositories by name, topic, language, or stars using GitHub's search syntax. Heavily rate-limited (10 req/min for unauthenticated; 30 for authenticated). |
| Update Issue | Updates an existing GitHub issue: title, body, state, assignees, labels, or milestone. Only the fields you pass are changed. |
Pre-built GitHub workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect GitHub once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every GitHub field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the GitHub integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect GitHub to Tiny Command?
What GitHub triggers does Tiny Command support?
What GitHub actions can I run from a workflow?
Is the GitHub integration real-time?
Do I need to write code to use GitHub with Tiny Command?
How much does the GitHub integration cost?
More developer tools apps people connect.
Same category as GitHub, ordered by how often teams pair them. Hover the carousel to pause.
Do more with GitHub.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
