Quickstart
Run your first playbook end to end — from signing in to approving the assistant’s work.
You’ll sign in, open a space, upload documents, run a playbook, and approve the drafts the AI assistant produces. Each step links to the page that covers the detail.
The assistant drafts; you decide what to approve. The agent and automated steps never commit data on their own. They produce drafts — proposed records, filled forms, generated documents — and you review, edit, approve, or reject before anything becomes real data.
What you’ll need
- A work account in a CloudRaker organization (sign-in is handled by your company’s identity provider).
- A space to work in — or the ability to create one.
- A few documents to work on, and a playbook that your space type makes available.
New to the terms? Skim Key concepts for the glossary, or What CloudRaker is for the big picture. If you’re an admin setting things up for the first time, start with the Administration section and space types, playbooks, and actions — this quickstart assumes those exist.
The happy path
Sign in
Go to app.cloudraker.com and sign in with your work account. Your organization’s identity provider handles the login — there’s no CloudRaker password.
Open or create a space
A space is the workspace for one body of work — it holds the files, records, and people for that job.
In the sidebar, find the Spaces group. Spaces are listed under a collapsible header for each space type; expand one and click a space to open it. To start fresh, click New space and create one from a space type.
Which space type you pick matters: it decides which playbooks and actions are available inside the space. See Create a space and Space types.
Upload your documents
Open the space’s Files tab. Drag files onto the page, or use Upload files to pick them.
Uploaded files are processed automatically — there’s nothing to trigger. Give processing a moment to finish before you run a playbook over them. See Files.
Run a playbook
Open the space’s Playbooks tab and click Run playbook. Pick a playbook that fits the work, choose which files the run may use — all files in the space or a selected subset — then click Start run.
The run starts and the run page opens. Only playbooks made available by your space type appear in the picker. See Run a playbook.
Follow the run and approve
On the run page, the agent works through the playbook’s tasks on its own and pauses at approval cards when it has drafts for you.
Open a card to review the assistant’s drafted values. Extracted values are grounded — each links back to its exact source (a page and region in a PDF, or a timecode in audio) so you can confirm it before you approve. Then:
- Approve the drafts you trust.
- Reject anything wrong, with a note explaining what to fix.
Your approval is what turns a draft into real data. See Approvals and steering.
Rejecting sends the work back — be specific in your note so the next attempt fixes the right thing.
See your results
Approved extraction records land in the space’s Data tab, where you can filter, sort, and reuse them. Generated files — filled forms, produced documents — land back in the Files tab.
See Records.
Where to go next
Plain-language definitions of every term you’ll meet in CloudRaker.
Go deeper on reviewing drafts, approving, and steering a run.
More on starting runs and choosing which files a run can use.
See how a space is organized across its Files, Playbooks, Data, and other tabs.