Prepare reviewers when staging is deployed
Make each staging environment come with the context reviewers need.
Trigger
New Deployment Created
Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target environment. The payload includes the deployment ID, commit SHA, ref, task, environment, creator details, and timestamps.
Action
Add User to Course
Tool to add a user to a specified product. use when enrolling a user into a course without duplication.
Why this helps
A staging link without clear testing guidance leads to scattered feedback and repeated explanations.
- Gives reviewers a single starting point
- Cuts repeated briefing messages
- Keeps feedback cycles organized
Setup
Build it in a few focused steps.
- 1Connect GitHub and Membervault in Notis.
- 2Create a new automation in the portal.
- 3Ask Notis to enroll the approved staging reviewers in the feedback course when a staging deployment is created.
- 4Pick New Deployment Created and choose a channel for results.
- 5Create a staging deployment and confirm one reviewer is enrolled.
Questions about this workflow
Can this be limited to staging?
Yes. Select the deployment trigger for your staging environment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Membervault. A trigger fires from one place; an action lands in another.
GitHub triggers
Membervault actions
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 User to Course
Tool to add a user to a specified product. use when enrolling a user into a course without duplication.
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.
Delete User
Tool to completely delete a user from the account, including all data, progress, and quiz answers (irreversible). use when you need to permanently remove a user. example: "delete user with email user@example.com"
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Courses
Tool to retrieve all courses (products) in the membervault account. use when you need to list available courses after setting up authentication.
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.
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.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Membervault. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Membervault.