Integrations
Laimonade integrates with GitHub, so commits become evidence on backlog items, and with Slack, so your team can ask Laimon questions in a channel.
Last reviewed · maintained by Founder
Which integrations does Laimonade have?
Two, both optional, both configured under Integrations in the app sidebar:
- GitHub — commits, pull requests and CI status, mapped onto your backlog.
- Slack — ask Laimon questions in a channel, and receive sprint updates there.
Your coding agent connects over MCP rather than through this page. That is a separate setup — see connect your coding agent.
GitHub
What connecting GitHub does
It turns delivery into evidence. Once repositories are tracked, Laimonade reads their activity and attaches it to the items it belongs to, which is what makes closure something you can check rather than something someone asserted.
Three things follow from it:
- Commits are matched to backlog items. A confident match (80% or better) moves an item from Backlog or Ready to In Review and records the commit as closure evidence. A weaker match (70–79%) is recorded as a pending match and waits for you to accept it or mark it wrong; the item does not move. Below 70% nothing is recorded.
- Pull-request state becomes signals. Review requested, changes requested, approved and ready to merge, and a review queue that has stalled for more than 24 hours — each is raised once, where you will see it without going looking.
- Laimon knows your stack. What it reads from the repository informs how it grooms items and what it treats as risky.
Epics are never matched to commits. They complete when their children do.
Setting it up
Open Integrations, activate the GitHub integration, install the Laimonade GitHub App into the organisation or account that owns the repositories, and choose which repositories to track. Tracking is per repository, not per organisation — nothing is read from a repository you did not select.
What Laimonade does not write to GitHub
It does not push code, open pull requests, merge anything or comment on your PRs. The GitHub side of the integration is a read. Laimonade's writes land in your backlog.
Slack
What connecting Slack does
It puts Laimon where the conversation already happens. Your team can ask questions about the project without opening the app, and sprint activity arrives in a channel rather than waiting to be checked.
Commands
| Command | What it does |
|---|---|
/laimon dev summary | Posts today's GitHub commits to the dev-updates channel. |
/laimon daily summary | Summarises today's sprint activity and recent backlog changes. |
@Laimon <any question> | Ask anything about the project in natural language. |
/laimon help | Lists the available commands in Slack. |
Setting it up
Open Integrations, connect Slack, and choose which channels Laimon posts to. Channels are mapped per purpose — a stakeholder-facing channel reads differently from a dev-updates one, and separating them is the difference between a digest people read and one they mute.
Are Jira, Linear, Toggl or GitLab supported?
No. GitHub and Slack are the only integrations today, and this page will say so until that changes rather than listing plans as though they shipped.
If an integration would decide whether Laimonade works for you, tell us — what people are actually blocked on is how this list gets longer.
Do integrations cost credits?
Connecting and syncing do not. Credits are consumed when Laimon does token-backed work on what arrives — matching a commit to an item, or writing a digest. Reading GitHub state and posting a command's answer do not. See pricing for what a credit is.