Keep reviewers connected to the files they need
Reviewer changes can update project-file access without another permissions chore.
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 collaboration
Adds a collaboration for a single user or a single group to a file or folder. collaborations can be created using email address, user ids, or a group ids. if a collaboration is being created with a group, access to this endpoint is dependent on the group's ability to be invited. if collaboration is in `pending` status, the following fields are redacted: - `login` and `name` are hidden if a collaboration was created using `user id`, - `name` is hidden if a collaboration was created using `login`.
Why this helps
Reviewers waste time requesting access to specifications, test evidence, or launch materials after being added to a PR.
- Reduces access friction
- Aligns review participation with file access
- Prevents stalled reviews
Setup
Build it in a few focused steps.
- 1Connect GitHub and Box to Notis once through the portal.
- 2Create an automation: “When pull request reviewers change, create the appropriate Box collaboration for the current reviewers on the project folder.”
- 3Pick GitHub Pull Request Reviewers Changed as the trigger and choose a reporting channel.
- 4Test by adding a reviewer to a test pull request.
Questions about this workflow
Can removed reviewers lose access?
Describe the desired handling for removed reviewers in the plain-language instruction.
Does this work with teams?
The GitHub trigger includes users and teams; specify how the Box collaboration should be handled.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Box. A trigger fires from one place; an action lands in another.
GitHub triggers
Box actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add classification to file
Adds a classification to a file by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/files/:id//enterprise 12345/securityclassification-6vmvochwuwo`.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add classification to folder
Adds a classification to a folder by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/folders/:id/enterprise 12345/securityclassification-6vmvochwuwo`.
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.
Add domain to list of allowed collaboration domains
Creates a new entry in the list of allowed domains to allow collaboration for.
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.
Add initial classifications
When an enterprise does not yet have any classifications, this api call initializes the classification template with an initial set of classifications. if an enterprise already has a classification, the template will already exist and instead an api call should be made to add additional classifications.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add or update user avatar
Adds or updates a user avatar.
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.
Add shared link to file
Adds a shared link to a file.
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.
Add shared link to folder
Adds a shared link to a folder.
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.
Add shared link to web link
Adds a shared link to a web link.
Connect any two apps with Notis in the middle.
GitHub and Box, 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 Box.