Skip to main content

Capabilities and workflows

When to use: Bind knowledge bases, tools, skills, and MCP, or organize multi-step work in a workflow.

Path: Left instances → target instance → Edit / capability settings → choose resources → save.

  1. Test resources independently in the Resource Center first.
  2. Bind knowledge bases, tools, skills, MCP, or prompts.
  3. Save, then run a representative task.
  4. On failure, check resource status, permissions, credentials, and instance bindings.

Done when: the instance calls the configured capabilities as expected.

Bind a knowledge base when creating an instance

Workflow orchestration and publish

  1. Outline inputs, outputs, steps, errors, and stop conditions.
  2. Add nodes, connect them, and configure parameters, branches, loops, and variables.
  3. Debug with representative data and inspect each node.
  4. Retest happy and error paths, publish, then run one post-publish regression.

Done when: the workflow is published and test output is correct.

Principles

  • Memory switches change UX and compliance. See Memory.
  • Enable only the skills and tools the business needs.
  • For secrets, use API auth. See UI tour, OpenClaw, MCP.
  • Regression-test after any config change; avoid changing production in peak hours without notice.