Skip to main content

Integrations

Integrations allow agents to interact with external tools and services, extending their capabilities beyond chat.

Available Integrations

IntegrationStatusAgentsUse Case
Atlassian (Jira + Confluence)Hermes (MCP), OpenClaw, ZeroClawIssue tracking, docs / knowledge base
Brave SearchHermes, OpenClaw, ZeroClawWeb search tool
GitHubHermes, ZeroClaw, OpenClaw, Ethos
GitLab📋Not plannedAlternative to GitHub
Linear📋Not plannedIssue tracking
Notion📋Not plannedKnowledge base
Slack (MCP tool integration)Hermes, OpenClaw, ZeroClawOutbound tool surface: list channels, search, read history, post messages via korotovsky/slack-mcp-server

Integration vs Provider vs Channel

ComponentPurposeExample
ProviderAI model backendOpenAI GPT-4
ChannelHow users talk to agentDiscord, CLI
IntegrationWhat the agent can doRead GitHub issues

How Integrations Work

Integrations typically:

  1. Read data: Fetch information from external services
  2. Take actions: Create/update items in external services
  3. Receive events: Webhooks for real-time updates
  4. Use credentials: API keys or OAuth tokens

Configuration

Integrations are managed independently of agents — define one once, then attach it to one or more agents.

From the CLI:

clawctl integration registry get --types                  # list supported types
clawctl integration registry create my-github --type github
clawctl integration registry describe my-github # paste tokens interactively

From the web dashboard:

clawctl server start opens the web dashboard, which includes an Integrations page where you can add, edit credentials, and remove integrations through a form. The page surfaces how many agents use each integration so you don't accidentally remove one that's in use; credential values are never returned to the browser.

Security

  • API tokens stored securely
  • Scoped permissions (least privilege)
  • Audit logging for actions
  • Per-integration credential isolation

Requesting New Integrations

To request a new integration:

  1. Check if it exists in 📋 Not Planned section
  2. Open an issue describing:
    • The service (e.g., PagerDuty, Zendesk)
    • Use case
    • Required actions (read, write, both)
  3. Consider contributing a PR

See individual integration pages for detailed setup instructions.