Connect company partnerships to repository access
When a partnership calls for shared code work, send Notis the company context and the access details to act on.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A new company collaboration can require repository access, but the invitation step can fall through the cracks.
- Turn a partnership handoff into a clear access task
- Reduce missed collaborator invitations
- Use company context to explain why access is needed
Setup
Build it in a few focused steps.
- 1Connect Akta and GitHub once in the Notis portal.
- 2Create an automation named for inviting company partners to repositories.
- 3Tell Notis how to use the incoming company signal and supplied GitHub username and repository details before adding the collaborator.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real company collaboration and repository.
Questions about this workflow
What must the webhook provide?
Include the company signal, GitHub username, and repository owner and name. State the conditions for an invitation in the automation prompt.
Does this always invite the user?
GitHub may invite the user or update permissions directly, depending on the repository and the authenticated account's access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Akta to GitHub. A trigger fires from one place; an action lands in another.
Akta 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.
Akta 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.