Move promising social partnerships into GitHub
When a creator, developer, or partner is ready to contribute, turn the social signal into a clear GitHub access step.
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
Potential collaborators are easy to lose between a promising message and the actual repository invitation.
- Shortens the path from conversation to contribution
- Makes access follow-up more reliable
- Keeps invitations tied to trusted signals
Setup
Build it in a few focused steps.
- 1Connect TikHub and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a TikHub message confirms a trusted collaboration, invite the named GitHub user to the specified repository with the appropriate permission.
- 4Select an incoming webhook trigger and a reporting channel, then test with one approved collaborator.
Questions about this workflow
Can it grant different permission levels?
Yes. State the permission rule in the plain-language instruction and require confirmation of the repository and user.
Does it work for organizations?
Yes, provided the connected GitHub account has the required repository permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link TikHub to GitHub. A trigger fires from one place; an action lands in another.
TikHub triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just TikHub and GitHub. Any 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.