Skip to main content
Quick actions create an ephemeral browser, perform one URL-level operation, and return the result. Use them when the job is one scrape, one screenshot, or one PDF and you do not need browser session continuity. Use a managed browser instead when the workflow needs login state, multiple steps, downloads, dialogs, recordings, Debug UI inspection, CDP, or post-step observations after each browser-code action.

Choose the action

All quick actions can use browser policy. SDK, CLI, and REST quick actions also support custom proxy configuration.

SDK examples

CLI examples

REST examples

Screenshot and PDF REST responses return encoded document data. Store it in your application or move to a managed browser if you need a richer artifact lifecycle.

When to switch to managed browsers

Switch when any of these are true:
  • The task needs multiple page interactions.
  • You need a Debug UI URL or CDP connection.
  • The result depends on login state.
  • You need downloads, dialogs, permissions, files, or recordings.
  • An agent or application needs observations after each step.
  • Cleanup and lifecycle control matter.
Reference: SDK quick actions reference, REST API, browser control, and policy and proxy.