Check organization access status for a project contact
Use the organization and username in a review handoff to check whether the organization has blocked that account.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if a user is blocked by an organization
Checks if a github user is blocked by an organization; a successful response (204 no content) indicates the user is blocked, while a 404 not found error indicates the user is not blocked.
Why this helps
Project coordination gets harder when an access restriction is discovered only after a handoff fails.
- Check a specific user's block status in an organization.
- Surface an access concern in the project handoff report.
- Reduce time spent diagnosing an unclear collaboration blocker.
Setup
Build it in a few focused steps.
- 1Connect Classmarker and GitHub once in Notis.
- 2Create an automation that checks block status for the organization and username supplied in the handoff.
- 3Pick the Notis webhook trigger and choose where run reports should go.
- 4Test with one real organization and user pair.
Questions about this workflow
Does this unblock a user?
No. It checks whether the user is blocked by the organization and does not change access.
What should the webhook provide?
Provide the organization name and GitHub username to check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Classmarker to GitHub. A trigger fires from one place; an action lands in another.
Classmarker triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Classmarker and GitHub, 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 GitHub.