Verify collaborator access before account work
Check the exact GitHub user and repository included with a Bigpicture update, then report whether collaborator access is present.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if a user is a repository collaborator
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Why this helps
Teams can lose time discovering access gaps only after a repository task is ready to start.
- Confirm access before coordinating repository work
- Avoid granting access without an explicit decision
- Report missing or invalid user and repository details
Setup
Build it in a few focused steps.
- 1Connect Bigpicture io and GitHub once in Notis.
- 2Create an automation in Notis from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to check collaborator status only for the exact GitHub username and repository supplied with the research, then report the result without changing access.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real update that includes a GitHub username and repository owner/name.
Questions about this workflow
Will this add the person as a collaborator if they lack access?
No. It only checks collaborator status and reports the result.
What information must the update include?
It needs a GitHub username plus the repository owner and repository name. Notis should report when any of those are missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bigpicture io to GitHub. A trigger fires from one place; an action lands in another.
Bigpicture io 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.
Bigpicture io 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.