> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Run an action

Once an action is installed and configured (see [Actions and the library](/actions/overview)), you run it over the files in a space. A run reads the files you pick, does the action's one job, and shows results on a run page as they come in.

For structured extraction specifically, see [Extract data](/actions/extract-data); for filling and signing, see [Document generation](/actions/document-generation).

## Where runs start

Every standalone run lives in a space's **Actions** tab. Open a space and select **Actions** — it lists "Every action run in this space." with a **"Run action"** button. If there's nothing there yet you'll see **"No runs yet"** / "Run an action over this space's files to see results here."

You can also launch a run from the **Files** tab. Select one or more files, and the bulk toolbar's **"Run action"** button starts a run over exactly those files.

## The launcher

**"Run action"** opens the launcher, titled **"Run an action"** ("Pick an action and the files to process. Results appear on the run page as they come in.").

#### Pick an action

Use the **"Action"** select (**"Choose an action"**). If nothing is installed, you'll be pointed to "the actions library."

#### Fill in run settings

If the action takes per-run settings, a **"Run settings"** form appears. Fill it in.

#### Choose files

Pick the files to process — the picker shows **"`{n}` of `{m}` selected"** with **"Select all eligible files"** and **"Upload more"**. Files the action can't handle show **"This action can't process this file"** and can't be selected. An action that works on one file at a time accepts exactly one.

#### Run it

Click **"Run action"**. You're taken to the run page, where results fill in as they arrive.

The launcher also shows a **"Recent runs"** list so you can jump back into a run you started earlier.

<img src="https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/cloudraker.docs.buildwithfern.com/812972a86f3402550f5165acefb98cfe8d30e51f40b0436edbd58fb28b780908/docs/assets/images/guide/actions/run-action-launcher.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260726%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260726T051357Z&X-Amz-Expires=604800&X-Amz-Signature=87337e7fa33cb687a132fd23a1209af2734a5d496dad08a5180837976b94a603&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" alt="The Run an action launcher with the 'Invoice extraction' action chosen, its Run settings form, and 2 of 5 files selected" />

## The run page

The run page (`/spaces/$spaceId/runs/$runId`) headers the action name and a status badge — **"Running"**, **"Waiting for you"**, **"Done"**, or **"Failed"** — alongside the start and finish times and a source-file count. While a run is active you can **"Cancel run"** (confirm: "Cancel this run? The run stops and is marked failed. This can't be undone."). If the AI assistant dispatched the run from a playbook, a **"Triggered by playbook run"** link points back to it.

The body of the page changes to fit the action:

| Action                          | What you see                                                                                                                            |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Structured extraction (running) | Live per-file progress — **"`{done}` of `{total}` documents extracted"**, each file flipping from **"Extracting…"** to **"Extracted"**. |
| Structured extraction (done)    | The results grid — see [Extract data](/actions/extract-data).                                                                           |
| Fill form (paused)              | The in-app **"Review form values"** step — see [Document generation](/actions/document-generation).                                     |
| Sign                            | The **"Signatures"** envelope panel — see [Document generation](/actions/document-generation).                                          |
| Everything else                 | Generic sections: **"Documents"** (the source files), **"Results"**, and **"Generated files"** (download rows).                         |

For redaction and other file-producing actions, the redacted or generated file appears under **"Generated files"** — download it from there.

<img src="https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/cloudraker.docs.buildwithfern.com/eecb9b06935ab66ae2fa7e3c91abc45e2bda718425d0d48838a415db3335e5c9/docs/assets/images/guide/actions/run-done.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260726%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260726T051357Z&X-Amz-Expires=604800&X-Amz-Signature=2076f76b551ec64471ac4a64007cfed12bf15ebf50b869139753aa6551274be8&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject" alt="An action run page in the Done state, showing the run header with start and finish times and the Results section below" />

## Bulk runs

To process many files at once, open the space's **Files** tab, select the files, and use the bulk toolbar's **"Run action"**. This launches a single run over every selected file — the same run page, with one row per file. There's no separate "batch" mode; a bulk run is just a run with many source files.

The raw output, the list of generated files, and the action version are folded into a **developer-mode-only** disclosure labeled **"Run details — sources, generated files, raw output."** Turn on developer mode from the profile menu to see it. See [Actions and the library](/actions/overview#developer-mode).

## Where to go next

#### [Extract data from documents](/actions/extract-data)

Read the results grid, review fields against their sources, and import to Data.

#### [Fill and sign documents](/actions/document-generation)

Review drafted form values and track a signing envelope.

#### [Run actions inside a playbook](/playbooks/approvals-and-steering)

Approve the AI assistant's action steps as it works.