Claude and GitHub
Start a workflow in one and act in the other, with every step on the record. Ask your AI for it, or build it yourself.
- Claude steps
- 3
- GitHub steps
- 31
Ideas for Claude and GitHub
Each one is a real trigger and action. Ask your AI for any of them, in your own words, and it builds the workflow.
- When
New pull requestThen
Start an agent - When
Updated pull requestThen
Ask Claude - When
New issueThen
Wait for an agent's reply - When
Updated issueThen
Start an agent - When
Label added to an issueThen
Ask Claude - When
New push to branchThen
Wait for an agent's reply
Templates that use Claude and GitHub
Friday summary of what the team shipped
Every Friday, AI turns the week's merged GitHub pull requests into a plain-English summary and emails it.
Customer-friendly release announcements
Rewrites each GitHub release's notes in plain language, gets your approval, then posts it to Slack.
Announce new GitHub releases in plain English in Slack
Posts each new GitHub release in Slack as a short, jargon-free summary.
What each app adds
Claude
Actions
- Ask ClaudeAsk Claude to write, summarise or answer something, and get its reply.
- Start an agentHand a task to an agent you've set up in the Claude Console. It works on its own in Anthropic's cloud, so follow this step with 'Wait for a Claude agent's reply' to get its answer.
- Wait for an agent's replyWait until a Claude agent has finished its task, then get its reply. If the agent asks permission to use a tool, this step declines, as nobody is there to approve it.
GitHub
Triggers
- New pull requestRuns when a pull request is opened in a GitHub repository.
- Updated pull requestRuns when a pull request in a GitHub repository is updated.
- New issueRuns when an issue is opened in a GitHub repository.
- Updated issueRuns when an issue in a GitHub repository is updated.
- Label added to an issueRuns when a label is added to an issue in a GitHub repository, whether the issue was just opened with it or labelled later, such as when a bug is triaged. Each label starts a run once per issue. Labels an issue already had when the workflow was turned on don't start it.
- New push to branchRuns for each new commit pushed to a branch of a GitHub repository.
Actions
- Create branchCreate a new branch in a repository. Points the new branch at the tip of an existing branch (defaults to the repository's default branch) unless you supply a specific commit SHA.
- Delete branchDelete a branch from a repository.
- Get branchGet details of a specific branch, including its latest commit SHA.
- Create commentAdd a comment to an issue or pull request. Use the issue or pull request number, since both share the same numbering.
- Create issueCreate a new issue in a repository.
- Get issueGet details of a specific issue.
How to connect Claude and GitHub
Connect your AI
Add Lodol to Claude, ChatGPT, Cursor or any MCP tool in one step, or open the editor.
Connect Claude and GitHub
Sign in to each once in your workspace. Their keys are encrypted and used by name.
Describe it, then turn it on
Say what should happen, and when. Try a run, then turn it on; every run is traced.
Questions about Claude and GitHub
Yes. Connect each app once in your Lodol workspace and any workflow can use both: 3 actions in Claude, and 22 actions and 9 triggers in GitHub.
Ask Claude, ChatGPT, Cursor or any AI tool connected to Lodol, in your own words, and it builds the workflow in your workspace. Or add the steps yourself in the visual editor, or start from one of the 3 templates that already use both.
Free includes 100 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes.
Connect Claude and GitHub.
Ask for it in Slack, Claude or ChatGPT. Lodol does it every time, and tells you if anything breaks.
Free plan, no credit card