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
    3. Nodes
    5. Triggers

    Trigger Nodes

    Start your workflows automatically or on-demand

    Overview

    Trigger nodes define when and how your workflows start. Every workflow must have at least one trigger. You can have multiple triggers on a single workflow to start it from different sources.

    Key Concepts

    • Manual triggers - Start with a button click, ideal for testing
    • Schedule triggers - Run at specific times or intervals
    • Event triggers - React to external events (emails, webhooks, file changes)
    • Activation required - Most triggers require workflow activation to run automatically
    The Manual Trigger node's config panel with its description field and a link to switch to a Schedule Trigger
    The Manual Trigger config panel — the simplest starting point, with a one-click switch to a Schedule Trigger.

    Available Triggers

    Manual Trigger
    Start workflows manually with a button click. Perfect for testing, one-time runs, or user-initiated automations. Every workflow needs at least one trigger.

    Common Use Cases

    Testing workflows, on-demand tasks, user-initiated actions

    Schedule Trigger
    Run workflows automatically at scheduled times. Pick a quick preset, or a custom interval (every N minutes or hours), daily, weekly, monthly, one-off or cron schedule.

    Common Use Cases

    Daily reports, periodic data sync, scheduled backups, monitoring

    View detailed documentation →
    Webhook Trigger
    Receive HTTP requests to start workflows. Get a unique URL that external services can call to trigger your automation.

    Common Use Cases

    Integrating with external services, receiving notifications, API endpoints

    View detailed documentation →
    Connect Hub Trigger
    Start workflows when an event happens in any Connect Hub app — a new email, a new issue, a new booking and more. Use it for Gmail ("New Email Received") and Google Drive ("New File") events.

    Common Use Cases

    Email processing, file workflows, reacting to events in thousands of apps

    Microsoft Outlook Trigger
    Trigger when new emails are received in Microsoft Outlook or Office 365. Filter by sender, subject, and folder.

    Common Use Cases

    Enterprise email automation, inbox management, notification processing

    Slack Trigger
    React to Slack events: new messages, reactions, mentions, file uploads. Build chatbots and automated responses.

    Common Use Cases

    Chatbots, team notifications, command handlers

    Telegram Trigger
    Trigger when messages, commands, or updates are received in Telegram. Build bots and automated responses.

    Common Use Cases

    Chat bots, command handlers, notification relays

    WhatsApp Trigger
    Trigger on WhatsApp Business messages, status updates, and events. Automate customer communication.

    Common Use Cases

    Customer support bots, message routing, automated replies

    Facebook Trigger
    Trigger on Facebook page events: new comments, posts, page updates, and more.

    Common Use Cases

    Social media monitoring, comment moderation, engagement tracking

    SharePoint Trigger
    Start workflows when SharePoint events occur: new documents, list item changes, folder modifications.

    Common Use Cases

    Document management, approval workflows, content sync

    Workflow Activation

    Most triggers require your workflow to be activated before they'll run automatically:

    • Manual Trigger - Works without activation (test anytime)
    • Schedule Trigger - Requires activation to run on schedule
    • Webhook Trigger - Accepts requests as soon as the workflow is saved with the node (no activation needed)
    • App/Event Triggers - Require activation to start watching for events

    To activate: Save the workflow, then click the Inactive button next to Undo/Redo at the top-left of Visual Studio so it turns green and reads Active. When active, your workflow will run automatically based on its triggers.

    Multiple Triggers

    A single workflow can have multiple triggers. For example:

    • Run daily on schedule AND when a new email arrives
    • Trigger via webhook AND manually for testing
    • React to Slack messages AND scheduled reminders

    Each trigger starts the same workflow independently. You can use conditional logic inside the workflow to handle different trigger sources differently. A workflow uses at most one Webhook Trigger and one Schedule Trigger — if you add more, only the first of each is used.

    Related Documentation

    Visual Builder Overview

    Learn about creating workflows

    If Condition Node

    Handle different trigger types

    Testing Workflows

    Test with manual triggers