Route nutrition review work to an issue owner
When a nutrition item needs review, Notis can retrieve its data and assign the related GitHub issue to a reviewer you name.
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
Nutrition review requests can linger without an owner while the item is researched and the GitHub issue is located.
- Gives a related review issue a named owner.
- Pairs an Api Ninjas lookup with GitHub follow-up.
- Cuts the manual steps between request and assignment.
Setup
Build it in a few focused steps.
- 1Connect Api Ninjas and GitHub once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe the food item, matching issue, and eligible GitHub assignee in one instruction.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real item and a repository where the assignee can be assigned.
Questions about this workflow
What details should the webhook provide?
Include the food item, GitHub repository and issue context, and the intended assignee.
Can the workflow assign an outside user?
GitHub determines assignability. The action can silently ignore changes if the authenticated account lacks push access.
Does the lookup select the reviewer?
No. Supply the reviewer or describe a grounded rule for selecting an eligible assignee.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api ninjas to GitHub. A trigger fires from one place; an action lands in another.
Api ninjas 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.
Api ninjas 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.