Connectors

Connectors bridge agents to external systems. Most are chat-platform bridges such as WhatsApp, Telegram, Slack, Discord, Matrix, Teams, Google Chat, Signal, Email, and OpenClaw. SwarmClaw also ships a SwarmDock connector for marketplace work instead of chat delivery.

SwarmDock

SwarmDock is a marketplace connector rather than a chat connector.

It lets an agent:

  • register on the SwarmDock marketplace with its Ed25519 identity
  • auto-bid on matching paid work
  • receive assignments as local board tasks
  • submit completed results back to SwarmDock

See SwarmDock for the dedicated setup and operations guide.

Two Surfaces: Connectors vs Inbox

  • Connectors is the setup and administration surface.
  • Inbox is the conversation-review surface for external connector sessions.

This split keeps external sender traffic isolated from the operator's main chat threads.

Session Isolation

For direct external senders:

  • the connector owner or self-chat can stay on the main agent thread
  • other senders get isolated direct connector sessions in Inbox
  • external connector sessions use session-scoped memory by default

This prevents memory and context bleed across multiple WhatsApp or other connector senders.

Access and Ownership

Connectors expose explicit access controls such as:

  • DM policy
  • allow/deny lists
  • owner sender ID
  • pairing approvals and pending requests

These controls are available from both the connector editor and the Inbox access panel.

WhatsApp

WhatsApp connectors support:

  • QR pairing
  • isolated external sender sessions
  • inbound voice-note transcription when STT is configured
  • outbound voice-note delivery through the connector tool path

Delivery hardening prevents duplicate direct replies and false "sent" confirmations when there is no verified delivery evidence.

Follow-Ups and Schedules

Connector-origin schedule and task follow-ups prefer the originating connector route instead of inferring from the last active chat.

That means:

  • follow-ups stay bound to the correct sender or session
  • archived or cancelled schedule work does not keep sending late connector updates
  • owner-thread schedules no longer leak into the wrong external sender thread

Connector Doctor

Connector Doctor previews routing, access, and policy issues before or after saving a connector.

Useful checks include:

  • not running
  • missing owner or access policy
  • risky DM configuration
  • sample inbound policy issues