Keep review plans visible when reviewers change
Review requests can shift as workloads change. Have Notis create a Confluence update with the current reviewers and changes so the team can see who is expected to review.
Trigger
GitHub Pull Request Reviewers Changed
Triggers when the list of requested reviewers (users or teams) for a pull request changes — for example when a reviewer is added, removed, or re-requested. The payload includes the full current reviewer list (users and teams with details), which reviewers were added, which were removed, and the previous reviewer list for reference.
Action
Create Page
Tool to create a new confluence page in a specified space. use when you need to create new documentation or content.
Why this helps
Reviewer changes get lost in the PR timeline, leaving uncertainty about who is still expected to review.
- Make reviewer changes easier to spot
- Keep current reviewer details in team notes
- Reduce uncertainty during code review
Setup
Build it in a few focused steps.
- 1Connect GitHub and Confluence once in the Notis portal.
- 2Create an automation from Automations, New Automation, or tell Notis in plain language from any channel.
- 3Describe the outcome in one instruction: create a Confluence review plan update for each reviewer change with the full current reviewer list, changes, and pull request link.
- 4Pick the GitHub Pull Request Reviewers Changed trigger and choose where run reports go.
- 5Test with one real reviewer change.
Questions about this workflow
Does the event show who was added or removed?
Yes. The event includes the full current reviewer list and details about reviewers added or removed.
Will it request a reviewer in GitHub?
No. The trigger observes reviewer changes and the Confluence action documents them; it does not change the pull request.
Can the update go on an existing page?
This workflow uses Create Page to make a new review plan update. For updating existing page metadata, identify the page and use a page property action instead.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Confluence. A trigger fires from one place; an action lands in another.
GitHub triggers
Confluence actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Content Label
Tool to add labels to a piece of content. use after obtaining the content id to tag pages or blog posts with metadata labels.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Space by ID
Tool to retrieve a confluence space by its id. use when you need detailed metadata of a specific space.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Blogpost
Tool to create a new confluence blog post. use when you need to publish content in a specific space.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Create Blogpost Property
Tool to create a property on a specified blog post. use when you need to add custom metadata to a blog post.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Whiteboard Property
Tool to create a new content property on a whiteboard. use when you need to attach custom metadata to a confluence whiteboard.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Create Page
Tool to create a new confluence page in a specified space. use when you need to create new documentation or content.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create Page Property
Tool to create a property on a confluence page. use when you need to add custom metadata or settings to a page.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Create Private Space
Tool to create a private confluence space. use when you need an isolated workspace viewable only by its creator.
Connect any two apps with Notis in the middle.
GitHub and Confluence, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Confluence.