Why Playbooks
Automate recurring work
Capture a multi-step process once, then re-run it with new inputs whenever you need it — no rebuilding the steps each time.
Compose in plain English
Describe the outcome you want. The agent drafts the plan, wires the connectors, and runs it — no pipelines to build.
Light inputs, heavy lifting
Fill in a small form. The Playbook’s detailed instructions and staged plan are baked in, so the agent does the work.
Grounded & traceable
Every deliverable is grounded in your data with citations, and a QA loop verifies figures before it ships.
How a Playbook run works
Playbooks run on demand from room chat. Picking one and filling in its inputs kicks off an agent run you can watch stage by stage.1
Pick a Playbook
Choose one from the composer’s Playbooks menu, the welcome screen, or the Playbook gallery. You can start from a curated template or one your team published.
2
Preview the plan
Each Playbook shows an example input, its execution flow (the stages it runs), and the deliverables it produces before you commit. You can also expand the full instructions.
3
Fill in the inputs
A short form collects only what the Playbook needs — a company name, a document, a date range. Required fields and any setup gaps are flagged inline.
4
Run it
Submit the form. The agent loads the Playbook’s instructions and starts executing the plan, calling tools and connectors as needed.
5
Track progress live
A progress rail shows each stage as it moves through running → done, with parallel stages grouped together. You can cancel a run, or resume it, at any time.
app.corvic.ai/room/2875/agent/76367MCP Integration
runningdone0/6 stages1/6 stages3/6 stages4/6 stages5/6 stages6/6 stages
Data gathering — all sources in parallel→ data.diligence
execute_python
Run concurrently
Market report→ artifact.market_report
skill
Competitor x-ray→ data.competitors
web_search
Build the HTML diligence report→ artifact.html
write_file
Accuracy QA loop — verify figures & citations→ validation.passed
openrouter
Final delivery→ artifact.qa_log
write_file
Deliverables — nothing skipped
Live playbook progress: each stage moves from pending to running to complete, with parallel stages running concurrently.
Once a Playbook is running, it stays active for the thread. Follow-up messages continue in the same Playbook context, and you can fill in the inputs again to re-run it with new values.Anatomy of a Playbook
Every Playbook is defined by a small spec that the product renders into the preview, form, and progress view.Click any stage in the execution-flow diagram to see what it does, what it waits for, what it produces, and which tools it uses. Stages on the same row run concurrently.
Get a Playbook
Pick a battle-tested one
Start from a curated Playbook shipped with a room template, or one a teammate published to your room.
Create your own
Use Make your own in the Playbook gallery. Describe the workflow you want and the agent drafts the inputs and plan with you — no config files to write.
Create your own, conversationally
Choose Make your own and describe the process in plain English — for example, “Connect to GitHub, find the latest PR, summarize the diff, and email me the summary.” Corvic drafts the plan, wires up the connectors, and shows the Playbook being constructed stage by stage. When it looks right, publish it to the room so your whole team can run it.app.corvic.ai / new-playbook
Chat3:00 AM
Ask me anything about your data.Start a new conversation
Connect to Github, find the latest PR, summarize and send email.
PlaybooksSample questions
Claude Sonnet 4.6PromptTools · 1
You
Connect to Github, find the latest PR, summarize and send email.
1
Connect to GitHub→ data.repo
GitHub
2
Find the latest pull request→ data.pr
GitHub API
3
Summarize the PR diff→ data.summary
LLM
4
Send the summary via email→ delivery.done
SMTP
Playbook ready to run
Type a workflow in plain English — Corvic drafts the plan, wires the connectors, and runs it for you.
Sharing & scope
Playbooks are scoped so drafts stay private until they’re ready to share.This chat
Draft Playbooks you’re still shaping live in the current thread. Find them under Draft Playbooks in the thread assets panel.
Room
Publish to room to make a Playbook available to everyone in the room. Shared Playbooks appear in the gallery for all members.
Setup requirements
Before a Playbook runs, Corvic checks that everything it depends on is in place and flags anything marked Needs setup:- Connectors — if a Playbook calls an external service, connect that API in the API Secret Vault and allow the agent to use it. You can still run without it — the agent skips what it can’t reach and notes the gap.
- Workflows — if a Playbook reads from a room Workflow that doesn’t exist yet, create it first. Workflows are shared across the room and run on their own schedule; the Playbook only reads their outputs.
Categories
The Playbook gallery groups Playbooks so you can find the right one fast:Data
Documents
Finance
Research
Evaluation
Automation
Example Playbooks
Corvic ships curated Playbooks with its room templates. A few examples:Related Documentation
Exploration & Workflows
The chat-first room experience where Playbooks run.
Workflows
Shared, scheduled pipelines that Playbooks can read from.
Agents
The assistant that executes a Playbook’s plan.
API Secret Vault
Connect the external services Playbooks call.
Room Templates
Pre-built rooms that ship with curated Playbooks.
Agent Skills
Reusable capabilities Playbooks build on.