Run Your Automations from iPhone: Shortcuts vs Zapier, Make, IFTTT, n8n
Disclosure: I'm the developer of Pocket Actions, one of the tools compared here. Pricing and free-tier details come from each vendor's official page (linked) as of the "last checked" date. Anything I couldn't confirm there is marked unconfirmed.
Sometimes you don't want "automatic" — you want a button
Most automation platforms are built around triggers: a new email, a form submission, a schedule. But a lot of personal automation is different. You don't want it running all the time; you want to fire it once, from your phone, when you decide:
- a report or analysis you only need occasionally
- "deploy", "back up", or "send the update" while you're away from your desk
- a job that costs money every run (say, an AI API call), which you'd rather not put on a cron schedule
So the question isn't "which automation platform is best?" It's "what's the easiest way to trigger my automation from an iPhone?" Here's how the common options compare for that job.
How to choose
- How you build the automation: no-code builder, or your own code (a GitHub Actions workflow, a Google Apps Script)
- How easy it is to start from the phone: Home Screen, widget, taps, passing inputs
- Cost model: what's free, and whether usage is counted per task, per credit, or per run
- Where it runs and what accounts you need: their cloud, your server, or your existing GitHub/Google account
Comparison table
Scroll sideways to see the whole table
| Tool | How you build | Free tier (official) | Paid starts at (official) | Strongest at |
|---|---|---|---|---|
| iOS Shortcuts | Actions on the iPhone; can call web APIs | Built into iOS | — | On-device tasks; launch from Home Screen, Siri, Action button, Back Tap |
| Zapier | No-code, 9,000+ apps | 100 tasks/mo, two-step Zaps; webhooks are paid-only | Pro $19.99/mo billed annually (750 tasks), $29.99 monthly | Always-on SaaS-to-SaaS automation |
| Make | Visual no-code scenarios | 1,000 credits/mo | Unconfirmed (not shown in the official page content I could read) | Complex branching no-code flows |
| IFTTT | Trigger + action Applets | 1,000 credits/mo, hourly polling | Starter $2.09/mo, Pro $5.49/mo, Pro+ $13.99/mo | Smart home and light personal automations; has iOS/Android apps |
| n8n | No-code plus JS/Python code steps | Self-hosted Community Edition (you run the server) | Cloud Starter €20/mo billed annually | Powerful workflows and AI agents, self-hosted |
| Pocket Actions | Runs your own GitHub Actions (workflow_dispatch) and Apps Script web apps | 5 runs/day, 17/week | Premium $2.99/mo or $49.99 lifetime | Manually firing automations you already have, in 1–3 taps |
Notes:
- Zapier prices are the annual-billing monthly equivalent; Professional has a 14-day free trial (Zapier pricing).
- I couldn't confirm whether Zapier, Make, or n8n offer an official iPhone app or one-tap mobile trigger — unconfirmed. Any of them can be started by a webhook, which you can call from an iOS Shortcut (on Zapier, webhooks require a paid plan).
The options, one by one
iOS Shortcuts
Already on your iPhone. Shortcuts can run from the Home Screen, a widget, Siri, Control Center, the Action button, or Back Tap, and can call web APIs (Apple's Shortcuts User Guide).
- Pros: free, no extra app, many ways to launch, mixes with on-device data.
- Cons: to trigger GitHub Actions or Apps Script you build the request yourself — URL, headers, token, JSON body — and any input prompts by hand.
- Good for: people comfortable wiring up an API call. Honestly, for some readers this is enough.
Zapier
The default no-code automation platform. The free plan gives 100 tasks a month and two-step Zaps; webhooks and multi-step Zaps need Professional or higher (pricing).
- Pros: huge app catalog, strong error handling and replay.
- Cons: for an occasional "press a button" job, the free tier lacks webhooks and paid plans are a monthly bill.
- Good for: connecting work SaaS apps that should run on their own.
Make
A visual scenario builder. Free includes 1,000 credits a month; most module actions use one credit (pricing).
- Pros: fine-grained control over branching and data shaping.
- Cons: credits scale with steps, so long scenarios use them up quickly. Paid prices: unconfirmed here.
- Good for: no-code users who outgrow Zapier's simpler flows.
IFTTT
"If this, then that" Applets. Free has 1,000 credits a month with hourly polling; paid plans poll every 15 or 5 minutes. You can subscribe through its App Store or Google Play app (plans).
- Pros: the cheapest paid tiers here, many smart-home and consumer services, webhooks available.
- Cons: not built for complex logic or running your own code.
- Good for: quick, lightweight personal automations.
n8n
No-code canvas plus JavaScript/Python code steps, billed per workflow execution regardless of step count. Cloud Starter is €20/month billed annually; the self-hosted Community Edition is available on GitHub (pricing).
- Pros: very flexible, AI agents and MCP built in, cheap if you self-host.
- Cons: free means running and maintaining your own server.
- Good for: people who can operate a server and want serious workflows — a common Zapier alternative for developers.
Pocket Actions
An iPhone app that runs GitHub Actions workflows (workflow_dispatch) and Google Apps Script web apps you already wrote, in 1–3 taps. It doesn't build automations; it's the button for automations you already have.
- Pros:
- No server, no automation subscription, no Pocket Actions account.
- It builds an input form automatically from your workflow's
inputs. - Your GitHub token (PAT) is stored only in the device's secure storage.
- The actual work runs on GitHub Actions or Apps Script.
- Cons:
- You write the automation yourself as a workflow or Apps Script (many people have AI write it). It's not no-code.
- iOS only; Android is in closed testing.
- Free tier: 5 runs per day, 17 per week.
- GitHub Actions runs always use the
mainbranch. - For Apps Script, it shows "success" once the call is accepted, even if your script throws an error. Check results on the GAS side.
- No run results or logs inside the app.
- Good for: anyone who already automates with GitHub Actions or Apps Script and wants to trigger it from an iPhone quickly.
- Not for: people who don't want to write code, or who need SaaS apps wired together automatically — use Zapier, Make or IFTTT.
How each tool actually starts a GitHub workflow or an Apps Script
Every option above ends up doing the same thing underneath: an HTTP request to GitHub's API or to an Apps Script web app URL. The difference is who builds that request, where the credentials live, and what it costs per run. Below is the minimal setup for each, so you can judge the effort honestly.
The two targets
GitHub Actions — a workflow with a workflow_dispatch trigger, started by POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches (REST docs):
# .github/workflows/report.yml
name: Report
on:
workflow_dispatch:
inputs:
ticker:
description: "Symbol to check"
type: string
required: true
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: python report.py "${{ inputs.ticker }}"
curl -X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer $GITHUB_TOKEN" \
https://api.github.com/repos/OWNER/REPO/actions/workflows/report.yml/dispatches \
-d '{"ref":"main","inputs":{"ticker":"AAPL"}}'
Per GitHub's current REST docs, a successful workflow dispatch returns 200 with workflow_run_id, run_url and html_url (docs). Whether older API versions still return an empty 204 is unconfirmed, so treat any 2xx as success. Every tool in this article has to send exactly this.
Apps Script — a script deployed as a web app, with a doGet(e) or doPost(e) function (web apps guide):
function doGet(e) {
const name = (e.parameter.name || 'world');
// ...your actual work: update a sheet, send a mail, etc.
return ContentService
.createTextOutput(JSON.stringify({ ok: true, name: name }))
.setMimeType(ContentService.MimeType.JSON);
}
Deploy → New deployment → type Web app, choose who it runs as and who has access, then copy the /exec URL. A plain GET to that URL runs doGet. Google answers with a redirect, so command-line clients need to follow redirects (curl -L).
iOS Shortcuts
- Ask for Input (Text) → prompt "Ticker".
- Dictionary → key
ref=main; keyinputs= a nested Dictionary withticker= Provided Input. - Get Contents of URL → the dispatches URL, Method POST, Headers
Accept,Authorization: Bearer <token>, Request Body JSON → the Dictionary. - Show Notification → "Started".
For Apps Script it's even shorter: Get Contents of URL on the /exec URL with ?name=... appended, then Show Result to see the JSON your script returns. Shortcuts follows the redirect for you.
Effort: about ten minutes per button once you know the actions. Cost: nothing. Weak spot: the token sits in a Text field inside the shortcut, and you rebuild the input UI by hand for each workflow.
Zapier
Zapier's HTTP step is Webhooks by Zapier, which isn't on the free plan (pricing). A typical "button" Zap:
- Trigger: a manual trigger such as a Zapier button or a form (exact trigger options vary by plan; check your account).
- Action: Webhooks by Zapier → Custom Request, method POST, the dispatches URL, the same headers, and the JSON body.
- Store the token in the step's header field. Zapier keeps it on their servers.
Effort: low if you already pay for Zapier. Each run counts as tasks. For one button you press a few times a week, you're paying a monthly fee for one HTTP call.
Make
- Create a scenario with a trigger (a Webhooks → Custom webhook module gives you a URL you can hit from the phone).
- Add HTTP → Make a request: POST, the dispatches URL, headers, JSON body.
- Turn the scenario on and call the custom webhook URL from Safari or a Shortcut.
Each module run uses credits (pricing), so this two-module button costs about two credits per press. That's fine on the free 1,000, but you've now added a second URL (the Make webhook) that anyone can call if it leaks.
IFTTT
IFTTT's Webhooks service can both receive a request and make one (Webhooks service). A button setup:
- If: Button widget pressed (from the IFTTT app), or a Webhooks "Receive a web request" trigger.
- Then: Webhooks → Make a web request, POST, content type
application/json, the body, and additional headers.
Whether custom headers like Authorization are available on every plan is unconfirmed here; check the action in your account before you count on it.
n8n
- Webhook node (gives you a production URL) → HTTP Request node.
- In the HTTP Request node, store the GitHub token as a credential (Header Auth) instead of pasting it into the node, so it isn't exported with the workflow.
- Activate the workflow; call the webhook URL from a Shortcut.
Self-hosted, there's no per-run fee, but the button only works while your server is up. On n8n Cloud, each press is one execution against your plan (pricing).
Pocket Actions
- Create a classic PAT with the
reposcope (workflowisn't needed because the app never edits workflow files). A fine-grained PAT with Actions read/write and Contents read is supported in code but hasn't been tested on a device yet. - Paste it once; it stays in the device's secure storage.
- Pick the repository and workflow. The
tickerinput becomes a text field automatically. For Apps Script, add the/execURL.
There's no middle server: the phone calls GitHub or Google directly, and the work runs there.
Pitfalls that hit every option
Scroll sideways to see the whole table
| Problem | Where it shows up | What to do |
|---|---|---|
404 from GitHub | Any tool calling the API | The token can't see the repo, or the path is misspelled. GitHub uses 404 for private resources you can't access (troubleshooting) |
422 "does not have 'workflow_dispatch' trigger" | Any tool | The workflow on ref lacks the trigger; merge it |
| Inputs sent as numbers or booleans fail | Zapier/Make/n8n JSON builders | Send input values as strings, the way the curl example does, unless you've confirmed typed values work |
| Apps Script change "doesn't take effect" | Every GAS caller | The /exec URL serves the deployed version. Edit the deployment and choose New version (deployments guide) |
| Apps Script returns an HTML login page | Every GAS caller | The web app's access setting requires sign-in; the caller isn't signed in |
| Button "worked" but nothing happened | Anything with a middle layer | Check the run history in each layer: tool → GitHub Actions tab / Apps Script executions |
(Exact error message wording isn't documented; treat the quoted text as typical, unconfirmed.)
Security: where your token ends up
- Shortcuts: inside the shortcut on your device (and in iCloud if shortcuts sync). Don't share that shortcut.
- Zapier / Make / IFTTT / n8n Cloud: on the vendor's servers, next to your other connections.
- Self-hosted n8n: on your server; its security is your job.
- Pocket Actions: only in the device's secure storage; no Pocket Actions server or account.
Whatever you choose, give the token the least access that works: a fine-grained token for one repository where your tool supports it, or a classic token you can revoke quickly. For Apps Script, a web app set to "Anyone" can be run by anyone who has the URL, so add a shared-secret parameter and check it in doGet if the script does anything you wouldn't want strangers to trigger.
Which should you pick?
- No code, connect SaaS apps: Zapier (work), Make (complex flows), IFTTT (cheap and light).
- You run servers and want power: self-hosted n8n.
- On-device tasks, or you're happy building API calls: iOS Shortcuts.
- Your automation already lives in GitHub Actions or Apps Script and you want a one-tap trigger: Pocket Actions. Shortcuts can do the same job; Pocket Actions just saves you building the request, the input prompts and the token handling.
A real example
As the developer, I use Pocket Actions to run an automation that has AI evaluate stocks I'm curious about — only when I need it, not on a schedule.
Try it free
If your automations live in GitHub Actions or Apps Script, you can try it free for up to 5 runs a day.
View Pocket Actions on the App Store
FAQ
Can iOS Shortcuts trigger GitHub Actions?
Yes. A shortcut can send a workflow_dispatch request to the GitHub API. You build the URL, headers, token and inputs yourself.
Does Zapier's free plan include webhooks? No. Per Zapier's pricing page, webhooks are on Professional and above. Free includes 100 tasks a month and two-step Zaps.
What's a cheaper Zapier alternative? Per official pricing pages, IFTTT paid plans start at $2.09/month and n8n's self-hosted Community Edition is free (you run the server). They're good at different things, so pick by use case.
Is Pocket Actions a Zapier alternative? Not really. It doesn't build automations; it triggers ones you wrote in GitHub Actions or Apps Script.
Is Pocket Actions on Android? Not yet. It's iOS only; Android is in closed testing.
Related
- How to Trigger GitHub Actions from Your iPhone: 7 Options Compared
- How to Run Google Apps Script from Your Phone: 7 Methods Compared
- GitHub Actions iPhone apps compared
- Pocket Actions changelog
Last checked: 2026-11-01 (Apple Shortcuts User Guide; official pricing pages of Zapier, Make, IFTTT and n8n). Pricing changes, so verify before deciding.
