Accept GitHub repository invitations automatically
Once someone is approved, the final access step can happen without another tab to remember.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Why this helps
Pending invitations become invisible blockers when founders assume onboarding finished after approval.
- Complete onboarding faster
- Reduce pending-access surprises
- Close the loop after approval
Setup
Build it in a few focused steps.
- 1Connect Accredible certificates and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it from a message.
- 3Tell Notis: When the webhook confirms approval of the named collaborator, accept the pending GitHub repository invitation associated with that approval.
- 4Select the webhook trigger, choose your reporting channel, and test with one pending invitation.
Questions about this workflow
Does this accept any invitation?
No. The instruction should identify the approved repository invitation and the intended collaborator.
What happens if the invitation is already accepted?
Notis reports the result, and no additional onboarding step is needed.
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.