Give market research issues a clear owner
When a stock research request arrives, Notis can retrieve live data and assign the matching GitHub issue to the person you specify.
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
Research requests lose momentum when the symbol, issue, and next owner have to be connected manually.
- Moves a market research issue to a named owner.
- Uses the submitted symbol for a live data lookup.
- Keeps research follow-up tied to the issue.
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 ticker lookup, matching GitHub issue, and eligible assignee in one instruction.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real ticker and assignable GitHub username.
Questions about this workflow
What information must arrive in the request?
Include a stock symbol and enough information to identify the GitHub repository and issue.
Will Notis choose a research owner from stock data?
No. Supply the owner or a clear selection rule; stock data does not define your team's ownership.
What access is needed to assign the issue?
GitHub may ignore the assignment if the authenticated user lacks push access to the repository.
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.