Run an action

Launch a single action over one or many files in a space. Follow it on the run page.
View as Markdown

After you install and configure an action (see Actions and the library), run it over the files in a space. A run reads the files you pick and does the action’s one job. Results appear on a run page as they come in.

For structured extraction, see Extract data. For filling and signing, see Document generation.

Where runs start

Every standalone run lives in a space’s Actions tab. Open a space and select Actions. The tab lists “Every action run in this space.” and has a “Run action” button. If no runs exist, you 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. The bulk toolbar’s “Run action” button starts a run over 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.”).

1

Pick an action

Use the “Action” select (“Choose an action”). If no action is installed, the launcher points you to “the actions library.”

2

Fill in run settings

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

3

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 cannot handle show “This action can’t process this file”. You cannot select them. An action that works on one file at a time accepts exactly one file.

4

Run it

Click “Run action”. The run page opens. Results fill in as they arrive.

The launcher also shows a “Recent runs” list. Use it to return to a run you started earlier.

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) shows the action name and a status badge: “Running”, “Waiting for you”, “Done”, or “Failed”. It also shows 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:

ActionWhat you see
Structured extraction (running)Live per-file progress: {done} of {total} documents extracted”. Each file flips from “Extracting…” to “Extracted”.
Structured extraction (done)The results grid — see Extract data.
Fill form (paused)The in-app “Review form values” step — see Document generation.
SignThe “Signatures” envelope panel — see Document generation.
Everything elseGeneric 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.

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 shows one row per file. There is no separate “batch” mode. A bulk run is a run with many source files.

A developer-mode-only disclosure holds the raw output, the list of generated files, and the action version. Its label is “Run details — sources, generated files, raw output.” Turn on developer mode from the profile menu to see it. See Actions and the library.

Where to go next