Accept GitHub repository invites from Checkvist
A Checkvist task can close the loop on a GitHub invite while the details are still fresh.
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
Repository invites get buried between planning lists and GitHub notifications.
- Keeps access requests visible in your task list
- Cuts context switching between planning and GitHub
- Leaves a clear run report when the invite is accepted
Setup
Build it in a few focused steps.
- 1Connect Checkvist and GitHub in Notis once.
- 2Create a new automation and describe that a named Checkvist task should accept a pending GitHub repository invitation for the authenticated user.
- 3Choose a notis_webhook trigger and send the Checkvist task request to its webhook.
- 4Choose a report channel, then test with one real invitation task.
Questions about this workflow
Can this accept any GitHub invitation?
It can accept a pending repository invitation available to the authenticated GitHub user, based on the task instruction.
Does Checkvist provide the trigger event?
No. Use a Notis webhook and send the task request to it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Checkvist to GitHub. A trigger fires from one place; an action lands in another.
Checkvist 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.
Checkvist 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.