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. Developers
    3. Workflows

    Run workflows from anywhere

    Anything built on the Visual Studio canvas, or saved from an agent run, has an id. Run it with variables, wait for the result, put it on a schedule, or trigger it from a webhook.

    What it does

    A workflow is a fixed sequence of browser steps, app actions and logic. Running one costs no AI credits (unless a step itself uses AI), which is why the agent's saveAsWorkflow option matters: do it once with AI, repeat it forever without.

    Every run returns an execution id you can poll. Runs are queued and usually start within a minute; the finished record carries each step's output, and a webhookUrl gets a signed callback when it ends.

    Three ways to run it

    SDK
    import { Prompteryx } from '@prompteryx/sdk'
    const px = new Prompteryx({ apiKey: process.env.PROMPTERYX_API_KEY })
    
    const workflows = await px.workflows.list()
    const run = await px.workflows.runAndWait(workflows[0].id, {
      input: { postcode: 'SW1A 1AA' },          // becomes {{postcode}} inside the workflow
      execution: { runMode: 'headless' },
      timeoutMs: 5 * 60_000,
    })
    console.log(run.status, run.outputs)        // 'completed', { … }
    
    // or start and check back later
    const started = await px.workflows.run(workflows[0].id, { input: { postcode: 'SW1A 1AA' } })
    const later = await px.executions.wait(started.executionId)
    const logs = await px.executions.logs(started.executionId)
    CLI
    npx prompteryx workflows list
    npx prompteryx workflows run fHX8NlpAJxoWuAOll7zr --input postcode="SW1A 1AA" --wait
    npx prompteryx runs logs api_…
    HTTP
    curl -X POST https://www.prompteryx.ai/api/v1/workflows/WORKFLOW_ID/execute \
      -H "Authorization: Bearer px_live_YOUR_KEY" -H "Content-Type: application/json" \
      -d '{"variables":{"postcode":"SW1A 1AA"},"options":{"runMode":"headless"},"webhookUrl":"https://your-server.com/done"}'
    # → 202 { "success": true, "data": { "execution": { "id": "api_…", "status": "pending", "statusUrl": "…" } } }
    
    curl https://www.prompteryx.ai/api/v1/executions/api_… -H "Authorization: Bearer px_live_YOUR_KEY"
    # → { "data": { "execution": { "status": "COMPLETED", "outputs": { "Step name": { … } }, "nodeResults": [ … ] } } }
    From an AI assistant (MCP)
    "Run my 'Weekly bin day check' workflow and tell me the result."
    # workflow_list → workflow_execute. Assistants can also create a workflow from a description,
    # add steps to one, or record browser actions and save them as a workflow.
    Schedules and webhooks
    Run without writing any code at all.
    // every weekday at 08:00 London time
    await px.schedules.create({ workflowId: 'wf_…', cronExpression: '0 8 * * 1-5', timezone: 'Europe/London', input: { postcode: 'SW1A 1AA' } })

    Webhook triggers give a workflow its own URL that any service can POST to. See Webhooks.

    Limits

    Runs count against the plan's monthly executions. Browser steps use cloud minutes unless the run targets your local Chrome through the desktop app.

    Full endpoint list with every field: REST API reference.