Confluence and Review Notifications
MergeLoom can use approved documentation context and notify review channels after PR/MR output is published.
Confluence Context
Section titled “Confluence Context”Confluence context lets workspace admins attach selected Confluence pages as run context.
Use it when:
- product requirements live in Confluence
- architecture notes are outside the repository
- onboarding docs explain service boundaries
- ticket text refers to an approved design page
Configure Confluence from the controller where available, then add selected pages as context sources through repository/context settings.
For Self Hosted, the worker can fetch job-scoped Confluence content through controller-issued access when the job includes Confluence context sources. For Cloud Hosted, the managed execution path uses the same configured context source model.
Do not assume all Confluence spaces are automatically indexed. Use approved pages or configured context sources.
Review Notifications
Section titled “Review Notifications”Review notifications post published PR/MR links to Slack or Microsoft Teams.
Open Workflow in the controller and configure:
- Slack incoming webhook URL
- Teams incoming webhook URL
- optional review notification template
Notifications are sent after the review request is created or updated. Notification failure should not invalidate the code work. If a notification does not arrive, check whether the PR/MR exists first, then inspect controller-side activity or contact support.
Template Guidance
Section titled “Template Guidance”Keep notification templates short. Useful fields usually include:
- ticket key
- ticket title
- repository
- PR/MR link
- run outcome
Do not put secrets, private tokens, or sensitive prompt content in notification templates.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Check |
|---|---|
| Confluence context is missing | Connection status, page permission, context source scope, and whether the job includes that source. |
| Worker cannot fetch Confluence content | Controller connection, job-scoped access, worker network path, and worker audit. |
| Slack or Teams message does not appear | Webhook URL, channel permissions, plan gate, PR/MR publish status, and controller activity. |