Clear pending GitHub repository invitations from your review list
Turn invitations you have already chosen to accept into a scheduled follow-through step.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Why this helps
A pending repository invitation can remain untouched after the decision to join has already been made.
- Reduce forgotten repository invitations.
- Process intended invitations from a review list.
- Keep invitation follow-through tied to your records.
Setup
Build it in a few focused steps.
- 1Connect Baserow and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to accept only repository invitations marked for acceptance in Baserow and report any that cannot be accepted.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real pending invitation you have chosen to accept.
Questions about this workflow
Which invitations can this accept?
It accepts a pending repository invitation issued to the authenticated GitHub user.
Can it accept an invitation for another user?
No. The action is for invitations issued to the authenticated user.
What should a Baserow record contain?
It should identify the invitation and clearly indicate that you have chosen to accept it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Baserow to GitHub. A trigger fires from one place; an action lands in another.
Baserow 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.
Baserow 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.