Quick start

From sign-up to your first real playbook run, in one guided conversation.

New workspaces open on a guided setup that takes you from nothing to a first real run in four checkpoints: add your first app, connect it, create a playbook, see it run. You can complete every checkpoint in the setup conversation, or do any step yourself with the checklist beside it — both paths count.

Setup is free. Your trial's 100 credits are only spent when skills actually run.

1. Add your first app

Open the Gallery and pick an app. Each card shows the app's category, a one-line summary, and how many operations its skill carries. Click Add — the skill is copied into your workspace immediately, at no cost.

You land directly in the connect conversation for that app.

2. Connect it

The assistant walks you through the credential: what token the app needs and where to get it (each credential field links to the provider's own token page). The value goes into a secure card — a masked field, never chat text. It's stored write-only in an encrypted vault and can't be read back.

As soon as the credential is saved, RuneSpace runs one read-only operation against the live API and shows the result as evidence: the method, URL, HTTP status, and response. A 401 means the key is wrong; a 403 means missing scopes. If the check fails, the card reopens so you can paste a corrected value.

Prefer a form? Do it manually takes you to the skill's Credentials card, where the same credential can be added directly.

3. Try a first read

On the skill's page, the Test against live API panel suggests starter questions built from the skill's read operations — these don't change anything. Ask in plain words and watch each API call appear in the transcript as evidence you can expand.

4. Create a playbook

Go to Playbooks → New playbook and describe the job in plain words — what to check, what to summarise, and how often. The assistant drafts the name, instructions, skills, and schedule, then shows a confirmation card. Nothing is created until you confirm.

During onboarding the card reads "Enable and run now": on confirm, the playbook is created, enabled, and its first run starts immediately instead of waiting for the next scheduled slot.

5. See it run

The run lands in your feed on the home page within moments — what it read, what it produced, and what it cost in credits. From then on the playbook runs on its schedule, and every run is kept in the playbook's history.

That's the whole loop. Next: