Grant GitHub access after a certificate is issued
A verified credential can open the right repository door without another follow-up task.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Founders lose time checking credential records, finding the right GitHub repository, and sending access invitations manually.
- Reduce onboarding handoffs
- Keep repository access tied to verified credentials
- Prevent qualified contributors from waiting for an invitation
Setup
Build it in a few focused steps.
- 1Connect Accredible certificates and GitHub to Notis once through the portal.
- 2Create a new automation in Automations or tell Notis what you want in plain language.
- 3Use this instruction: When a verified Accredible credential is issued, invite the named contributor to the appropriate GitHub repository with the access level stated in the credential context.
- 4Choose the incoming webhook trigger, select a channel for run reports, and test with one real credential.
Questions about this workflow
What starts this workflow?
A Notis webhook receives a request from Accredible certificates or your credential backend when a credential is issued.
Does Notis decide repository access automatically?
Yes. Your plain-language instruction tells Notis how to interpret the credential context and select the appropriate repository and permission.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Accredible certificates to GitHub. A trigger fires from one place; an action lands in another.
Accredible certificates triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Accredible certificates and GitHub. Any 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.