Route supporter requests without mental juggling
When someone supports your work and asks for help, the next owner should be obvious. Notis can route the related GitHub issue for you.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Small support requests get buried because assigning them requires another manual handoff.
- Create a clear next owner
- Shorten response time for supporters
- Prevent requests from sitting unassigned
- Reduce context switching between support and development
Setup
Build it in a few focused steps.
- 1Connect Ko-fi and GitHub once in the Notis portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Use this instruction: When a Ko-fi support request arrives, find its related GitHub issue and assign it to the appropriate maintainer.
- 4Pick an incoming webhook trigger, choose your run-report channel, and test with one real request.
Questions about this workflow
Can Notis choose among several maintainers?
Yes. State your ownership rules in the plain-language instruction.
Does this change issue content?
No. The GitHub action assigns the issue only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ko fi to GitHub. A trigger fires from one place; an action lands in another.
Ko fi 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 Ko fi and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.