Route incoming requests to a GitHub issue owner
Give Notis the request and issue context so it can add the right assignee in GitHub.
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
Issue ownership is easy to miss when a request starts outside the repository.
- Put ownership on the issue while request context is fresh.
- Reduce manual follow-up after an API-driven request.
- Use only assignees and issue details present in the request.
Setup
Build it in a few focused steps.
- 1Connect Apiverve and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to find the issue and assignee named in each request, then add that assignee to the issue.
- 4Choose the webhook trigger and select where Notis should send run reports.
- 5Test with one real request and confirm the issue assignment.
Questions about this workflow
What if the request does not identify an issue or assignee?
The prompt should tell Notis not to guess. Include the issue and intended assignee in the request or handle that request manually.
Can GitHub ignore an assignment?
The action description says changes may be silently ignored 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 Apiverve to GitHub. A trigger fires from one place; an action lands in another.
Apiverve 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.
Apiverve 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.