Workbench guide

Run any enabled capability interactively in the console, inspect jobs and usage, then copy the exact API request for automation.

The console is an interactive workbench over the same capability implementations as the public API. The sidebar groups capability pages into workspaces: Prospecting (prospecting runs, campaigns, and audiences), Research (playbooks and their templates, company research, enrichment, and site intelligence), Outreach (messages, message templates, and documents), and Assets (brands and offers). Other enabled capabilities have their own sidebar entries, and All capabilities lists every capability with its status. On each page you create work, watch job status, and review the result. Console actions expose the exact API request through View code, so a run you like can be handed to code or an agent unchanged.

A typical exploration:

  1. Select the project that should own usage and charges.
  2. Open a capability page from its workspace in the sidebar and enter its documented inputs — a target company for Playbooks, identifiers to enrich for Enrichment, a brief for Documents.
  3. Submit, watch job status and progress, then review the rendered result and its usage.
  4. Use View code to copy the equivalent API call for automation.

Workbench requests perform real work on hosted deployments and record real usage. A development project isolates that work but does not simulate it. A capability that is not enabled for your organization shows a locked state instead of executing, and specification-preview surfaces store plans without running anything — the console reflects the same execution boundaries as the API.

For automation, start with the Quickstart. Job behavior is in Jobs and resumable polling, failures are handled with Errors and retry decisions, and each capability's exact request values are in its own guide — for example Playbooks or Enrichment.