PrompteryxBeta
    ⌘K
    PlatformSupport
    Menu
    IntroductionInstall Desktop & extensionQuick StartPlatform Overview
    OverviewWhat you can makeAI Browser Agent in the chatModels and AutoConnectorsSchedulesProjectsExplore and publishingShare linksMemory and SkillsPersonal agent (beta)Welcome, settings and skinsPlans, credits and top-upsPrompteryx DesktopGroups (pilot)Phone app (early access)
    OverviewCreating WorkflowsTesting & DebuggingScheduling
    OverviewGetting StartedCommandsRecordingSettingsStructured OutputParallel AgentsTips & Best Practices
    OverviewInstallationSidebar AgentUsing Attached FilesExecute on Current TabExporting to Visual Studio
    Overview
    OverviewOpen PageClickClick CoordinatesFillExtract TextScreenshotWaitPress KeyFocus ElementBlur ElementSelect TextHighlight ElementSet ViewportGet Bounding BoxScrollHoverSelect OptionAssertionsCookiesEvaluate JavaScriptExample Workflows
    OverviewPrompteryx Browser AgentOpenAI
    OverviewSchedule TriggerWebhook Trigger
    OverviewGoogle SheetsGoogle CalendarConnect Hub (3,000+ apps)Example Workflows
    AI Vision SettingsChrome Automation ProfilesCloud BrowserBrowser Profiles & Persistent ContextVideo RecordingExecution LogsSharing & CollaborationEdit History
    Selectors GuideVariables
    Start hereGet an API keyRun the AI browser agentDrive a cloud browserRun workflows from anywhereUse connected apps (Connect Hub)SDK (TypeScript)CLIMCP for AI assistants
    REST APIWebhooksMCP toolsCloud Browser APICloud Browser quickstartMigrate from Browserbasen8nZapierMake.com

    Need help? Contact Support

    1. Documentation
    2. Nodes
    3. Triggers
    4. Schedule

    Schedule Trigger

    Trigger Node

    Run workflows automatically at specified times or intervals

    Overview

    The Schedule Trigger starts your workflow automatically at configured times. Pick a quick preset (like "Daily at 9:00 AM"), or choose Custom schedule... for an interval, a daily, weekly or monthly time, a one-off run, or a cron expression.

    Activation Required
    Schedule triggers only run when the workflow is activated: save the workflow, then switch it from Inactive to Active in the toolbar. Active schedules are listed on the Schedules page. Saving an active workflow updates its schedule straight away. If the schedule can't be turned on (for example a Run Once time in the past, or your plan's limit on active scheduled workflows: Starter and Developer 5, Pro and Enterprise 15, not included in the Free Trial), the workflow stays Inactive and the reason is shown.
    Parameters
    Configuration options for this node
    quickSchedule
    Select
    Required

    Quick Schedule preset: every 5/15/30 minutes, every 1/2/4 hours, daily (9 AM, 6 PM, midnight), weekdays, weekends, every Monday, the 1st or 15th of the month — or "Custom schedule..."

    Default: Daily at 9:00 AM
    customType
    Select

    Schedule Type when Custom is chosen: Repeating Interval, Daily, Weekly, Monthly, Run Once, or Advanced (cron expression)

    Example: interval, daily, weekly, monthly, once, cron
    intervalValue / intervalUnit
    Number / Select

    Repeating Interval: run every N minutes or hours (Run Every 1–60, Unit Minutes or Hours)

    Example: 30 minutes
    dailyTime / weeklyDays / monthlyDay
    Time / Days / Number

    Daily, Weekly and Monthly: the time to run, the days of the week, or the day of the month (1–31)

    Example: 09:00, Mon–Fri, 1
    onceDate / onceTime
    Date / Time

    Run Once: the date (YYYY-MM-DD) and time to run, or an optional day of the week to run on its next occurrence

    Example: 2026-12-01, 18:00
    cronExpression
    String

    Advanced: a standard 5-field cron expression

    Example: 0 9 * * 1-5 (9am weekdays)
    timezone
    Select

    Timezone the schedule follows. Auto-detect uses your browser's timezone when you activate or save the workflow.

    Default: Auto-detect (your browser timezone)
    The Schedule Trigger config panel in Visual Studio: a Quick Schedule preset dropdown set to Daily at 9:00 AM, and a Timezone selector on auto-detect
    The Schedule Trigger's config panel — pick a quick preset (or Custom for intervals and cron) and the timezone the schedule should follow.

    Schedule Types

    Custom Schedule Types
    Choose "Custom schedule..." in Quick Schedule, then a Schedule Type
    Interval
    Every N minutes or hours
    Daily
    Once a day at a set time
    Weekly
    Chosen days at a set time
    Monthly
    A day of the month at a set time
    Run Once
    A single future date and time
    Cron
    Any standard cron expression

    Recurring schedules can run at most every 5 minutes — a faster schedule is not accepted. A Run Once time must be in the future. After activating, check that the schedule appears on the Schedules page.

    Cron Expressions

    Cron expressions provide precise control over scheduling. Format:

    ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6, Sun=0) │ │ │ │ │ * * * * *

    Ranges (1-5), lists (1,15), steps (*/15) and names (MON, JAN) are supported, and 7 also means Sunday. The expression is evaluated in the trigger's timezone.

    Common Examples:

    0 9 * * *Every day at 9:00 AM
    0 9 * * 1-5Weekdays at 9:00 AM
    0 */2 * * *Every 2 hours
    30 8 1 * *1st of month at 8:30 AM
    0 0 * * 0Every Sunday at midnight
    */15 * * * *Every 15 minutes

    Usage Examples

    Daily Report Generation
    Run every day at 9 AM to generate reports
    Quick Schedule: Daily at 9:00 AM
    Same as cron:0 9 * * *
    Timezone: America/New_York
    Hourly Price Check
    Monitor prices every hour
    Schedule Type: Repeating Interval
    Run Every: 1
    Unit: Hours
    Weekly Backup
    Run every Sunday at 2 AM
    Schedule Type: Advanced (cron expression)
    Expression:0 2 * * 0

    Best Practices

    Set the Right Timezone
    The default, Auto-detect, uses the timezone of the browser you activate or save the workflow from. If the workflow must run at a specific local time (or teammates in other timezones edit it), pick the timezone explicitly. Daylight-saving changes are handled for you.
    Use a Cloud Browser for Unattended Runs
    Scheduled workflows that use a Cloud Browser profile run on Prompteryx's servers. On a local Chrome profile, each run needs your computer on with Prompteryx Desktop running — otherwise the run is marked as failed.
    Test Before Activating
    Click "Run Workflow" to run a scheduled workflow straight away and check it works before activating the schedule. This prevents unexpected runs of untested workflows.
    Late and Missed Runs
    If the scheduler runs a few minutes late, the missed slot still fires once (slots more than about 5 minutes old are skipped). A Run Once schedule can fire up to 24 hours late; after that it is marked as missed.

    Related Documentation

    Testing Workflows

    Test before scheduling

    Webhook Trigger

    Trigger on-demand via HTTP