A lot of small automation tasks get solved by subscribing to a SaaS tool. You pay $10 or $20 a month, connect an account, and move on. That's fine when the tool does a lot. It's harder to justify when the tool is really just "run this small script on a schedule and send me a message if something happens."
GitHub Actions already runs on a schedule, has free minutes for public and light private use, and doesn't need a server. Over time I moved a handful of small tools off paid plans and onto workflows instead. Here are five of them.
1. Website uptime monitoring
Paid uptime monitors usually check a handful of URLs every few minutes and alert you if one goes down. That's a simple enough job for a scheduled workflow: ping the site, check the response code, and send an alert to Discord, Slack, or Telegram if it fails.
I wrote a full walkthrough of building this one, including the alerting setup, in this uptime monitor guide. If you'd rather skip the build, there's also a ready-to-use template that's free to grab.
2. Social media posting
Scheduling tools for social platforms are usually priced around how many accounts or posts you need per month. If you're only managing one or two accounts, that's a lot of money for something that's really just "post this on a timer."
I replaced mine with a workflow that generates a post using an LLM and publishes it to Bluesky on a schedule, with some basic rules for topics and posting frequency. The full setup is in this Bluesky automation guide, and there's also a ready-made bot if you want the free version without building it yourself, or a more advanced version that can also reply, like, and follow based on keywords.
3. Scheduled data pulls and reports
A lot of "reporting" tools are just a script that hits an API, formats the result, and emails or posts it somewhere. If you already know what data you want and where it should go, a workflow triggered on a cron schedule does the same job without a subscription.
The part that trips people up here is usually not the scheduling — it's understanding what's actually happening when one system needs to notify another. If that's fuzzy, this explanation of webhooks is worth reading before you build anything that needs to react to an event instead of just running on a timer.
4. Dependency and security checks
Several paid tools exist just to tell you when a dependency is out of date or has a known vulnerability. GitHub Actions can run these checks directly, using free tools like pip-audit, npm audit, or Dependabot, and open an issue or send a notification when something needs attention.
This one's less about building something custom and more about not paying for a wrapper around a check you can already run for free in a workflow.
5. Simple internal APIs and triggers
Some of what I was paying for wasn't really automation — it was just a way to trigger something from outside my own systems. A workflow with a workflow_dispatch trigger, or one triggered by an external webhook, does the same job.
Related: if you're not sure whether you actually need something this custom or whether a no-code tool would get you there faster, this comparison of Zapier and GitHub Actions walks through the actual tradeoffs in cost, setup time, and flexibility.
Where this doesn't work
None of this is free in the way "free" sometimes gets used. GitHub Actions has usage limits, and workflows need someone to maintain them when an API changes or a script breaks. A paid tool with a support team and a polished dashboard is still worth it if the task is complex or the failure cost is high.
But for the kind of task that's really just "check this, then do that, on a schedule" — a lot of what people pay for monthly is a workflow you can write once and forget about.
More build notes like this over at Procwire.
Top comments (0)