Skip to main content
A reporter analyzes sources by running a workflow — an ordered list of steps, each a tool plus an inline prompt. This guide builds one and runs it.

1. Create the reporter

2. Create a workflow

A workflow has a target_kind — what it runs against (youtube_video, youtube_channel, or collection):

3. Add steps

Each step is a tool_id plus an inline prompt_text (and optional params). Browse available tools at GET /v1/tools:
Reordering by drag-and-drop? Send the whole list at once with PUT /v1/reporters/{id}/workflows/{wid}/steps and a steps: [...] array — it replaces all steps in order.

4. Run it

Running is asynchronous — you get a 202 + an execution. Point it at a source (a URL/handle resolved like an item). Omit workflow_id to use the reporter’s default workflow:
Track the execution to completion; the output lands as documents (GET /v1/documents?reporter_id=rep_123). Inspect a finished run with GET /v1/executions/{id} to see each step’s input/output.

5. (Optional) attach collections

Attach collections to the reporter so it has a working set, then run a collection-wide workflow with POST /v1/reporters/{id}/process-collection:

Next

Schedule it

Run the workflow automatically over new videos on a cadence.