Be efficient
Schedule to weekly for briefs, monthly - for closes. Interval - only for freequent changes.
Run workflow automations on schedule
WEXTL® Workflow Scheduler [1] runs workflows on a cadence you set - interval, weekly, monthly by day, monthly by weekday, or last day of the month - each with its own IANA timezone, if specified.
WEXTL® keeps every scheduled execution on the run history [4] with its inputs and outputs visible - so you will always have data to monitor [5].
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Video slide shows a workflow scheduling settings panel on WEXTL® canvas.
How to set an effective schedule for automation?
Workflow scheduler is designed for flexible automation cadence settings - for people who look for minimal, but advanced setup. Below you can find 4 tips on how to make a schedule that is cost efficient [5].
Run during business hours
Restrict to weekdays or business hours. Nobody wants to read a Sunday digest.
Skip if already running
Avoid double runs. If the previous run has not finished, do not start the next one.
Select IANA timezone
No timezone surprises. Let regional teams set their own schedule.
3 practic steps to set correct schedule inside WEXTL® workflow builder
Only 3 manipulations that help to achieve efficient workflow schedule [1]. Under 5 minutes [5] for the whole setup - from picking a cadence to a live automation running inside specified time slots.
STEP 1
Pick a cadence and timezone
Choose interval, weekly, monthly by day, monthly by weekday, or last day of month [1]. Each has its own setting of IANA timezone.
Schedule workflow
Set when WEXTL should run the automation. Workflow will run on the specified schedule until you turn it off.
Run every*Text
15 minutesinterval
STEP 2
Save your workflow
Open workflow schedule settings after workflow has been built [3]. Save the interval from Step 1 - exactly as you want automation to run.
STEP 3
Monitor runs, pause when needed
Each execution is visible run history [4] with its inputs, outputs and settungs. Switch automation off to pause the runs without deleting the schedule [1] - the graph and nodes stay intact.
Recent ticks
Every tick shows on the run history. Success, skipped by skip-if-running, or failed — the record is always there.
Today · 09:00
Yesterday · 09:00
Fri · 09:00
Thu · 09:00
How does WEXTL scheduling handle timezones and DST?
Each schedule carries its own IANA timezone set inside the scheduler itself [1] - a US finance close and an EU morning digest can sit in the same workspace, each firing on its own local clock. Falls back to the workflow timezone, then the workspace, then UTC - if none is set.
Daylight saving time is handled explicitly, not left to chance: a timeslot that falls inside a spring-forward gap rolls forward to the first valid instant after the jump. A time that falls in the fall-back fold - which occurs twice - fires once, on the earlier occurrence, never twice.
An interval set to every 15 minutes fires at :00, :15, :30, and :45 in the schedule's local time - wall-clock-boundary alignment, the way traditional cron aligns [5] - not 15 minutes after whoever last saved the workflow.
Video shows scheduled workflow firing on IANA timezone cadence on WEXTL®.
What happens when scheduled runs overlap or need to pause?
By default, a schedule that fires while the previous tick is still running enqueues the new run - the same stack and run behavior most automation tools default to [5]. No silent skips of the intervals.
To aviod overlapping runs, you can turn on skip and running setting. WEXTL® automatically suppresses overlapping run - useful for a CRM reconcile automations that may run longer.
Turning a scheduled workflow off stops the cadence without touching the canvas [3]. After editing automation and activating it back - cadence is auto recalculated without changes to workflow nodes [4].
How to skip double runs if already running on WEXTL®.
1300+ apps you can trigger on schedule
Any app in WEXTL® Apps Library [2] can act on a scheduled tick - reconcile, digest, sync, or notify at whatever cadence fits your team's rhythm.
Supported integrations
Frequently asked questions
Scheduling fires on a clock — interval, weekly, or monthly patterns you set. An inbound Webhook trigger fires the moment an external system POSTs an event. Use scheduling for digests, syncs, and reconciles you own the timing of; use webhooks when the source system tells you when work needs to happen.
A schedule fires on a clock — interval, weekly, or monthly patterns you set. Calendar-aware assistant workflows (see Executive Assistants) watch for meeting events on a connected calendar instead. Use a schedule for digests, syncs, and month-end jobs; use a calendar watch when the trigger is a meeting itself.
That month is skipped — WEXTL doesn't quietly roll it to the 1st or the 30th. If a schedule needs to fire every month regardless of length, last-day-of-month or monthly-by-nth-weekday are the patterns built for that.
Yes. The interval and weekly patterns both take a weekday restriction — set an every-30-minutes interval limited to Mon-Fri, or a weekly pattern that runs 09:00, 12:00, 15:00 on weekdays only. Weekends fall out of the cadence without any extra logic inside the workflow itself.
Editing the cadence recomputes only the NEXT fire time — a tick already in-flight finishes on the old plan, and any queued (but not-yet-started) tick advances to whatever the new cadence says. The workflow's nodes and connections don't get rebuilt, so downstream steps behave the same way they did on the last successful tick.
Put recurring work on a schedule or explore more
References
List of resources used for writing this documentation page on WEXTL®. Follow a citation to jump straight to the source.
- WEXTL® Workflow Scheduler
- WEXTL® Apps Library — full catalog of supported app integrations.
- WEXTL® visual workflow builder — canvas for building and visually tracing automations.
- WEXTL® built-in workflow nodes — catalog of built-in nodes with per-node documentation pages.
- WEXTL® anonymized usage experience from customers — collected by support team and/or partners.