Skip to main content
Question

How to Schedule a Zap Every 15 or 30 Minutes?

  • Oct 23, 2026 5:02 PM UTC
  • 7 replies
  • 81 views

Is it possible to run a Zap every 15 or 30 minutes using the Schedule by Zapier trigger? I can only see an option to run it every hour minimum. 

I can see the Custom Frequency option in Schedule by Zapier. Can it be configured to run a Zap every 15 or 30 minutes, or does it only support intervals in days, weeks, and months? If it's not supported, is there a recommended workaround to run a Zap every 15 or 30 minutes?

7 replies

DavidLGS
Forum|alt.badge.img+6
  • Zapier Solution Partner
  • Oct 23, 2026 5:24 PM UTC

Every once in awhile, Zapier will get their own functionality wrong. Have you tried setting the custom frequency to 0.01 days and turning your zap on to see what happens? Even though they say decimals are not supported….sometimes they are.

If that doesn’t work, you can try a 2-zap workaround.

I’VE NOT TESTED THIS (nor do I have time), but it would be fun to find out if it works.

The first zap needs any arbitrary trigger that you can trigger once on your own. The next step would be a code step that triggers an output every 15 minutes, and just simply “prints” or outputs the current time. 

Then, in your second zap, you would trigger it from the code step’s output. 

Theoretical example:

Trigger Zap 1 whenever you’re ready. → Code step waits 15 minutes and outputs the time.

Zap 2 gets triggered when code step outputs the time. Executes actions in Zap 2.

… 15 minutes go by …

Code step outputs a new time. Zap 2 gets triggered.

 

It’s a theory anyways….


Forum|alt.badge.img+1

​@automation_journey 

Schedule by Zapier doesn’t support running a Zap every 15 or 30 minutes. The shortest built-in interval is Every Hour. The Custom Frequency option supports daily, weekly, and monthly intervals, with a minimum interval of one day.

You can find more details in our guide to scheduling Zap workflows.

A couple of timezone details to keep in mind:

  • Schedule triggers use your Zapier account timezone, rather than the timezone set for an individual Zap. If you change your account timezone, turn the Zap off and back on for the change to take effect.

  • Run timestamps in Zap History appear in UTC. These may differ from your local time even when the Zap is running on the correct schedule.

Recommendation: For 30 minutes, use two offset Every Hour Zaps.


​@automation_journey 

You can try https://zapier.com/apps/schedule-helper/integrations

It can easily run every 15 or 30 minutes

It can do

  • Multiple minutes
  • Multiple hours
  • Multiple days
  • Multiple weeks
  • Multiple week days
  • Multiple months

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Oct 28, 2026 4:14 PM UTC

Hi ​@automation_journey 

Follow this guide: 

 


  • Beginner
  • Oct 30, 2026 6:49 PM UTC

what if another step requires loop functionality? it doesnt appear to be that I can double loop here


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Nov 2, 2026 11:43 AM UTC

Hi everyone! 👋

​@automation_journey, did any of the suggestions shared here do the trick? Let us know what worked, or if you could do with some more help.

​@ajhongsteno, you're right that more than one looping action, or nested loops, aren't supported in Classic Zaps. They are supported in Next Gen Zaps though, which are in early access. You can request access here: https://zapier.com/workflow/early-access. If you give Next Gen Zaps a try and run into any trouble, just let us know!


oliverwilliams

Ran into this exact same wall when I started out. The staff reply actually saved me.

 

Hourly is the fastest built-in trigger you get. To cut that down to 30 minutes, I just set up two separate hourly Zaps. Staggered the second one to run 30 minutes after the first. Worked like a charm for me.

 

Just make sure to check your account time zone settings first. If you don't, the offset gets messy fast. Definitely try this two-Zap trick before you mess around with custom code steps.