Turn follow-up reports into clear issue ownership
Send the report and let Notis update assignees on the GitHub issues it identifies.
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
Follow-up reports can name owners, but those decisions are easy to lose before they reach the issue tracker.
- Reflect report decisions in issue ownership
- Add or remove assignees on identified issues
- Keep follow-up work close to the tracked issue
Setup
Build it in a few focused steps.
- 1Connect Carbone and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe how to match report items to issues and update their assignees in one instruction.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with a real report and confirm the resulting issue assignments.
Questions about this workflow
Can the report assign any GitHub user?
The action adds or removes assignees. GitHub may silently ignore changes if the authenticated user lacks push access to the repository.
What if an issue is missing from the report?
Tell Notis to act only on issues identified in the supplied report so unrelated issue assignments are not changed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Carbone to GitHub. A trigger fires from one place; an action lands in another.
Carbone 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.
Carbone 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.