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 7 October 2026 · maintained by Founder

Which integrations does Laimonade have?

Four integrations and one intake channel, all optional, all 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.
• Cloudflare and Fly.io — read your production deployments, and host a preview of each working branch. See hosted previews.

Laimonchat is not an integration; it is the chat surface for people outside your team. See Laimonchat for external requesters.

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, whether or not the item belongs to an epic yet. A weaker match (70–79%) is recorded on the item as a possible match; the item does not move. A commit that matches nothing above 70% becomes a new backlog item drafted from it, in In Review, so work done outside the backlog still reaches the Kanban.
• 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 writes to GitHub

Comments, and nothing else. It does not push code, open pull requests or merge anything. Most of Laimonade's writes land in your backlog; the comments are where a reply belongs on GitHub itself:

• On a pull request linked to a backlog item with acceptance criteria — by an item id in the branch name or description, or by a commit already matched to the item — a verdict on each criterion: met, not met or cannot verify, with the evidence. It is advisory and never blocks the merge.
• On a pull request that has a hosted preview, one comment per preview with its URL and the commit it was built from. See hosted previews.
• On a newly opened issue, a note saying whether it was filed to the backlog, and why not when it was not.
• On an issue assigned to Laimon, the acceptance criteria and estimate it wrote for the item behind it.
• When someone mentions Laimon in an issue thread, a reply.

The verdict, the preview comment, the triage note and the refinement note are each one comment, edited in place as things change, so a push does not send everyone following the thread another email. A reply to a mention is a new comment, because it answers a question.

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

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.

Cloudflare and Fly.io

What connecting them does

Laimonade reads your production deployments and marks a backlog item Live once every commit that delivered it is in a finished production deploy. Connect Cloudflare with an API token and account ID, Fly.io with an organisation token, then bind a Pages project, Worker or Fly app to each tracked repository. The Deploy path card sets what Deploy to production runs on a merged item: a GitHub Actions workflow, a Fly deploy, or nothing.

One repository with a front end and a back end (monorepo)

A repository that holds two apps, say frontend/ on Cloudflare Pages and backend/ on Fly.io, is split into deploy targets, one per directory:

1. Open Integrations, find the Deploy targets card, and add frontend and backend to the repository.
2. In the Cloudflare card, bind the Pages project to repository · frontend/. In the Fly.io card, bind the app to repository · backend/.
3. In the Deploy path card, choose a path per directory. A Fly deploy runs fly deploy inside the directory, with the fly.toml there.
4. Once each directory has its own project or app, remove Whole repository from the targets. Removing a target removes its binding, deploy path and preview settings.

What changes once a repository is split:

Laimonade reads which files a commit changed from the push GitHub sends it. When that is not known, the commit counts as changing every directory, so an item is never marked Live on a guess. A repository with one app needs none of this: it keeps a single Whole repository target and behaves as before.

Are Jira, Linear, Toggl or GitLab supported?

No. GitHub, Slack, Cloudflare and Fly.io 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.