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. Visual Builder
    5. Testing

    Testing Workflows

    Visual Studio

    Debug and validate your automations before deployment

    Overview

    Testing is a crucial part of building reliable automations. The Visual Studio provides several tools to help you test, debug, and refine your workflows before activating them for production use.

    Missing required fields

    A node with a required field that is empty, or set to a choice that doesn't exist, shows an amber warning triangle on the canvas. Hover over it to see which fields need filling, for example Viewport Strategy (invalid choice).

    Run Workflow checks every active node first. If one is missing a required field, the run doesn't start and a message names the node and the field: open the node, fill it in and run again. Switched-off nodes are skipped.

    Workflows built for you (from the chat, a recording or an import) fill required fields with the node's defaults, so only fields that need your input, such as instructions, are left empty.

    Running Workflows

    Run Workflow

    Click the purple "Run Workflow" button in the toolbar to run your entire workflow from start to finish. The execution logs will show each step as it executes.

    • Enabled once the canvas has at least one node (use a Manual Trigger for testing)
    • With Run Visible, a browser window opens for browser automation nodes
    • Execution logs show real-time progress
    • Video recording available if enabled
    The Visual Studio toolbar run controls: Record Browser Actions, the purple Run Workflow button, Run Visible and the Video Recording toggle
    The toolbar's run row — Record Browser Actions, Run Workflow, visible/invisible mode and per-run video recording.
    Running a Single Node

    For debugging, hover over a node to show its quick actions:

    • Click ▶ ("Execute this node") to run just that node, using the outputs earlier nodes produced in the last run
    • Click the pause button to deactivate a node — runs skip it until you activate it again
    • View node outputs in the Execution Results panel

    Execution Panel

    The Execution Results panel at the bottom of the editor opens when a run starts (toggle it with Log in the header). It shows:

    Execution Logs

    Real-time logs showing each action as it executes. Successful steps are shown in green, failures in red with error details.

    Node Details

    Select a node in the Nodes column to see its Input and Output (as a table, JSON or schema) and how long it took. Useful for verifying data extraction and transformations.

    Path Filter

    For workflows with parallel branches, use the path filter to view logs from specific branches (All Paths, Main, Branch-1, Branch-2, etc.).

    Visible vs Headless Mode

    Switch between the two with the Run Visible / Run Invisible toggle in the toolbar. Running invisibly is available on the Starter, Developer, Pro and Enterprise plans.

    Visible Mode

    The browser window is visible, allowing you to watch the automation in real-time. Best for development and debugging.

    • See exactly what the automation does
    • Easier to debug selector issues
    • Can manually intervene if needed

    Headless Mode

    Browser runs in the background without a visible window. Best for production and scheduled runs.

    • Doesn't interrupt your work
    • Enable video recording for review

    Video Recording

    Enable video recording to capture a full visual record of workflow execution. Especially useful for headless runs and debugging intermittent issues.

    Turn on Video Recording with the toggle in the Visual Studio toolbar (Starter, Pro and Enterprise plans). After a recorded run, use Watch in the Execution Results panel, or Watch Recording on that run in the History view.

    Debugging Tips

    Use the Selector Picker
    If a selector isn't working, use the Selector Picker (target icon) to click on elements and generate new selectors. Enable auto-fallback for more resilient selectors.
    Add Wait Nodes for Late Content
    Browser actions already wait for their target element to be ready. If content loads late (for example a widget rendered after the page is interactive), add a Wait for Element node for it.
    Use Screenshots for Debugging
    Add Screenshot nodes at key points to capture the page state. This helps identify what the page looks like when something fails.
    Try Prompteryx Browser Agent
    If selectors are unreliable or the task requires reasoning, use the Prompteryx Browser Agent node. It uses AI vision to interact with elements and can handle complex, dynamic pages. Note: Uses AI credits per action.

    Related Documentation

    Visual Studio Overview

    Learn the basics

    Highlight Element

    Debug with visual highlights

    Prompteryx Browser Agent

    AI-powered automation

    Selectors Guide

    Master element selection