Available Integrations
GitHub
Issue and PR webhooks, OAuth for repo access, automated code reviews, and AI task labels.
Jira
OAuth 2.0 connection, bidirectional ticket sync, status field mapping, and sprint support.
Linear
OAuth 2.0, issue sync, label and state mapping, and team-based project routing.
Cloudflare
Workers deployment, D1 database, R2 storage, KV namespaces, and edge routing.
Tailscale
Mesh VPN tunnels, secure device-to-device access, and zero-config private networking.
Comparison Table
| Feature | GitHub | Jira | Linear |
|---|---|---|---|
| OAuth | Yes | Yes (OAuth 2.0) | Yes (OAuth 2.0) |
| Webhooks | Yes | Yes | Yes |
| Bidirectional sync | Yes | Yes | Yes |
| Auto task creation | Yes (label trigger) | Via webhook | Via webhook |
| PR reviews | Yes | - | - |
| Comment sync | Yes | Yes | Yes |
| Priority mapping | Yes | Yes | Yes |
| Status mapping | Yes | Yes | Yes |
How Integrations Work
Webhook-to-Task Pipeline
When a webhook arrives at/api/webhooks/github (or Jira/Linear), profClaw:
- Verifies the signature (
X-Hub-Signature-256for GitHub) - Parses the event type (
issues.opened,pull_request.opened, etc.) - Checks configured label triggers (
ai-task,ai-review) - Creates a
TaskviaaddTask()and queues it for agent processing - Posts a result comment back to the source issue or PR
Sync Engine
The sync engine (src/sync/) handles bidirectional state updates:
- Push: Local ticket changes propagate to the external platform
- Pull: External changes update local tickets on a polling interval
- Bidirectional: Both directions, with conflict resolution
local_wins, remote_wins, latest_wins, manual