Barside
Download
Barside/Content/Intelligence · AI agents

Intelligence · AI agents

The cheapest way to run scheduled AI jobs without paying per task

Use a runner that bills nothing per step: a scheduled GitHub Actions workflow within its included compute, a self-hosted n8n, a short Fly.io or Cloud Run job, or your own computer. Your AI company still bills the tokens on every route.

Feature guideUpdated 16 min read

The cheapest way to run scheduled AI jobs without paying per task is a runner that bills nothing per step: a scheduled GitHub Actions workflow inside its included compute, a self-hosted n8n Community edition, a short job on Fly.io or Google Cloud Run billed by compute time, or a scheduler on your own computer. Zapier counts tasks for action steps, Make counts credits for operations, and n8n Cloud counts one execution per whole run. On every route, the AI model you call is a second bill, and moving the job does not remove it.

Everything about other products on this page comes from their own pricing pages and documentation as we read them in November 2026. We ran no tests and took no screenshots, and every monthly total below is a worked example with assumed run counts. We make Barside, a free desktop app for Windows, Linux and Mac, and the second half of the page says what it does for scheduled AI jobs and where it stops.

Running scheduled AI jobs without paying per task, route by route

Each route meters something different. The table sums up what each vendor's own page says, as of November 2026, and the sections below link the page behind every line.

RouteWhat it countsFree allowance on the vendor's pageSuits
ZapierTasks: each successful action step; triggers do not countFree plan: 100 tasks a month, two-step ZapsFew runs with few steps
MakeCredits: most actions use 1 creditFree plan: 1,000 credits a monthShort scenarios
n8n CloudExecutions: one per whole workflow runA trial with 1,000 executionsLong workflows at a steady rate
n8n Community edition, self-hostedNothing per runFree without a license key; you pay for the serverPeople who keep a server running
GitHub ActionsRunner minutes, priced per minuteFree on standard runners in public repositories; US$12 of compute a month on GitHub FreeJobs that can start a few minutes late
Google Cloud Run job with Cloud SchedulerEach job instance's lifetime (instance-based billing)Not confirmed for jobs; the Free Tier page lists request-based limitsContainer jobs on Google Cloud
Fly.io MachineSeconds a Machine runs, plus storage while stoppedNo free tier for new organizationsContainer jobs about once an hour or a day
Your own computerNothing per runYour computer and its powerJobs that can wait until the computer is on

The meter decides how the bill grows. On per-step meters, a job that calls the model, saves the result and sends a message costs more each time you add a step. On per-run, per-minute and per-second meters, the number of runs and their length drive the bill, and extra steps matter only through the time they take.

Two bills: the runner and the AI model

A scheduled AI job has two costs, and it helps to price them apart. The first is the runner: the platform, server or computer that wakes the job up and runs its steps. The second is the AI model the job calls, which bills by the tokens it reads and writes.

If you call the model with your own API key, your AI company bills those tokens on every route in this guide, and moving the job from Zapier to GitHub Actions leaves that line as it was. Some platforms can supply the model themselves and fold it into their own meter. Zapier's pricing page says many actions cost more than one task, depending on step type, AI model tier and number of tool calls. Make's Credits page says that with Make's AI Provider, credits are based on tokens and operations, and with your own provider connection you pay Make for operations and your AI provider for tokens. Our comparison of AI features in Make, Zapier and n8n covers those AI meters in detail.

Keep the model as its own line when you compare routes, and cap it where it is billed: with a spending limit on your AI company account, and in Barside with the AI spending limit described below. This page leaves model prices out. Our guide to AI apps where you bring your own key explains how that billing works.

The cheapest way to run scheduled AI jobs, worked out for three schedules

The cheapest way to run scheduled AI jobs depends on how often the job runs and whether it has to run while your computer is off. To compare routes, take one job and three schedules. This is an example with assumed numbers: a job with a schedule trigger and three steps (fetch the input, call the AI model, save the result), where each run takes 2 minutes of compute. In a 30-day month, a daily schedule makes 30 runs, an hourly one 720 and a 15-minute one 2,880.

Runner (example)Every day: 30 runsEvery hour: 720 runsEvery 15 minutes: 2,880 runs
Zapier, assuming 3 tasks a run90 tasks2,160 tasks8,640 tasks
Make, assuming 4 credits a run120 credits2,880 credits11,520 credits
n8n Cloud, 1 execution a run30 executions720 executions2,880 executions
GitHub Actions, Linux 2-core at US$0.006 a minuteUS$0.36 of computeUS$8.64 of computeUS$34.56 of compute
Your own computerNo runner feeNo runner feeNo runner fee
The AI model, with your own keyYour AI company's billThe same on every routeThe same on every route

Set against each plan as of November 2026, the counts work out as follows.

  • Zapier. The Free plan has 100 tasks a month but allows two-step Zaps only, so this job with three actions needs a paid plan. Professional starts at US$19.99 a month billed annually, or US$29.99 billed monthly, for 750 tasks a month, which covers the daily schedule. The hourly and 15-minute schedules need a larger task tier on the same pricing page, and an AI step that uses more than one task makes every column grow.
  • Make. The daily schedule fits in the Free plan's 1,000 credits a month on Make's pricing page. The other two need a paid plan, and the text we could read on that page gave no paid plan prices, so we could not confirm them. The Credits page did not say whether a schedule trigger that finds no new data uses a credit, so four credits a run is our assumption.
  • n8n Cloud. Starter is 20€ a month billed annually for 2,500 executions, which covers the daily and hourly schedules. The 15-minute schedule passes Starter at 2,880 executions, and Pro is 50€ a month billed annually for 10,000.
  • GitHub Actions. On GitHub Free, private repositories include US$12 of compute a month, so the daily and hourly schedules fit inside it. The 15-minute schedule goes US$22.56 past it, which is billed to your payment method, or blocked if you have none.
  • Your own computer. No runner fee on any schedule, as long as the computer is on, awake and running the job at those times.
Newsletters in, social posts out, every morning · Open the video

n8n in 2026: Cloud executions or the self-hosted Community edition

For self-hosted scheduled AI automation in 2026, n8n is a natural tool to weigh, because its Cloud plans and its self-hosted Community edition run the same workflows under different bills. n8n's pricing page counts executions on Cloud, and its FAQ says "An execution is a single run of your entire workflow," however many steps the workflow has and however much data it processes. Starter is 20€ a month and Pro 50€ a month, both billed annually, with 2,500 and 10,000 executions. The Cloud trial includes 1,000 executions and needs no credit card.

Self-hosted, the Host n8n documentation says "Without a license key, n8n runs as the free Community edition." We found no execution quota for it on that page or on the pricing page, so the cost moves to the server and the time you spend on it. The docs list a one-line setup that requires Docker on Linux or macOS (or WSL on Windows), and Docker Compose for production deployments with databases. They mark npm installation as deprecated from n8n 3.0. A self-hosted Business license is listed at 667€ a month billed annually, for teams that need its features.

Cloud vs self-hosted comes down to who keeps the server running. A workflow on n8n Cloud runs on n8n's servers at its scheduled times. A self-hosted n8n runs only while its server does, so a copy on your own computer has the same limits as any other job there, and a rented server adds its own bill. Our guide to Activepieces vs n8n for self-hosting covers n8n's license and what the Community edition leaves out.

Cheap cloud cron jobs on Fly.io and Google Cloud Run

For cheap cron jobs in a serverless container, Fly.io and Google Cloud Run both price compute by time, so a short job that runs and stops costs much less than a server that stays on all month. Their free allowances and schedulers differ.

Fly.io

Fly.io's resource pricing says Machines are "billed by the second while they're running," and only the root file system is billed while a Machine is stopped, at US$0.15 per GB a month. The smallest preset, shared-cpu-1x with 256MB of RAM, is listed at US$2.19 a month in its lowest-priced regions, Ashburn (iad) and Secaucus (ewr). As of November 2026, new organizations get no free tier or monthly free allowance, only US$1 of trial credit that lasts 7 days or until it is used up, and after the trial a credit card is needed to keep using billable resources. There is no monthly platform fee.

Fly.io's task scheduling guide covers four ways to run a job on a timer. A Machine can start hourly, daily, weekly or monthly, which the guide calls interval buckets for simple, low-frequency jobs, with no fine-grained control. Cron Manager is a small Fly app that starts a temporary Machine for each job and tears it down afterwards, and the guide calls it the most production-hardened option. Supercronic runs cron inside your app as a background process, and in-app scheduling uses a scheduler your app already has to start short-lived Machines.

As an example with assumed numbers, an hourly job that runs 2 minutes on that smallest Machine runs 24 hours in a 30-day month. That is a thirtieth of the US$2.19 monthly price, plus storage while the Machine is stopped, and it holds only if the Machine stops after each run.

Google Cloud Run

Cloud Run runs a container job on a schedule through Cloud Scheduler. Google's guide to running jobs on a schedule says "Cloud Scheduler will execute the Cloud Run job at the specified frequency," which you set in unix-cron format with a time zone. Google's Free Tier page lists, for Cloud Run's request-based billing, 2 million requests, 180,000 vCPU-seconds and 360,000 GB-seconds a month. Those limits are calculated per billing account, and you need a Google Cloud billing account to use them.

Google's billing settings page says "all Cloud Run jobs use instance-based billing," and for other billing setups, the Free Tier page points to the Cloud Run pricing page. Neither that page nor Cloud Scheduler's pricing page showed its prices in the tools we use, so we could not confirm the free allowance for jobs or what Cloud Scheduler charges. Do the arithmetic before you count on a free tier: in the example above, a run with 1 vCPU for 120 seconds uses 120 vCPU-seconds, so 720 runs use 86,400 and 2,880 runs use 345,600. Compare that with the allowance Google's pricing page shows for your setup.

GitHub Actions as a scheduler, and its catches

A scheduled GitHub Actions workflow can run a small job with no runner bill. GitHub's Actions billing page says standard GitHub-hosted runners are free in public repositories, and self-hosted runners are free and do not reduce the included usage. For private repositories, each plan includes compute as a dollar amount: US$12 a month on GitHub Free and GitHub Free for organizations, US$18 on Pro and Team, and US$300 on Enterprise Cloud, as of November 2026. A Linux 2-core runner costs US$0.006 a minute and a Linux 1-core runner US$0.002, so a job that mostly waits for an AI answer costs a third as much per minute on the smaller runner.

The schedule has rules worth knowing, from GitHub's page on events that trigger workflows:

  • The shortest interval is once every 5 minutes.
  • Scheduled runs can be delayed when GitHub Actions is busy, and under high enough load some queued jobs may be dropped.
  • Scheduled workflows run only on the default branch, in UTC by default or in a time zone you name.
  • In a public repository, scheduled workflows are turned off automatically after 60 days with no repository activity.

That suits a daily digest or a nightly cleanup that can start a few minutes late. For a job that must start at an exact minute, the delays above matter. A public repository also shows its code to everyone, so keep your AI key out of the code.

How Barside runs scheduled AI jobs on your computer

Barside runs scheduled AI jobs on your own computer with no fee per run or per step. Barside is free on Windows, Linux and Mac and has no AI of its own: each run uses the AI you connect in Settings → AI, and that company bills the tokens. A Claude or ChatGPT plan can run agents on your computer too, through Claude Code or Codex with My plan. There are two kinds of scheduled AI jobs:

  • Scheduled agents write a note at set times from your open tasks, reminders, recent notes, calendar events and Library search, and can also read what came into Reading since the last run. Presets include Morning briefing (weekdays at 8:30 AM) and Weekly review (Fridays at 4:00 PM). The agent writes its own note by itself, and any reminder, task or email draft it suggests waits for your approval. AI agents that ask before they act covers every agent.
  • Saved workflows repeat a job the AI assistant did once. A scheduled workflow never starts by itself: at its time it asks in Agents & approvals → Inbox, and it runs when you press Approve.

To schedule a workflow:

  1. Connect an AI in Settings → AI. Under AI spending limit, turn on Limit what Barside's AI spends.
  2. Give the assistant the job once, for example "Take the newest item in Reading's Newsletters and write three short social posts as notes in Marketing," and let it finish.
  3. Under its last reply, choose Save as workflow, keep or change the Workflow name, and press Save workflow.
  4. Open Agents & approvals → Workflows, choose Schedule on the card, pick Every day, Weekdays, Weekly or Monthly and a time, tick Ask me to run it on this schedule, and press Save schedule.
  5. At that time, a "Run workflow" item waits in Agents & approvals → Inbox. Press Approve to start it, or Refuse and nothing runs.

The spending limit is Barside's side of the token bill. You set an amount from US$0.50 to US$10,000 for a day, a week (from Monday) or a month, Barside shows a notification at 80%, and at the limit its AI stops sending requests. Each computer counts its own use, so set a limit on your AI company account as well, because its bill is the final word.

Take Marco, an example freelance writer whose computer is on from 8 to 6 on weekdays. His newsletter workflow, scheduled on Weekdays at 9:00, costs him only the tokens his AI company bills, and the Weekly review agent writes its note on Fridays at 4:00 PM. Neither job needs a server, a task plan or a cloud account. The saved workflows guide walks through every option.

What Barside does not do for scheduled jobs

  • Nothing runs while the computer is off, asleep or locked. Afterwards, only the latest missed run is made up, and only if it was planned within the last 12 hours. Older ones are logged as skipped in History.
  • A scheduled workflow waits for you. It starts only after Approve in the Inbox, so it suits jobs you look at each day. A job that has to finish unattended at 3 AM belongs on another route.
  • Schedules repeat every day, on weekdays, weekly or monthly, at a time you pick. The hourly and 15-minute examples above belong on one of the other routes.
  • No triggers from web apps. Barside has no app-to-app connectors or webhooks, so nothing fires on a new email or form entry. Zapier, Make or n8n fit those jobs, and the Zapier alternatives guide compares them for one person.
  • Limits. Up to 50 scheduled agents and 100 saved workflows, and one AI-backed agent runs at a time while the others wait.
  • Running while your computers are off costs extra. Cloud agents, part of Barside Plus at US$20 a month or US$200 a year plus sales tax, run your scheduled agents on Barside's server at their times. They need cloud sync and an API key, and the server checks every five minutes, so a run may start a few minutes after its time. Saved workflows and the meeting agent stay on your computer, and cloud runs are not counted by the AI spending limit in Settings → AI.

Privacy: where a scheduled job's data goes

On every route, the text you send the model goes to the AI company you call, under its data policy. On a hosted runner, such as Zapier, Make, n8n Cloud, GitHub's runners, Cloud Run or Fly.io, the job's inputs also pass through that host. A self-hosted n8n keeps the workflow's data on the server you run.

In Barside, saved workflows and scheduled agents are stored in your library on your computer, and a workflow's recorded steps leave out typed passwords, keys, tokens and card numbers, marked [removed]. When a job runs on your computer, the request and the notes it reads go to your AI company. Notes and workspaces you leave out of Library AI, in Library & briefing → Sources, are never given to an agent. With cloud agents, Barside's server can read your synced notes, which is how it runs your agents. Read how agents use your data.

Works well with

Barside runs on Windows, Linux and Mac, and you can download it free.

FAQ

Questions and answers

What is the cheapest way to run a scheduled AI job?

For a job that can wait until your computer is on, a scheduler on your own computer has no runner fee, and in Barside a scheduled agent or saved workflow costs only the tokens your AI company bills. For a job that must run at any hour, a scheduled GitHub Actions workflow is free on standard runners in public repositories, and private repositories on GitHub Free include US$12 of compute a month as of November 2026. The AI model is a separate bill on every route.

Does GitHub Actions charge for scheduled workflows?

Scheduled runs use runner time like any other run. As of November 2026, GitHub's billing page says standard GitHub-hosted runners are free in public repositories. Private repositories include compute as a dollar amount, US$12 a month on GitHub Free, and a Linux 2-core runner costs US$0.006 a minute. Scheduled runs can be delayed under high load, and the shortest interval is every 5 minutes.

Is the self-hosted n8n Community edition free?

n8n's hosting docs say that without a license key, n8n runs as the free Community edition. You pay for the server it runs on and the time to keep it updated, and your AI company bills the tokens. We found no execution quota for it on n8n's hosting or pricing pages. n8n Cloud counts executions instead: Starter is 20€ a month billed annually for 2,500, as of November 2026.

Does n8n count every step of a workflow?

No. n8n's pricing page says an execution is a single run of your entire workflow, however many steps it has and however much data it processes. So a long scheduled workflow uses no more of an n8n Cloud allowance per run than a short one, while per-step meters such as Zapier's tasks or Make's credits grow with each step.

Is Fly.io or Google Cloud Run cheaper for a cron job?

It depends on your allowance and how long each run takes. Fly.io bills a Machine by the second while it runs, has no free tier for new organizations, and lists its smallest Machine at US$2.19 a month as of November 2026. Google's Free Tier page lists Cloud Run limits for request-based billing, but Cloud Run jobs use instance-based billing, and that allowance is on a pricing page we could not read, so check it there. For both, multiply runs by seconds and compare.

Do Barside's scheduled agents run when my computer is off?

Not on your computer. Nothing runs while it is off, asleep or locked, and afterwards only the latest missed run from the last 12 hours is made up. With Barside Plus (US$20 a month or US$200 a year, plus sales tax), cloud agents run your scheduled agents on Barside's server at their times. Saved workflows stay on your computer.

Is Barside free?

Yes. Barside is free on Windows, Linux and Mac, with scheduled agents, saved workflows and the approval inbox included. Each run uses the AI you connect in Settings → AI, and that company bills you, or you can use a Claude or ChatGPT plan through My plan. Barside Plus is optional and adds cloud agents, cloud sync and encrypted cloud backup.

Sources

Where the facts come from

Checked on November 10, 2026. Products change: if something here is out of date, tell us at support@barside.space.

  1. GitHub Docs: GitHub Actions billing
  2. GitHub Docs: Events that trigger workflows
  3. Google Cloud: Free Google Cloud features and trial offer
  4. Google Cloud: Execute jobs on a schedule (Cloud Run)
  5. Fly.io Docs: Resource pricing
  6. Fly.io Docs: Task scheduling guide with Cron Manager and friends
  7. n8n Plans and Pricing
  8. n8n Docs: Host n8n
  9. Zapier pricing
  10. Make pricing
  11. Make Help Center: Credits
  12. Billing settings for services - Cloud Run docs, Google Cloud