Flow's Scheduled Trigger or an External Cron Job for Shopify?
Flow's Scheduled trigger is a CUSTOMIZE, not a drop-in cron replacement: the trigger runs at most once every 10 minutes, and one year is the longest interval it supports. Keep Flow for every schedule from 10 minutes up, free on Basic through Plus. Put a genuine sub-10-minute sync on an external scheduler calling the Admin API, where Plus gets 1,000 points/second.
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's Scheduled time trigger reference: the trigger is limited to run a maximum of one time every 10 minutes, the longest interval possible for repeating workflows is one year, and the amount must be a whole number because decimals are not supported (verified Sep 2026). Read the Flow help page: Flow is a free app on Basic, Grow, Advanced and Plus, Send HTTP Request is available from Grow upward, and only Plus stores can use tasks created by custom partner apps. Read the troubleshoot page for the 1,000-workflow ceiling, the warning at more than 10 active workflows on the same trigger, and the 36-hour execution limit per workflow section. Fetched the Zapier and Make App Store listings: Zapier carries 3.7★ across 56 reviews, Make 1.0★ across 3. Celigo has no App Store listing at all; its Shopify integration is installed and run from Celigo's own platform, so it is named here as an off-platform lane rather than an app. Build bands are Deploi estimates.
- Reference scenario
- $20M–$200M GMV · Shopify Plus · an ERP or 3PL inventory sync that ran every 5 minutes under cron · 15–40 live Flow workflows · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Hourly or slower (reports, digests, reminders, nightly jobs) | WAIT | Flow's Scheduled trigger already covers this at no cost, on every plan from Basic upward. Set a whole-number interval, wire the actions, and skip the scheduler conversation entirely. |
| Every 10 to 30 minutes, with an outbound call to your own system | CUSTOMIZE | Flow triggers the schedule and Send HTTP Request (Grow, Advanced and Plus) posts to your endpoint, waiting up to 30 seconds for a response code and retrying 4XX, 5XX and 429 errors for up to 24 hours. You build only the endpoint on the far side. |
| Sub-10-minute sync, no dev bench | BUY | An iPaaS scheduler runs on its own clock below Flow's floor. Zapier's Professional plan costs $29.99/month and Team $103.50/month (verified Sep 2026), which beats standing up a service you then have to operate. |
| Sub-10-minute sync at Plus volume against an ERP or 3PL | BUILD | The reference scenario. A worker you own runs on any interval, batches its reads, and uses the Plus GraphQL Admin API allowance of 1,000 points/second against 100 on standard plans. Metered iPaaS pricing turns hostile at a 5-minute cadence across thousands of SKUs. |
What Flow Scheduled Triggers Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | A schedule that matches the warehouse's rhythm removes the manual reconciliation an ops team otherwise runs by hand every morning after an overnight drift. |
| Revenue — indirect | Medium | Stock and price data refreshed every few minutes rather than every hour cuts the window in which the storefront sells an item the warehouse has already shipped elsewhere. |
| Customer experience | Medium | Oversell cancellations are the most damaging kind of post-purchase email, and sync latency is the variable that produces them. |
| Data & insight | Medium | A worker you own writes every sync run, payload and failure into your warehouse, where Flow's own history disappears after 14 days. |
Spend ceiling: Size the spend to the cost of stale data, not to the elegance of the scheduler. If a 10-minute lag never produces an oversell, Flow's free trigger is the whole answer and the budget is zero. If a 5-minute lag does, a worker at $6,000–$18,000 (Deploi estimate, illustrative) is cheap against a season of cancellations.
What buying enables (top apps)
- + Sub-10-minute schedules running this afternoon, with no service to host or operate
- + Hundreds of prebuilt connections into the SaaS tools the job also has to touch
- + A free or entry tier that lets you prove the cadence matters before committing budget
What building additionally unlocks
- + Any cadence you choose, including the once-a-minute loops no scheduler product prices sensibly
- + Batched reads against the Plus allowance of 1,000 points/second, plus bulk queries for catalog-wide sweeps
- + A permanent run log in your own warehouse, outliving Flow's 14-day retention and any vendor dashboard
- + A reconciliation sweep that catches what the fast loop misses, which Shopify's own webhook guidance recommends
Find Your Verdict in 3 Questions
Does the job genuinely need to run more often than every 10 minutes?
Yes: Go to question 2.
No: Your verdict: WAIT — Flow's Scheduled trigger covers every interval from 10 minutes to one year, free on Basic through Plus.
Do you have a dev bench that can host and operate a small scheduled service?
Yes: Go to question 3.
No: Your verdict: BUY — an iPaaS scheduler runs below Flow's floor from $29.99/month on Zapier Professional (verified Sep 2026), with no service to operate.
Does the sync touch enough records that metered task pricing would scale with your catalog?
Yes: Your verdict: BUILD — a worker batching Admin API calls at the Plus allowance of 1,000 points/second costs $6,000–$18,000 once (Deploi estimate, illustrative) instead of scaling forever.
No: Your verdict: BUY — a metered scheduler is cheaper than operating your own for a small, stable job.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A Zapier or Make schedule is live in an afternoon on a free or entry tier; your own scheduled worker is a 2–5 week project at $6,000–$18,000 (Deploi estimate, illustrative). | ||
| Recurring fees | Zapier bills $29.99–$103.50/month and Make $10.59–$34.12/month for as long as the schedule runs (verified Sep 2026); a worker you own costs hosting plus upkeep, and Flow itself stays free on every plan. | ||
| Maintenance & upgrades | The iPaaS vendor absorbs Shopify's quarterly API version changes; your team absorbs them for a custom worker, along with every schema change on the ERP side. | ||
| Switching & exit | Scenarios and Zaps are rebuilt by hand in whatever tool comes next; a worker calling the Admin API is ordinary code that moves with your integration layer. | ||
| Risk | |||
| Vendor risk | Make's Shopify listing carries 1.0★ across 3 reviews and Zapier 3.7★ across 56 (verified Sep 2026), which is thin cover for a job that guards stock accuracy; a worker you own has no vendor to lose. | ||
| Security & compliance surface | An iPaaS holds inventory and order payloads in a third party's cloud between steps; a worker runs inside infrastructure you already secure and audit. | ||
| Platform-deprecation exposure | Both lanes ride the GraphQL Admin API and its version cadence. Flow's Scheduled trigger carries no sunset notice as of September 2026, and the 10-minute floor has held long enough to plan around. | ||
| Value | |||
| Fit to requirement | An iPaaS schedule can go faster than 10 minutes but still runs on the vendor's clock and queue; a worker you own hits the exact cadence the warehouse feed needs, down to the minute. | ||
| Time to market | This afternoon against 2–5 weeks (Deploi estimate, illustrative). Flow itself is faster than both when 10-minute granularity is enough. | ||
| Performance & scale | Flow's Get data actions run on lists of up to 100 items, and an iPaaS meters by task or operation; a worker batches its reads and spends the Plus allowance of 1,000 points/second as it sees fit. | ||
| Data ownership & AI-readiness | Flow stores workflow runs for 14 days and an iPaaS keeps history in its own dashboard; a worker writes every run, payload and failure into your warehouse permanently. | ||
| Focus & opportunity cost | A scheduler is unglamorous plumbing nobody gets credit for, so buy it unless the cadence or the volume genuinely breaks the bought option. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Flow | Native — Per july 2026 research. Shopify's own automation layer — the WAIT option to exhaust first | Free at entry volumes; scales with volume (verified Sep 2026) | Every schedule from 10 minutes to one year, with no scheduler to operate |
| Zapier: Workflow Automation | Live — 4.0★, 74 reviews; 14-day trial on Professional and Team. Generic middleware connecting Shopify to other SaaS tools; the free tier allows two-step Zaps, and paid tiers add multi-step Zaps and webhooks. Logic lives in Zapier's editor, and the Shopify listing's rating trails Mechanic's. | Free (two-step Zaps); Professional $29.99/month; Team $103.50/month (verified Sep 2026) | Sub-10-minute schedules for teams with no dev bench to operate a worker |
| Make | Live — flagged — 1.0★ across 3 reviews on the Shopify listing, which is far too thin a review base to judge the app on. Make's own platform is a mature visual iPaaS, so treat the listing as an install path and evaluate the platform on its own trial rather than on these reviews. | Free tier available; Core $10.59/month; Pro $18.82/month; Teams $34.12/month (verified Sep 2026) | Low-stakes sub-10-minute schedules where a cheap metered scheduler is enough |
| Scheduled worker on your own infrastructure | Build lane — A small service on your own cron, calling the GraphQL Admin API on any interval you choose, with bulk queries for the large pulls and your own run log. No App Store listing exists for this because it is code, not a product. Celigo and similar iPaaS platforms sit in the same lane, configured from their own consoles rather than installed from the App Store. | $6,000–$18,000 one-time plus ~15–20% a year in upkeep (Deploi estimate, illustrative) | Sub-10-minute syncs at Plus volume where cadence, batching and run history all matter |
The Build Path
- Keep everything at 10 minutes and up inside Flow: Set the Scheduled time trigger to a whole-number interval, because decimals are not supported, and let Flow handle the fetch, the conditions and the actions. Nothing to host and nothing to bill, on every plan from Basic upward.
- Flow's schedule plus Send HTTP Request for the outbound half: Where the schedule is fine but the work belongs in your system, Send HTTP Request (Grow, Advanced and Plus) posts to your endpoint, waits up to 30 seconds for a response code, and retries 4XX, 5XX and 429 responses for up to 24 hours. You own only the endpoint.
- A scheduled worker calling the GraphQL Admin API: For sub-10-minute cadence, run your own cron against the Admin API, where Plus allows 1,000 points/second against 100 on standard plans. Use bulk queries for catalog-wide pulls: from API version 2026-01 each app can run five bulk query operations per shop simultaneously, each with 10 days to complete.
- Reconciliation and run history you keep: Shopify's own webhook guidance is blunt that delivery is not guaranteed and apps should run reconciliation jobs. Pair the fast schedule with a slower full sweep, and log every run into your warehouse because Flow keeps only 14 days.
- Effort band
- $6,000–$18,000 build — Deploi estimate (illustrative); lands in the $10–25K contact-form band. A single-entity inventory sweep sits at the bottom; multi-store, multi-warehouse reconciliation with alerting sits at the top
- Typical timeline
- 2–5 weeks (Deploi estimate, illustrative); ship the reconciliation sweep before the fast loop, because the sweep is what saves you when the fast loop misses
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $900–$3,600/yr (Deploi estimate, illustrative) for quarterly Admin API version bumps, ERP schema changes and alert tuning. Flow itself stays free.
- What you own — and what you take on
- You own: the cadence, the batching strategy, the run log and the reconciliation sweep. You take on: hosting, on-call for a job that now matters, and the rate-limit budget you spend against the Admin API.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,500–$5,000 (configuration and testing) | $6,000–$18,000 |
| Years 1–3 (recurring) | $3,700–$8,000 (subscription plus changes) | $2,700–$10,800 (maintenance and hosting) |
| 3-year total | ≈$5,200–$13,000 | ≈$8,700–$28,800 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: Zapier's Team plan at $103.50/month held flat, plus an initial configuration project at illustrative agency rates; metered task overages are excluded, which flatters the buy column.
- † Build path: one scheduled worker with a reconciliation sweep and alerting, plus hosting and upkeep; three-year horizon; Flow is free in both lanes.
What the Sticker Price Hides
On the buy path
- — Metered pricing scales with record count, so a 5-minute schedule across a large catalog leaves the entry tier fast (Zapier Professional $29.99/month, Team $103.50/month, verified Sep 2026)
- — Automation splits across two editors: half the schedule in Flow, half in the iPaaS, and no single place answers why a sync ran late
- — The vendor's queue sets the real cadence, which is not the same as the interval you configured
- — Make's Shopify listing carries 1.0★ across 3 reviews (verified Sep 2026); low-review middleware in an inventory path is a vendor risk, not a bargain
On the build path
- — A scheduler nobody owns is a scheduler that fails silently; budget alerting and on-call from day one, not after the first missed sweep
- — Rate-limit budget is real even on Plus: 1,000 points/second is generous but shared with every other integration hitting the same store
- — Flow keeps runs for 14 days and your worker keeps none by default, so the run log has to be built rather than assumed
- — ~$900–$3,600/yr upkeep (Deploi estimate, illustrative) for API version bumps and ERP schema changes
What Merchants Say
Ops teams porting a cron script describe the same surprise: the workflow builds fine, then the interval field refuses anything under 10 minutes and the migration plan needs a second lane.
Metered-scheduler reviews cluster on the bill: a 5-minute schedule multiplied by a large catalog turns a cheap entry tier into a line item nobody forecast.
If You Change Your Mind Later
If you bought and outgrow it
Leaving an iPaaS means rebuilding each scenario by hand in the next tool, because neither Zapier nor Make exports logic in a form Flow imports. Write down each schedule's interval, its query and its actions while you build them, and the rebuild becomes a week of configuration instead of an archaeology project.
If you built and want out
Almost nothing strands: a worker calling the GraphQL Admin API is ordinary code that moves with your integration layer, and its run history stays in your warehouse. Retreating to Flow is a real option for any job you later discover does not need sub-10-minute cadence after all.
When This Answer Changes
We're watching for:
- ▸ Any change to the Scheduled time trigger's 10-minute floor or its one-year ceiling (both held as of September 2026)
- ▸ Flow's Get data cap moving above 100 items, which would widen what a single scheduled workflow can sweep
- ▸ A Flow run-history window longer than 14 days, which would reduce the case for your own run log
Verdict change log:
No changes since first publication (September 2026).
Common Questions
How often can Shopify Flow's Scheduled trigger run?
Flow's Scheduled time trigger runs at most once every 10 minutes. Shopify states the limit exists to avoid workflows running longer than the interval between occurrences. For repeating workflows the longest possible interval is one year, and the amount must be a whole number, since decimals are not supported. Anything faster than 10 minutes needs a scheduler outside Flow.
Can Shopify Flow replace a cron job that runs every 5 minutes?
No. Flow's Scheduled time trigger caps at one run every 10 minutes, so a 5-minute cron job cannot move across unchanged. Two lanes cover the gap. An iPaaS scheduler such as Zapier costs $103.50/month on the Team plan (verified Sep 2026). A small service you own calls the GraphQL Admin API, where Plus stores get 1,000 points/second against 100 on standard plans.
What does Flow's Scheduled trigger cost on Shopify Plus?
Nothing. Shopify Flow is a free app on the Basic, Grow, Advanced and Plus plans, and the Scheduled time trigger is included. The cost appears only below the 10-minute floor: an external scheduler runs $29.99–$103.50/month on Zapier's paid tiers (verified Sep 2026), or $6,000–$18,000 once to build your own worker (Deploi estimate, illustrative). Flow's run history lasts 14 days, so budget a log of your own either way.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- List every scheduled job and write its true required interval next to its current one, since most cron jobs run faster than the business needs
- Move every job at 10 minutes or slower into Flow's Scheduled trigger with a whole-number interval
- Route outbound work through Send HTTP Request first, and confirm the 30-second wait and 24-hour retry window fit the endpoint
- Build a worker only for the jobs that survive the interval audit, and batch its reads with bulk queries
- Add a slower reconciliation sweep behind the fast loop and alert on divergence, not on individual failures
If you're going with BUY
- Price the iPaaS tier against your real record count, not the sample volume in the listing
- Keep the trigger and the conditions in Flow wherever possible, so one editor still explains most of the automation
- Confirm what run history the vendor retains and export it on a schedule, because Flow keeps only 14 days of its own
- Diary a re-decision when the metered bill passes the cost of a worker's yearly upkeep
Official Docs & Sources
- Scheduled time trigger (10-minute floor, one-year ceiling) — Shopify Help Center
- Shopify Flow: plan availability and included actions — Shopify Help Center
- Flow workflow limits and troubleshooting — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Flow Loops or Bulk Operations for Hundreds of Shopify Records?
Flow's Get data actions run on lists of up to 100 items, so a For each loop cannot sweep a large catalog. Catalog-wide edits need a real bulk lane.
Your App Has No Flow Connector: Build the Bridge or Wait?
Only an app's own developer can ship its Flow tasks. Outbound automation needs just Send HTTP Request; inbound needs a bridge app from $29/month (verified Sep 2026).
Flow Failure Alerting on Shopify: Build the Watcher or Buy One?
Shopify ships no store-wide Flow alert. Build a watcher on the Workflow error occurred trigger, which fires once per workflow version within a 30-day window.
Flow Workflow Retries on Shopify: Build Your Own Safety Net?
Flow retries transient errors like step timeouts and 5XX statuses, and never retries permanent ones. Critical workflows need their own error branches.
Should You Build or Buy Site Search on Shopify?
Site search on Shopify splits by catalog size: native to ~1,000 SKUs, buy in the middle, build at big-catalog, search-led scale.
Need a sync faster than Flow can schedule?
We map which of your jobs genuinely need sub-10-minute cadence, keep the rest free inside Flow, and build the worker plus reconciliation sweep for the ones that don't fit.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing and platform limits carry their verification date and get re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.