Keep repository invitations from blocking Bolna work
Schedule a check for the GitHub repository access needed by your Bolna agent work and accept the intended pending invitation.
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 repository invitation can sit unnoticed and block follow-up work when it arrives outside the usual context.
- Make invitation follow-up part of a recurring routine.
- Accept a pending invitation when it matches the specified Bolna work.
- Reduce the chance of overlooking repository access.
Setup
Build it in a few focused steps.
- 1Connect Bolna and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to accept a pending GitHub repository invitation only when it matches the repository and Bolna work context you specify.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real pending invitation.
Questions about this workflow
Will it accept every invitation?
The instruction should specify which repository or Bolna work context qualifies. The GitHub action accepts a pending invitation for the authenticated user.
Can this discover invitations through Bolna?
Bolna has no listed trigger events here, so this workflow starts on a Notis schedule and uses the specified Bolna context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolna to GitHub. A trigger fires from one place; an action lands in another.
Bolna 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.
Bolna 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.