Actions and the library
An action is a reusable, single-purpose tool your team can run on documents — read a document and pull out structured data, fill a form, send a document for signature, and more. You install an action once from the library, configure it, and then run it over a space’s files, either on its own or as a step the AI assistant dispatches inside a playbook.
To run an installed action, see Run an action.
Installed actions
Open Actions in the sidebar to reach /actions, titled “Actions” with the description “Installable actions your team can run on documents.” The “Installed actions” section lists everything your team has installed, with a “Filter actions” box to narrow the list.
The table has these columns:
- Name — links to the action’s configuration editor.
- Created — when the action was installed.
- Uninstall — a trash button. It opens a confirm dialog titled “Uninstall action?” (“This removes “
{name}” from your organization. This can’t be undone.”); confirm with “Uninstall”.
If nothing is installed yet, you’ll see “No actions installed” / “Install an action from the library to get started.” The list is paginated (10, 20, 50, or 100 per page).
To install something new, click “New action” in the top right — it takes you to the library.
Installing an action is an admin action. Some columns — “Action type”, “ID”, and “Slug” — only appear in developer mode. Everyone else sees just Name, Created, and Uninstall. The ID and the slug identify the same installed action and are interchangeable wherever the API asks for one; the slug is per-organization and changes if you rename it, the ID never does.
The library
The library at /actions/library is titled “Action library” with the description “Install a curated preset or start from a base action.” A left-hand nav faceted by “All”, “Themes”, and “Categories” filters the catalog, and a “Search the library” box searches by name. “Back to installed actions” returns you to /actions.
Cards are grouped into two sections:
- Starter presets — curated, ready-to-use configurations for a common job (for example, extracting the key terms from a contract). Each preset card has a “Use preset” button.
- Base actions — the plain, unconfigured version of each action, one per action type. Each base card has a “Start from base” button.
Every card shows an icon, a short description, and dot-badges for its theme, category, and output type. Clicking “Use preset” or “Start from base” installs the action for your organization immediately and opens its configuration editor — you don’t install and configure in separate steps. If an install fails, you’ll see “Couldn’t install this action.”
Configure an installed action
The configuration editor lives at /actions/$actionId. It has an editable “Name”, a “Configuration” section, and a right-rail “Details” card.
The “Configuration” form is generated from the action’s own definition — the help text reads “These settings are passed to the action each time it runs.” You fill in typed controls (text boxes, switches, dropdowns, lists, pickers) and click “Save”. If an action takes no settings, you’ll see “This action has no configuration.”
Some settings can only be expressed as raw configuration. When that’s the case, non-developers see “This action’s configuration can only be edited in developer mode.” Turn on developer mode to edit those.
The Output choice
Extract-style actions (the ones that read documents and pull out structured fields) add an “Output” control with two choices:
- Data object — bind the extraction to a record type so approved results import as records in the space’s Data tab.
- Schema only — the extracted data stays on the run; nothing is imported into Data.
Focused Build entry points
Three sidebar destinations under Build are convenience views over the same installed actions, each filtered to one action type and opening a tailored editor:
- Document understanding — your structured-extraction actions. See Extract data from documents.
- Document generation → Fill form and Document generation → Sign — your form-filling and e-signature actions. See Fill and sign documents.
Each of these lists has a “New configuration” button that seeds a fresh install of that type. They edit the same installed actions as /actions/$actionId.
First-party actions
CloudRaker ships six actions you can install from the library. Three have dedicated Build pages:
The other three — redact PDF, redact audio, and browser fill — have no dedicated Build page or review UI: install them from the library, run them like any other action, and collect their output under Generated files on the run page. See Run an action.
Developer mode
Developer mode is a toggle in the profile menu. When it’s on, you also see:
- the Action type, ID, and Slug columns on the installed-actions list (ID and Slug render as copy-to-clipboard chips), and the catalog slug on library cards;
- a Form / JSON tab switch and a raw JSON editor in the configuration form;
- the Run details disclosure on the run page (see Run an action);
- a Manifest card on the configuration editor.
Developer mode is only about what you see in the app. To drive actions and runs from outside the app, see the Developers tab, which covers the API.
Where to go next
Launch a run over a space’s files, in bulk, and follow it on the run page.
Review extracted fields against their sources and import them into Data.
Set up form filling and e-signature, and track a signing envelope.
Drive actions and runs from the API.