Skip to main content
profClaw integrates with the tools your team already uses. Webhooks create tasks automatically, OAuth connections let the agent act on your behalf, and the sync engine keeps ticket state consistent across platforms.

​
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

​
How Integrations Work

​
Webhook-to-Task Pipeline

When a webhook arrives at /api/webhooks/github (or Jira/Linear), profClaw:
  1. Verifies the signature (X-Hub-Signature-256 for GitHub)
  2. Parses the event type (issues.opened, pull_request.opened, etc.)
  3. Checks configured label triggers (ai-task, ai-review)
  4. Creates a Task via addTask() and queues it for agent processing
  5. 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
Conflict strategies: local_wins, remote_wins, latest_wins, manual

​
Environment Variables