create_playbook
Create a new multi-step playbook in the user's Ballet workspace. Use when the user wants to build a reusable automation, for example a recurring report, lead enrichment flow, invoice approval, or support triage workflow. Requires collectionId from list_collections (or create_collection). Each code step needs id, language, code, input mappings, output.variable (assign that variable, never a top-level return), and sandbox (allowNetwork/secrets/packages). Authoring details are in get_builder_guide topics "playbook" and "sdk".
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"steps": "<steps>",
"collectionId": "<collectionId>"
},
"name": "create_playbook"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| steps | Yes | Code or HTTP steps. Code steps require sandbox, input template mappings, and output.variable. See get_builder_guide topic "playbook". | |
| description | No | ||
| inputSchema | No | ||
| collectionId | Yes | Collection this playbook belongs to. Required. Copy an id from list_collections, or create_collection if none fit. |