All Docs
FeaturesSidekickUpdated March 11, 2026

Integration Adapter Registry & Lifecycle — v1.0.2 Release

Integration Adapter Registry & Lifecycle

Introduced in v1.0.2

Overview

The Integration Adapter Registry is the central coordination layer for all of Sidekick's integrations. Rather than each integration being wired individually into the platform, every adapter registers itself with the registry at startup and declares what it can do. The registry takes it from there — handling discovery, lifecycle management, and health monitoring uniformly across all connectors.

This is the architectural foundation that lets Sidekick scale to hundreds of integrations without per-integration complexity.

How It Works

1. Adapter Registration

When Sidekick starts (or when a new integration is enabled), the adapter registers itself with the registry. The registration payload includes:

  • Identity — A unique adapter ID and human-readable name.
  • Capabilities — What the adapter can do (e.g. read messages, send messages, manage calendar events, trigger automations).
  • Metadata — Version, icon, required scopes, and any other integration-specific configuration.

The registry stores this information and makes it queryable by the rest of the platform. No static lists. No manual wiring.

2. Adapter Discovery

The platform discovers available integrations by querying the registry at runtime. This means:

  • New integrations become available immediately after registration — no platform restart or config change needed.
  • The dashboard's integration catalog is always in sync with what's actually registered.
  • ClawHub skills that reference an integration can resolve it dynamically through the registry.

3. Connection Lifecycle

Every adapter managed by the registry follows a four-stage lifecycle:

connect  →  active  →  refresh  →  disconnect
StageWhat Happens
connectThe adapter initiates authentication and establishes a session with the external service. OAuth flows, API key validation, and webhook subscriptions are set up here.
activeThe connection is live. The adapter is receiving events, executing actions, and reporting health metrics to the registry.
refreshThe session needs renewal — typically due to an expiring OAuth token or a dropped webhook. The registry triggers a refresh without tearing down the connection.
disconnectThe user has removed the integration, or the adapter has encountered an unrecoverable error. The registry cleans up session state and deregisters the adapter instance.

The registry tracks the current lifecycle state for every connected adapter and surfaces it in the Sidekick dashboard under Settings → Integrations.

4. Health Monitoring

The registry continuously monitors the health of all active adapters. If an adapter stops reporting or enters a degraded state, the registry will:

  1. Attempt an automatic refresh to restore the connection.
  2. Surface a warning in the dashboard if the refresh does not resolve the issue.
  3. Mark the adapter as unhealthy and pause dependent automations to prevent silent failures.

For Integration Authors

If you are building a new integration for Sidekick, the adapter registry dramatically reduces the work required. The steps are:

  1. Implement the adapter interface — Respond to the standard lifecycle hooks (onConnect, onRefresh, onDisconnect) and declare your capabilities.
  2. Register with the registry — Call the registration API with your adapter's identity and capability manifest.
  3. That's it. Discovery, lifecycle management, health monitoring, and dashboard surfacing are handled automatically.

There is no need to modify core platform code to add a new integration.

Relationship to ClawHub & OpenClaw Skills

The adapter registry is the runtime layer that makes Sidekick's OpenClaw skill compatibility possible at scale. When a SKILL.md references a local binary or service, the registry maps that dependency to the appropriate cloud-hosted adapter — automatically, at runtime, using capability matching.

Related