rocket_launch ASAPilot
Get Started

Channels and Integrations

The Channels workspace is the dashboard control plane for external surfaces. It lets ASAPilot operate through OpenClaw, email, or MCP without copying business logic into separate products.

Currently provisionable channels

OpenClaw Skill

Provision ASAPilot as a skill-driven gateway for multi-turn analysis, account-aware actions, and automation control inside OpenClaw.

Email

Give the workspace a secure inbox so stakeholders can send requests and keep replying in the same email thread while ASAPilot preserves context.

MCP

Expose ASAPilot as a streamable HTTP MCP server for IDEs, agent frameworks, and custom runtimes that need shared tools and workflows.

Planned but not provisionable yet

The current catalog also shows Slack and DingTalk as planned adapters. They are part of the roadmap and visible in the dashboard, but they are not currently provisionable surfaces.

How the model works

When to use Channels

  1. Use OpenClaw when operators already live inside a skill-driven client.
  2. Use Email when executives, partners, or reviewers need async access without opening the dashboard.
  3. Use MCP when the integration target is an IDE, agent runtime, or automation framework that speaks tool protocols.