Accept repository invitations from Close handoffs
Start implementation work without waiting for a manual invitation check.
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 are easy to overlook during a busy customer transition.
- Fewer blocked starts
- Quicker access
- Simpler launch checklists
Setup
Build it in a few focused steps.
- 1Connect Close and GitHub in Notis once.
- 2Create a new automation in Automations.
- 3Tell Notis to accept the pending GitHub repository invitation identified by each qualifying Close webhook.
- 4Choose the webhook trigger and a report channel.
- 5Test with one real implementation handoff.
Questions about this workflow
Can it accept any invitation?
Tell Notis which pending invitation or repository to accept in the webhook context.
What happens if no invitation is pending?
The GitHub result is reported so the handoff can be resolved.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Close to GitHub. A trigger fires from one place; an action lands in another.
Close 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.
Close 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.