Skip to content
Notis

Handle repository invitation acceptance requests

Make invitation acceptance an explicit request, then let Notis complete the GitHub step for the connected account.

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

A pending repository invitation can block work when it is easy to miss among other notifications.

  • Turn an explicit onboarding request into a GitHub action.
  • Reduce the delay between requesting access and accepting the invitation.
  • Keep a run report with the request outcome.

Setup

Build it in a few focused steps.

  • 1Connect Basin and GitHub once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3Tell Notis to accept the pending repository invitation for the connected GitHub user only when the Basin submission explicitly requests acceptance.
  • 4Pick the webhook trigger and choose where run reports go.
  • 5Test with one real pending invitation request.

Questions about this workflow

Whose invitation will the action accept?

It accepts a pending repository invitation issued to the authenticated GitHub user connected to Notis.

Can it accept an invitation that is not pending?

The action is for pending repository invitations. Review the run report if the invitation is no longer pending or the action fails.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Basin to GitHub. A trigger fires from one place; an action lands in another.

Basin triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Basin 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.