Connectivity

Integrations

Objective: Keep the squad movingMode: Retro Ops ShellLoadout: Stable + Low Drama
SearchAlertsProfile
Webhook Rails
2
Discord Tasks
1
GitHub Tasks
1
Human Escalations
0
Failing Automations
0

Webhook Rails

Inbound integration rail
Discord intake
live
/api/integrations/discord/task-from-message
  • •Creates a task from a Discord message payload.
  • •Audits channel, thread, and message IDs for later traceability.
  • •Best for “turn this thread into a tracked item” flows.
titleauthormessagepriorityrequiresHumanchannelIdthreadIdmessageId
Inbound integration rail
GitHub issue intake
partial
/api/integrations/github/task-from-issue
  • •Accepts GitHub-style issue payloads and opens a Mission Control task.
  • •Signature verification is wired, but live repo auth is still thin outside webhook delivery.
  • •Useful for issue-to-task routing even before deeper sync lands.
repoissueNumbertitlebodyauthorpriorityrequiresHumanurl

Service Handshake

Gateway daemon
unknown
Backbone for session, cron, and status reads
Node service
unknown
Browser/canvas-side execution surface for richer tooling
Agent registry
unknown
Operator-visible agent inventory from OpenClaw status
Security audit feed
live
Risk findings surfaced into dashboard + review routes

Mission Flow

Discord → task
  1. 1Post a signed webhook to the Discord intake route.
  2. 2Mission Control creates a task and links the originating thread/channel IDs.
  3. 3Operator triages the new item from Tasks, Alerts, or Dashboard lanes.
GitHub issue → task
  1. 1Send a GitHub-signed payload to the issue intake route.
  2. 2Mission Control stores the issue body as task context and logs an audit record.
  3. 3Use Tasks for ownership and human-required escalation until deeper sync exists.
Automation run-now
  1. 1Pick a cron job from the automations board.
  2. 2Run-now executes through openclaw cron run <id>.
  3. 3Review the result in Dashboard, Review, or Audit if it misbehaves.

Operational Reality

Discord intake
1
tasks currently sourced from Discord threads or messages
GitHub intake
1
tasks currently sourced from GitHub issues
Known gap
Session message injection is still not a clean local integration surface.
documented blocker
Current shell can audit the intent and route operators to the right board, but arbitrary off-route session message delivery still needs a supported path.

Automation Hooks

No automation jobs discovered from OpenClaw right now.

Operator Notes

Keep integrations honest
This route should show what is wired, what is partially wired, and what is still fantasy. No fake “connected” badges.
Best next shell pass after this page
Docs, search, and profile are now the main remaining routes if you want every operator-facing screen in the same pixel shell language.