How to Trigger GitHub Actions from Your iPhone: 7 Options Compared
Disclosure: This article is written by the developer of Pocket Actions, one of the apps compared below. I've tried to be fair, including where another option is the better fit. Competitor details come from their App Store listings and official docs, linked inline. Anything I couldn't confirm is marked as such.
The problem: your workflow is ready, but your laptop is closed
GitHub Actions began as CI/CD, but many people now use it as a free, serverless "run this script" button. A redeploy, a data refresh, a scraper, a report, or an AI job your assistant wrote for you: once these live in a workflow with a workflow_dispatch trigger, you can run them on demand.
The catch is where you are when you want to run them:
- A bug report arrives while you're out, and you just want to redeploy.
- You want a long batch job to start before bed, so it's done by morning.
- You want an AI job (research, summaries, inbox cleanup) to run now, not at the next cron tick.
- You'd like to run a job a few extra times today without editing the schedule.
GitHub supports manual runs through workflow_dispatch. The workflow file has to be on the default branch, and you need write access to the repository (GitHub Docs). So pressing the button from a phone is possible. The real questions are how many steps it takes, what credentials you hand over, and what you can see afterward.
This guide compares seven practical options. None of them is right for everyone, and many people end up combining two.
Three criteria that matter
1. Steps to run
If you trigger a workflow once a month, a long path is fine. If you trigger the same few workflows several times a week, the path matters more than any feature list. In the official app, for example, the path is roughly: open app → repository → Actions → Workflows → pick a workflow → Run workflow → (inputs) → confirm. Each step is small, but it adds up when you're standing on a train platform.
2. Setup and credentials
The options fall into three groups:
- Sign in with GitHub (official app, browser). No extra secrets.
- Paste a Personal Access Token (PAT) into an app. Ask where it's stored and what scopes it needs.
- Embed a token in something you build (an iOS shortcut). Fast, but the token lives inside the shortcut.
Whichever you choose, use the smallest scopes that work, set an expiry, and know how to revoke the token.
3. What happens after you tap
Some tools are built to watch runs: status, logs, notifications, re-run, cancel. Others are built to start runs. A few do both. If you need to confirm the result on your phone, a start-only tool isn't enough by itself.
Comparison table
Scroll sideways to see the whole table
| Option | Starts a workflow_dispatch run | Inputs | Logs / status | Setup | Price (US App Store) |
|---|---|---|---|---|---|
| GitHub Mobile (official) | Yes (since July 2024) | Yes | Yes, plus push notifications | Sign in with GitHub | Free |
| GitHub.com in Safari | Yes | Yes | Yes | Sign in | Free |
| iOS Shortcuts + REST API | Yes | Yes, if you build prompts | No (unless you build it) | Build one shortcut per workflow; token stored inside | Free |
| Acts – Actions Client | No sign of it* | — | Yes: progress, logs, re-run, cancel | Per app | Free |
| GitFlow for GitHub Actions | Yes (per listing) | Yes, with branch choice | Yes: dashboard, logs, re-run, deployment approvals | Per app | Free |
| GitHub Actions Widget | No (status only; tapping opens GitHub) | — | Latest status on Home/Lock Screen | Per app | $2.99 |
| Pocket Actions | Yes, in 1–3 taps; also runs Google Apps Script web apps | Yes (form built automatically) | No (only confirms the run was accepted) | Paste a PAT (repo only) | Free: 5 runs/day, 17/week. Premium: $2.99/mo or $49.99 lifetime |
*Acts' listing doesn't mention starting runs, and its public source code has no call to the dispatch endpoint (the App Store build could differ). GitFlow's listing explicitly says it starts workflow_dispatch runs with branch and inputs. Sources: Acts, GitFlow, GitHub Actions Widget, GitHub Mobile, GitHub Changelog.
Pros and cons of each option
1. GitHub Mobile (the official app)
Since July 2024, GitHub Mobile can manually run workflow_dispatch workflows from the Workflow view (Repository → Actions → Workflows) (GitHub Changelog). It also shows runs and logs, sends push notifications when a run finishes (with a failures-only option), and lets you re-run and cancel jobs (GitHub Blog). On top of that, it handles pull requests, issues, notifications, and code review.
Pros
- Official and free, with no extra token to manage.
- Covers the whole loop: start a run, watch it, get notified, re-run.
- Many developers already have it installed.
Cons
- The run button is several levels deep, separately for each repository. If your workflows are spread across many repos, you navigate a lot.
- It's a general-purpose GitHub client, so Actions is one section among many.
Best for: Anyone who triggers workflows occasionally and wants to watch results on the phone. If you only pick one tool, this is the reasonable default.
2. GitHub.com in Safari
Pros
- Nothing to install, and every web feature is available.
- Useful as a fallback when an app doesn't support something.
Cons
- The page is designed for a desktop screen, so tap targets are small and you scroll a lot.
- Sign-in and two-factor prompts can get in the way when you're in a hurry.
Best for: Rare, one-off runs, or anything the apps don't cover.
3. iOS Shortcuts + the GitHub REST API
A shortcut's "Get Contents of URL" action can call
POST /repos/{owner}/{repo}/actions/workflows/{workflow}/dispatches
with headers such as Authorization: Bearer <token> and a JSON body like {"ref":"main","inputs":{...}}. A GitHub employee published a working walkthrough (island94.org).
Pros
- Free and very fast once built: a Home Screen icon, Siri, a Back Tap, or even a personal automation.
- It can ask for inputs with "Ask for Input" prompts.
- Fully under your control.
Cons
- Shortcuts can't read the iOS Keychain, so the common practice is to paste the token into the shortcut itself (write-up). Keep such shortcuts private and use a fine-grained token scoped to one repository.
- You build and maintain one shortcut per workflow. Renaming a workflow file or changing inputs means editing the shortcut.
- No run status unless you build polling yourself.
Best for: People with one or two workflows who enjoy tinkering, or who want Siri or automation triggers.
4. Acts – Actions Client
Its App Store listing describes "an easy-to-use GitHub Actions client" that "displays the progress and logs of your workflow run beautifully, and allows you to re-run and cancel it" (App Store).
Pros
- Focused on Actions rather than all of GitHub.
- Readable logs, re-run, and cancel. Free.
Cons
- The listing doesn't mention starting new runs, and its public source code (maiyama18/Acts, last updated June 2022) has no call to the dispatch endpoint.
Best for: Watching and re-running CI runs from your phone.
5. GitFlow for GitHub Actions
Its listing describes a dashboard across repositories with success rate and failing or running workflows, every run with search and filters, step-by-step logs with highlighted errors, re-running jobs, and approving deployments (App Store).
Pros
- Strong monitoring across many repositories.
- Deployment approvals from your phone are handy for teams with environment protection rules. Free.
Cons
- Its listing says it can "start any manually triggered workflow (workflow_dispatch)" and pick the branch and inputs, so it covers launching too. It's new, with few ratings so far.
Best for: People responsible for keeping CI green across several repos.
6. GitHub Actions Widget
Its listing says it shows the latest run state, branch, and last-update time for up to four workflows on the Home Screen and Lock Screen. Tapping a workflow opens its run on GitHub (App Store).
Pros
- Zero-tap status: you see pass, fail, or running without opening anything.
Cons
- A status display, not a launcher. Limited to four workflows. Paid ($2.99).
Best for: Keeping an eye on a few critical workflows.
7. Pocket Actions
Pocket Actions is a launcher:
- It lists every
workflow_dispatchworkflow across all your repositories on one screen, and you can pin the repos you use most. - A workflow without inputs runs with one tap. One with inputs takes a couple more taps.
- The input form is built automatically from the workflow's
workflow_dispatchinputs. If GitHub's API doesn't return them, the app reads the workflow YAML. - It can also run Google Apps Script web apps from the same screen.
- There's no login and no backend. You paste a PAT with the
reposcope, and the token is stored only in secure storage on your device, never on the developer's servers. The in-app setup guide opens GitHub's token page with the scope already selected.
Pros
- Few taps, with everything you trigger often on one screen, across repositories.
- Nothing to build or maintain for each workflow (unlike Shortcuts).
- GitHub Actions and GAS in one place.
Cons
- No logs or run results. The app only confirms that GitHub accepted the request. You check the outcome in GitHub or GitHub Mobile.
- Free use is capped at 5 runs a day and 17 a week. Unlimited runs need Premium.
- Organizations that restrict third-party tokens may require admin approval.
- iPhone only for now. The Android app is in closed testing on Google Play.
Best for: People who trigger many workflows (or GAS scripts) on demand and want them one tap away.
How the options compare on credentials
Because this is about handing over access to your code, it deserves its own section.
Scroll sideways to see the whole table
| Option | What you hand over | Where it lives |
|---|---|---|
| GitHub Mobile / Safari | Your GitHub sign-in | GitHub's own app or browser session |
| iOS Shortcuts | A PAT you paste into the shortcut | Inside the shortcut definition |
| Third-party apps (Acts, GitFlow, Widget, Pocket Actions) | Depends on the app: sign-in or PAT | Per app. Check each listing and privacy policy |
| Pocket Actions specifically | A PAT with the repo scope | iOS secure storage on the device only. Removed when you log out or delete the app |
Practical tips that apply to every option:
- Prefer fine-grained tokens limited to the repositories you need, with an expiry date.
- If you lose your phone, revoke the token in GitHub → Settings → Developer settings first.
- For company repositories, follow your organization's policy. Some orgs block third-party tokens or require SSO authorization.
Which one fits you?
- You mostly review PRs and occasionally run or re-run a workflow → GitHub Mobile is enough.
- You want to watch runs and react to failures → GitHub Mobile notifications, Acts, or GitFlow. Add the Widget if you want status on your Lock Screen.
- You have one or two workflows and like building things → An iOS shortcut is free and fast. Use a narrowly scoped token.
- You trigger many workflows across repos, or also run GAS scripts, and want them one tap away → Pocket Actions.
- Your company forbids third-party tokens → Stick with GitHub Mobile or Safari.
A combination that works well
Starting and watching are different jobs, so many people pair tools:
- Start runs from a launcher (Pocket Actions or a shortcut).
- Get notified of failures by GitHub Mobile's push notifications (failures only).
- Glance at status with a widget if a few workflows really matter.
This keeps each tool simple, and you never need to dig through menus just to press "Run".
A real example: running AI jobs on demand to save money
One App Store review describes using Pocket Actions to trigger workflows that run AI-based stock fundamental analysis and email cleanup:
"I can run them with one quick tap whenever something catches my eye… Running AI automatically all the time costs too much, but since triggering is this easy, I lowered the frequency of the automatic runs and saved money."
(Translated from Japanese. This is a user's review, not the author's experience.)
As the developer, I use it for an automation that has AI evaluate stocks I'm curious about, run only when I need it.
The general lesson holds whichever tool you use. You don't have to drop cron. Keep schedules for work that must happen at a set time, and trigger the rest on demand. For AI workflows that call paid APIs, every scheduled run you skip is money you don't spend.
Getting started: a minimal workflow_dispatch workflow
All seven options need the workflow to declare workflow_dispatch. A minimal example with one input:
name: Redeploy
on:
workflow_dispatch:
inputs:
environment:
description: "Where to deploy"
type: choice
options: [staging, production]
default: staging
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: echo "Deploying to ${{ inputs.environment }}"
Commit this to the default branch, and it appears as runnable in GitHub Mobile and in the browser. Pocket Actions currently dispatches on the main branch, so it works when that is your default branch. In Pocket Actions, the choice input shows up as a selectable field. With a shortcut, you'd add the inputs object to the JSON body yourself.
Try it free
Pocket Actions is free on the App Store, with 5 runs a day (17 a week) at no cost. Paste a token, pin your repositories, and see whether the shorter path fits your routine.
- Download on the App Store (free)
- Pocket Actions website
- Changelog: see what's been fixed and shipped
FAQ
Can the official GitHub app run workflow_dispatch workflows?
Yes. Since July 2024, GitHub Mobile can manually run workflow_dispatch workflows from the Workflow view. It also shows logs and can notify you when a run finishes.
Why doesn't my workflow show a "Run workflow" button?
The workflow must declare the workflow_dispatch trigger, the file must be on the default branch, and you need write access to the repository.
Is it safe to give a PAT to a third-party app?
Use the minimum scopes and set an expiry. Pocket Actions needs only repo (the workflow scope isn't needed), stores the token only on your device, and doesn't send it to the developer's servers. Revoke the token in GitHub settings if your phone is lost.
Can Pocket Actions show logs or tell me if the run failed? No. It confirms the run was accepted. Use GitHub or GitHub Mobile, which can notify you of failures, to see results.
Does it work with workflow inputs?
Yes. It builds an input form from the workflow's workflow_dispatch inputs.
Can I trigger a workflow with Siri? With an iOS shortcut that calls the GitHub REST API, yes. The other options are tap-based.
How much does Pocket Actions cost? It's free for 5 runs a day and 17 a week. Premium removes the limits for $2.99/month or $49.99 lifetime.
Related
- iPhone Apps for GitHub Actions Compared
- How to Run Google Apps Script from Your Phone: 7 Methods Compared
Last checked: 2026-11-01 (App Store listings, GitHub docs and changelog, Pocket Actions pricing). Details of third-party apps can change, so check their listings before deciding.
