Create a Playbook

🚧

Beta

Playbooks are available to selected workspaces while we continue to improve them. Contact your V7 account team if you need access.

Create a Playbook by turning a business process into clear instructions, decisions, integrations, and outputs. Start with the outcome your team needs, not the tools you use today.

1. Provide representative examples

Add sample inputs and expected outputs. Include a normal case and difficult cases. Samples let you test whether the instructions produce the result your team expects before you rely on the Playbook for production work.

2. Review the draft plan

V7 Go presents a draft plan before it builds the full Playbook. Check that the plan covers the intended outcome, required inputs, decisions, integrations, human review points, and outputs.

3. Define the process

Describe the work in the order a capable teammate would perform it. State what each step needs, the rule it applies, and the result it must return. Refine the instructions until they cover the main process and known edge cases.

Make decisions explicit. A Playbook can branch when a document is incomplete, request human review when risk is high, or repeat work for each submitted item.

4. Add integrations and outputs

Connect an MCP integration only where a step needs external data or an approved action. Declare every required integration so V7 Go can identify missing connections before a run starts.

Use output steps for deliverables such as reports, files, structured records, and integration results. V7 Go collects outputs in one run overview.

5. Test before you rely on it

Run the Playbook with the sample inputs. Check that it follows the core instructions, handles expected exceptions, requests review where needed, and produces the expected output. Refine the instructions when a test exposes an ambiguity.

Technical notes

V7 Go validates the authored process before it can run. A valid Playbook needs a clear starting step and connected paths. Decision branches must define the next step for each expected result. Complex branches must return to a clear next step before the process continues.

Next steps

• Playbook inputs and resources
• Playbook outputs
• Review Playbook runs