Caddie
Build, repair, inspect, and explain B3OS workflows with Caddie.
Caddie helps users create workflows, update existing drafts, inspect data, debug failures, and answer platform questions from inside the workflow editor. Caddie works from B3OS schemas and runtime context instead of free-form automation guesses.
What Caddie Can Do
| Capability | Examples |
|---|---|
| Plan workflows | Turn a goal into trigger, action, branch, loop, connector, and wallet requirements |
| Build workflows | Create or edit draft workflow definitions after a user approves a plan |
| Repair workflows | Identify missing fields, invalid schema values, connector gaps, or broken expressions |
| Search actions and triggers | Find relevant actions, trigger schemas, templates, and provider capabilities |
| Inspect data | Read workflow context, connector availability, Google Sheet data, recent run state, or org knowledge where permitted |
| Debug runs | Explain failed executions, missing inputs, transaction issues, and provider errors from sanitized runtime data |
Conversation Modes
| Mode | Purpose |
|---|---|
plan_required | Produce a structured plan before changing a workflow |
execute_approved_plan | Apply an approved workflow plan |
direct_execute | Make a small safe edit without a full plan |
conversation | Answer questions and explain behavior |
repair | Fix or diagnose a workflow or failed run |
Caddie is most useful when it plans visibly and edits drafts deliberately. Keep wallet, connector, and publish actions under explicit user review.
Tool Context
Caddie can use B3OS-specific tools for discovery and inspection. Public docs describe categories rather than private prompts or internal model instructions.
| Tool family | What it helps with |
|---|---|
| Action and trigger search | Find schemas, required connectors, categories, and valid payload shapes |
| Template search | Reuse known workflow patterns |
| Data inspection | Inspect sheets, source data, or workflow inputs |
| Market and crypto lookup | Look up token, price, DeFi, Coinglass, Morpho, Polymarket, Dune, and transaction context |
| Workflow debugging | Read recent run state, failed executions, and sanitized errors |
| Organization knowledge | Use approved org-specific context and memories |
| Connector listing | Understand which provider accounts are available to the organization |
Caddie Workflow Lifecycle
Best Practices
Ask for the outcome
Describe the business or operational goal, not only the low-level action list.
Name constraints
Mention required chains, tokens, providers, connector accounts, wallet limits, and safety rules.
Let Caddie inspect schemas
Available actions change over time. Schema search is more reliable than guessing fields.
Approve plans before edits
Review trigger choice, connector requirements, wallet usage, and expressions before applying a complex plan.
Test before publish
Run with sample input, inspect the graph, then publish only after validation passes.
Guardrails
| Risk | Guardrail |
|---|---|
| Secret exposure | Caddie should use connectors and masked runtime data, not raw secrets |
| Invalid action payloads | Action and trigger schemas are fetched before writing node payloads |
| Unreviewed wallet activity | Wallet and transaction workflows should require explicit human review before publish or run |
| Stale provider assumptions | Caddie can search current schemas and provider capabilities |
| Over-broad edits | Draft edits should be scoped to the current workflow or approved plan |
Use connector setup, API key creation, and wallet management flows for sensitive values. Caddie should receive requirements and references, not secrets.