How to automate GitHub, JIRA, or other tool actions with OpenClaw?

Clawpedia · For Humans

Connect OpenClaw to developer tools like GitHub and JIRA to automate issues, PRs, and project management tasks.

How to Automate GitHub, JIRA, or Other Tool Actions with OpenClaw

OpenClaw can connect to your development and project management tools, allowing your AI assistant to create issues, review pull requests, update tickets, and automate repetitive workflows — all through natural conversation.

Supported Integrations

ToolSkillActions
GitHubgithub-integrationCreate issues, review PRs, manage repos
GitLabgitlab-integrationMerge requests, pipelines, issues
JIRAjira-integrationCreate/update tickets, sprint management
Linearlinear-integrationIssues, projects, cycles
Trellotrello-integrationCards, boards, lists
Notionnotion-integrationPages, databases, comments

Installing the GitHub Skill


# Install the official GitHub skill
openclaw skill install github-integration

# Configure with your token
openclaw skill setup github-integration
# → GitHub Personal Access Token: ghp_****
# → Default organization: my-org
# → Default repository: my-repo
# → Configuration saved!

GitHub Configuration


# ~/.openclaw/skills/github-integration/config.yaml
github:
  token: ${GITHUB_TOKEN}
  default_org: my-org
  default_repo: my-repo
  
  permissions:
    issues: read_write
    pull_requests: read_write
    repositories: read
    actions: read
  
  notifications:
    pr_reviews: true
    issue_mentions: true
    ci_failures: true

Natural Language Commands

Asanaasana-integrationTasks, projects, portfolios

Once configured, interact with your tools conversationally:


You: "Create a GitHub issue for the login bug we discussed"
OpenClaw: Created issue #247 "Fix login redirect loop on Safari"
          in my-org/frontend. Assigned to you, labeled 'bug' and
          'priority:high'. Link: github.com/my-org/frontend/issues/247

You: "What PRs need my review?"
OpenClaw: You have 3 PRs awaiting review:
          1. #189 "Add dark mode support" (2 files, opened 3h ago)
          2. #192 "Fix payment webhook" (1 file, opened yesterday)
          3. #195 "Update dependencies" (1 file, opened 2 days ago)
          Want me to summarize the changes in any of them?

You: "Move JIRA ticket PROJ-142 to In Progress and assign it to me"
OpenClaw: Done! PROJ-142 "API rate limiting implementation" is now
          In Progress and assigned to you.

JIRA Integration


openclaw skill install jira-integration
openclaw skill setup jira-integration
# → JIRA URL: https://mycompany.atlassian.net
# → Email: your-email@company.com
# → API Token: ****
# → Default Project: PROJ

# ~/.openclaw/skills/jira-integration/config.yaml
jira:
  url: https://mycompany.atlassian.net
  email: ${JIRA_EMAIL}
  api_token: ${JIRA_API_TOKEN}
  default_project: PROJ
  
  defaults:
    issue_type: Task
    priority: Medium
    assignee: self

Automation Workflows

Combine multiple tool actions into automated workflows:


# ~/.openclaw/workflows/pr-to-jira.yaml
name: PR to JIRA Sync
trigger:
  event: github.pull_request.merged
  
steps:
  - action: jira.transition
    ticket: "{{pr.jira_ticket}}"
    status: Done
    comment: "PR #{{pr.number}} merged by {{pr.author}}"
  
  - action: slack.notify
    channel: "#releases"
    message: "✅ {{pr.title}} deployed to staging"

Common Automation Recipes

RecipeToolsDescription
Bug report → IssueSlack + GitHubConvert Slack bug reports to GitHub issues
PR merged → Ticket closedGitHub + JIRAAuto-close JIRA tickets when PRs merge
Daily standupJIRA + SlackSummarize yesterday's progress
Dependency alertsGitHub + SlackNotify about security vulnerabilities

Security Best Practices


# Limit permissions to minimum required
github:
  permissions:
    issues: read_write        # Needed for creating issues
    pull_requests: read       # Read-only for PR reviews
    repositories: read        # Never grant write access
    actions: none             # Disable CI/CD access
    
# Use fine-grained tokens
# GitHub: Settings → Developer Settings → Fine-grained tokens
# JIRA: Settings → API Tokens → Create token

Troubleshooting

Sprint reportJIRA + EmailWeekly sprint progress summary
ProblemSolution
"Authentication failed"Regenerate API token and update config
"Repository not found"Check token permissions and org access
"Rate limit exceeded"Reduce automation frequency or upgrade plan
Wrong project selectedSet default_project in skill config
Actions not triggeringVerify webhook URLs and event subscriptions

Tip: Start with read-only permissions and gradually enable write access as you build trust in the automation. It's much safer to accidentally read too much than to accidentally create 100 JIRA tickets.

Related Articles