Loading…
How do I edit steps (Code and HTTP)?
TL;DR: Playbook steps are building blocks in your automation. Code steps run JavaScript, TypeScript, Python, or bash in Ballet's sandbox. HTTP steps call external APIs. Edit steps in the playbook's Code tab or ask the Console to modify them for you.
Who this is for
Builders editing playbook logic directly or via Ask Ballet.
What step types exist?
| Type | Purpose |
|---|---|
| Code | Run JavaScript, TypeScript, Python, or bash in an isolated sandbox — transform data, call helpers, orchestrate logic |
| HTTP | Make API requests to external services — GET, POST, PUT, DELETE |
How do I edit a step manually?
- Open a playbook.
- Go to the Code tab.
- Select a step in the step list or graph.
- Edit the code or HTTP configuration in the step panel.
- Save and run the playbook to test.
How do I edit with Ask Ballet?
Open the Console inside the playbook and describe the change: "Add a step that posts the ticket summary to Slack" or "Change the HTTP step to use the staging API URL."
How do steps use connectors and secrets?
Steps reference Connectors (MCP servers, integrations) and Secrets (encrypted credentials) configured in your workspace. Ask Ballet can wire these up during Build, or you can configure them in the playbook's Connectors panel.
Tips for reliable steps
- Keep each step focused on one task.
- Use secrets for credentials — never hardcode API keys.
- Test with a manual run before adding schedules or webhooks.