The Schedule trigger starts a Flow on a fixed cadence — no external event or webhook needed. Pick how often it should run, and Alta fires the Flow automatically on that schedule.
Who this is for: Anyone building automations in Flows that need to run on a clock — a nightly CRM sync, an hourly data pull, a weekly digest, or a monthly cleanup.
Before you start
The Schedule trigger is a starting block. It's the first step of a Flow, so every flow needs exactly one trigger.
A scheduled Flow only fires once the Flow is published and toggled Active. While it's a draft, the schedule does nothing.
No connection or authentication is required — Schedule is a built-in core integration.
Step 1: Add the Schedule trigger
Open the Flow you want to run on a schedule (or create a new one).
Click the trigger block at the top of the canvas and pick Schedule from the integration picker.
Choose one of the six schedule types below.
Step 2: Pick a schedule type
Every X Minutes — Triggers the current flow every X minutes. Set Minutes to any value between 1 and 59 (default is 1). Runs in UTC.
Every Hour — Triggers the current flow every hour. Optionally tick Run on weekends (Sat,Sun). When it's off, the Flow runs only Monday–Friday. Runs in UTC.
Every Day — Triggers the current flow every day. Set the Hour of the day (Midnight, 1 am … Noon … 11 pm), pick a Timezone (defaults to UTC), and optionally tick Run on weekends (Sat,Sun). With weekends off, it runs Monday–Friday only.
Every Week — Triggers the current flow every week. Choose the Day of the week (Sunday–Saturday), the Hour of the day, and a Timezone (defaults to UTC).
Every Month — Triggers the current flow every month. Choose the Day of the month (1–31), the Hour of the day, and a Timezone (defaults to UTC).
Cron Expression — Trigger based on cron expression. Enter a standard 5-field Cron Expression (default 0/5 * * * *, which means every 5 minutes) and pick a Timezone (defaults to UTC). Use this when the simpler options can't express the cadence you need — for example 0 9 * * 1-5 for 9:00 every weekday.
Step 3: Add your steps and publish
Build the rest of the Flow under the trigger — for example a CRM action, an HTTP request, or a Slack message.
Publish the Flow and make sure it's toggled Active. The schedule starts counting from that point.
Watch executions land in the Runs tab to confirm the Flow is firing as expected.
Tips and common pitfalls
Nothing is running? Check that the Flow is published and Active. A scheduled trigger does nothing while the Flow is a draft.
Times look off? Every X Minutes and Every Hour always run in UTC — they have no timezone selector. Only Every Day, Every Week, Every Month, and Cron Expression let you choose a timezone, and they default to UTC, so set it explicitly if you want local time.
Weekday-only runs: Leave Run on weekends (Sat,Sun) unchecked on the Every Hour and Every Day triggers to skip Saturday and Sunday.
Keep frequent schedules light: a tight cadence like every 1 minute fires often and consumes credits on every run. Use the lowest frequency that meets your need.
One trigger per Flow: if you need the same logic on both a schedule and an incoming request, build separate Flows or use a Catch Webhook trigger instead.
Related
]]>