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

Comparison Table

FeatureGitHubJiraLinear
OAuthYesYes (OAuth 2.0)Yes (OAuth 2.0)
WebhooksYesYesYes
Bidirectional syncYesYesYes
Auto task creationYes (label trigger)Via webhookVia webhook
PR reviewsYes--
Comment syncYesYesYes
Priority mappingYesYesYes
Status mappingYesYesYes

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

# GitHub
GITHUB_WEBHOOK_SECRET=your-secret
GITHUB_AI_TASK_LABEL=ai-task
GITHUB_AI_REVIEW_LABEL=ai-review

# Jira
JIRA_CLIENT_ID=your-client-id
JIRA_CLIENT_SECRET=your-client-secret
JIRA_REDIRECT_URI=https://your-host/api/auth/jira/callback

# Linear
LINEAR_CLIENT_ID=your-client-id
LINEAR_CLIENT_SECRET=your-client-secret
LINEAR_REDIRECT_URI=https://your-host/api/auth/linear/callback

# Cloudflare
CLOUDFLARE_API_TOKEN=your-token
CLOUDFLARE_ACCOUNT_ID=your-account-id

# Tailscale
TAILSCALE_AUTH_KEY=your-auth-key
TAILSCALE_TAILNET=your-tailnet