Integrations Overview
MergeLoom connects four categories of tools:
| Integration type | Examples | What it does |
|---|---|---|
| Work tracker intake | Jira, GitHub Issues, GitLab Issues, Azure Boards, monday.dev, Linear | Supplies eligible tickets, issues, work items, or board items. |
| Code host output | GitHub, GitLab, Azure Repos | Supplies repositories and receives branches, PRs, or MRs. |
| Documentation context | Confluence, repository guidance files | Adds approved context to runs. |
| Review notifications | Slack, Microsoft Teams | Posts review-ready PR/MR links after publish. |
Configure integrations in the customer controller at https://controller.mergeloom.ai.
The Local Worker UI is not where you connect Jira, GitHub, GitLab, Azure DevOps, monday.dev, Linear, Confluence, Slack, or Teams. Self Hosted workers receive job-scoped integration details from the controller when they start work.
Intake Is Polling and Manual Sync
Section titled “Intake Is Polling and Manual Sync”MergeLoom work intake is controller-driven polling and manual sync. Do not configure inbound webhooks from Jira, GitHub Issues, GitLab Issues, Azure Boards, monday.dev, or Linear unless MergeLoom support explicitly asks you to for a custom environment.
Review notifications are outbound Slack or Teams incoming webhooks configured in Workflow settings. Notification failures are logged and do not normally make the code run fail.
Connector Availability
Section titled “Connector Availability”| Connector | Role | Public support note |
|---|---|---|
| Jira Cloud | Work tracker | Atlassian OAuth app. |
| Confluence Cloud | Documentation context | Atlassian OAuth app; confirm sensitive page handling with MergeLoom before adding restricted spaces. |
| GitHub.com | Work tracker and code host | GitHub App path. Contact MergeLoom support before planning GitHub Enterprise. |
| GitLab.com / self-managed GitLab | Work tracker and code host | OAuth path; self-managed instances need matching base and API URLs. |
| Azure Boards | Work tracker | Azure DevOps Services-oriented Entra app path. |
| Azure Repos | Code host | Uses the Azure DevOps connection for repository access and PR output. |
| monday.dev / monday.com | Work tracker | OAuth path for boards and item updates. |
| Linear | Work tracker | OAuth path with read/write scope. |
| Slack / Teams | Review notifications | Incoming webhook URLs; no OAuth setup in the current customer workflow. |
Cloud Hosted
Section titled “Cloud Hosted”Cloud Hosted workspaces use controller-managed integrations and MergeLoom-managed workers. The controller coordinates intake, repository access, review creation, and audit.
Self Hosted
Section titled “Self Hosted”Self Hosted workspaces still use controller-managed integrations. The worker executes the code path locally and receives the repository access details needed for the assigned job.
Setup Order
Section titled “Setup Order”- Connect the work tracker.
- Connect the code host.
- Sync the repository catalog.
- Enable one writable work repository.
- Configure workflow intake and output.
- Add review notifications only after the first PR/MR path works.
- Add documentation context after the core route is stable.
Permission Principle
Section titled “Permission Principle”Give MergeLoom enough access to:
- read eligible work
- post comments and move statuses where configured
- clone/fetch/push the selected repositories
- create or update PRs/MRs
- fetch approved documentation context
- post review notifications
Avoid granting broad organization access if a narrower project, repository, group, or app installation scope meets the workflow need.
Related pages: